Is Ancestry down?
Checks passingchecked 5 minutes ago
Our checks of Ancestry pass from all 4 regions we check.
As of Nov 5, 2026, 3:37 PM UTC, RealUptime's checks of Ancestry passed in all 4 regions that returned a reading.
Ancestry's last published incident: "Customers may be experiencing issues at this time. Investigation underway.", Nov 2, 2026, 38 min. their claim, not our reading
Our checks of Ancestry did not fail from two or more distant regions in the 3 days we have checked it (since Nov 2, 2026). This does not show Ancestry works for users.
Email me when our checks of Ancestry fail from two or more distant regions
Ancestry reports: All systems operational (“All Systems Operational”)
Ancestry's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)
- Login ProcessesOperational
- Home PageOperational
- Family Tree FeaturesOperational
- DNA-related FeaturesOperational
- Search FunctionalityOperational
- Hint-related FunctionalityOperational
- Shopping CartOperational
- Mobile ApplicationsOperational
These are Ancestry's components, named and scored by Ancestry. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Ancestry's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Ancestry published 1 incident in the last 30 days. In the same period our checks failed from two or more distant regions 0 times.
Ancestry response time, by region
Check your own site while you wait on Ancestry
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Ancestry. It cannot diagnose Ancestry's own systems.
What our checks show, and what people reported
- North AmericaNot monitored from this regionUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 6msstatus code: nonechecked: Nov 5, 2026, 3:34 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Ancestry normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 17msstatus code: nonechecked: Nov 5, 2026, 3:30 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Ancestry normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralNot monitored from this regionAncestry is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionAncestry is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionAncestry is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- EuropeNot monitored from this regionEurope, UK
- EuropeChecks passinglatency: 21msstatus code: nonechecked: Nov 5, 2026, 3:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Ancestry normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKNot monitored from this regionAncestry is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Asia PacificNot monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 12msstatus code: nonechecked: Nov 5, 2026, 3:37 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Ancestry normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaNot monitored from this regionAncestry is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionAncestry is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Ancestry, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Ancestry yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Ancestry since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Ancestry covering any window you pick, with our check readings and Ancestry's own claim at the time, side by side.
Full check history for Ancestry: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/ancestry-com)<a href="https://realuptime.io/outages/ancestry-com"><img src="https://realuptime.io/outages/ancestry-com/badge.svg?days=30" alt="Ancestry uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Ancestry down?", https://realuptime.io/outages/ancestry-com. The readings change with every check, so give the date you read them.
How our checks compare with Ancestry's stated SLA
At or above your target
Our checks of Ancestry failed for none over the 67h 37m since we started checking it on 2026-11-02, which is 100% uptime by our checks. A 99.9% target allows 4 minutes over that period.
Our checks show no gap in this period. That does not rule out one you saw.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Ancestry's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.
What we check
What our check can and cannot see
A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.
Host checked: www.ancestry.com