Skip to main content

Is Ancestry Down?

No — Ancestry is up

Reachable from all 4 checked regions

Average response time: 374ms

Last checked · checks run every 6 hours

Official status page: https://status.ancestry.com

Ancestry uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
399ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 22 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

22-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: 100.00% uptime, 9 checks
Aug 3: 100.00% uptime, 19 checks
Aug 4: 100.00% uptime, 14 checks
Aug 5: 100.00% uptime, 12 checks
Aug 6: 100.00% uptime, 17 checks
Aug 7: 100.00% uptime, 21 checks
Aug 8: 100.00% uptime, 14 checks
Aug 9: 100.00% uptime, 12 checks
Aug 10: 100.00% uptime, 16 checks
Aug 11: 100.00% uptime, 17 checks
Aug 12: 100.00% uptime, 19 checks
Aug 13: 100.00% uptime, 14 checks
Aug 14: 100.00% uptime, 12 checks
Aug 15: 100.00% uptime, 16 checks
Aug 16: 100.00% uptime, 15 checks
Aug 17: 100.00% uptime, 15 checks
Aug 18: 100.00% uptime, 14 checks
Aug 19: 100.00% uptime, 16 checks
Aug 20: 100.00% uptime, 18 checks
Aug 21: 100.00% uptime, 19 checks
Aug 22: 100.00% uptime, 14 checks
Aug 23: 100.00% uptime, 12 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

bom
HTTP 403 · challenge

Answered in 188ms — the origin is serving traffic, it just refused our client.

cdg
HTTP 403 · challenge

Answered in 88ms — the origin is serving traffic, it just refused our client.

dfw
307ms
DNS 49ms TCP 1ms TLS 7ms TTFB 272ms
ewr
217ms
DNS 39ms TCP 2ms TLS 10ms TTFB 188ms
fra
HTTP 403 · challenge

Answered in 116ms — the origin is serving traffic, it just refused our client.

gru
HTTP 403 · challenge

Answered in 393ms — the origin is serving traffic, it just refused our client.

iad
601ms
DNS 401ms TCP 2ms TLS 8ms TTFB 545ms
jnb
HTTP 403 · challenge

Answered in 73ms — the origin is serving traffic, it just refused our client.

lax
374ms
DNS 6ms TCP 1ms TLS 9ms TTFB 311ms

What Ancestry does

Ancestry is a genealogy service built on a large collection of digitised historical records, plus a consumer DNA test that matches subscribers to relatives. People build family trees against those records, and the hints that link a person in your tree to a document are generated on Ancestry's servers, so tree building depends on the service being up.

What an outage looks like

Sign-in fails, which Ancestry tracks separately from the rest of the site, so the home page can load while nobody can get in. Searches return errors or no results against collections that normally match. Family tree pages fail to save edits, DNA match lists will not load, and hints stop appearing. The mobile apps are affected independently of the website.

What to do about it

Check status.ancestry.com, which reports login, search, family tree, DNA and hint features as separate entries, so you can tell a sign-in incident from a search one. If only the website fails, try the mobile app, which is tracked independently. Avoid re-entering tree edits repeatedly during an incident, because duplicate people and duplicate facts are tedious to merge afterwards.

Is it down for everyone, or just you?

If this page says Ancestry is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Ancestry outage FAQ

Is Ancestry down or is it just my account?
Ancestry tracks login processes as their own component, so a genuine outage affecting sign-in shows there. If the status page reports login healthy and you still cannot get in, the problem is more likely your account, your browser cache or your password. Ancestry's support site also publishes an article answering this exact question during incidents.
Will I lose family tree edits made during an outage?
Edits that saved and displayed are stored. Anything entered while the tree component was failing may not have been recorded, and the common mistake is retyping it several times, which creates duplicate people once the service recovers. Reload the profile after the incident and check what actually saved before adding it again.
Does an Ancestry outage affect DNA results?
DNA features are tracked separately from search and family tree, so match lists and ethnicity estimates can fail while record search works. Your results themselves are not recalculated or lost by an outage; the failure is in serving them. If a test is still processing, an incident does not restart the lab work, only your ability to view progress.
Does the Ancestry app work when the website is down?
Sometimes. Ancestry lists mobile applications as a separate component from the website, and they can fail independently, so trying the app is a worthwhile thirty-second test. Both depend on the same login and search services, so an incident in those affects everything at once regardless of which one you open.

How we measure this

  • We request Ancestry's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Ancestry publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Ancestry goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required