Is Ancestry down in the US?
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Ancestry at Nov 5, 2026, 4:56 PM UTC.
Over the last 24 hours we completed 250 checks from Ashburn and San Jose and 250 answered cleanly, 100.00% availability.
Of the 2 other regions we check Ancestry from, all 2 read checks passing right now.
Email me the next time we see Ancestry go down
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 4:56 PM UTC.
Ancestry from Ashburn and San Jose over the last 30 days
Over the last 30 days, Ancestry answered our Ashburn probe in 59 ms on average, and 1 check in 20 took longer than 142 ms.
Over the last 30 days, Ancestry answered our San Jose probe in 101 ms on average, and 1 check in 20 took longer than 170 ms.
Ranked by average response time across the 4 cities we check Ancestry from, Ashburn 3rd, San Jose 4th; Frankfurt was fastest at 12 ms and San Jose slowest at 101 ms.
From Ashburn and San Jose we ran 777 checks of Ancestry in 4 days, and 715 answered cleanly: 92.02% availability.
1 of the 4 days had at least one failed check. The weakest was Nov 2 (UTC), at 41.50% across 106 checks.
In Ashburn local time (EST), Ancestry was slowest around 12 PM, at 95 ms on average over the last 14 days, and quickest around 4 AM, at 19 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 175 | 100.00% | 10 ms |
| Wed, Nov 4 | 250 | 100.00% | 32 ms |
| Tue, Nov 3 | 246 | 100.00% | 149 ms |
| Mon, Nov 2 | 106 | 41.50% | 129 ms |
Ancestry outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Ancestry outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Ancestry from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 98 checks |
| Tokyo | Checks passing | 100.00% of 59 checks |
Other countries we check Ancestry from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Ancestry's public endpoints. They are not user reports, and they are not Ancestry's own status page.
See Ancestry's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Ancestry has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter