Is Ancestry Down?
When we last reached Ancestry directly, it answered and refused us — origin returns HTTP 403 bot challenge. An answer is proof the origin was serving traffic, but it measures our access, not the service, so we publish no percentage.
Last checked · checks run every 6 hours
Official status page: https://status.ancestry.com
Why there is no uptime figure on this page
The last time we fetched Ancestry's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether Ancestry works for you.
A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and Ancestry's own status feed, which you can weigh yourself.
30-day history
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.
A static asset loaded in 82ms. That proves the edge is up, but not that the site works.
A static asset loaded in 164ms. That proves the edge is up, but not that the site works.
A static asset loaded in 161ms. That proves the edge is up, but not that the site works.
A static asset loaded in 98ms. That proves the edge is up, but not that the site works.
A static asset loaded in 281ms. That proves the edge is up, but not that the site works.
A static asset loaded in 139ms. That proves the edge is up, but not that the site works.
A static asset loaded in 219ms. That proves the edge is up, but not that the site works.
A static asset loaded in 104ms. That proves the edge is up, but not that the site works.
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 up to 17 cities across three regions to find out where it breaks.
Related services
Ancestry outage FAQ
Is Ancestry down or is it just my account?
Will I lose family tree edits made during an outage?
Does an Ancestry outage affect DNA results?
Does the Ancestry app work when the website is down?
How we measure this
- We request Ancestry's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means 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 — and when Ancestry blocks our checks entirely, we report the vendor's own status directly.
Get alerted when Ancestry goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring