Ancestry outages and problems
In the past 24 hours, 13 user reports came in for Ancestry. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 2 reports, about 19 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Ancestry in October 2026
- Problem reports in October (since 28 October)
- 13
Monthly report for October 2026
What went wrong
What people said was wrong in recent problem reports for Ancestry worldwide.
Share of 7 recent reports that said what was wrong, from every country listed below.
Ancestry reports around the world
In the last 24 hours, 27 problem reports about Ancestry came in from 5 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 0 | 13 |
| The UK | Normal | 0 | 5 |
| Canada | Normal | 0 | 4 |
| Germany | Normal | 0 | 4 |
| Ireland | Normal | 0 | 1 |
| Australia | Normal | 0 | 0 |
| New Zealand | Normal | 0 | 0 |
Each country's status compares its reports with the usual level there. Map outlines: Natural Earth.
Ancestry problem spikes, last 30 days
Since 28 October, Ancestry had no outage spikes or periods of elevated reports.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 28 October 2026. Monthly reports for all services
How to fix Ancestry not working
Ancestry is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach ancestry.com over your own connection, right now. Nothing is sent to us or stored.
Open a private browser window
Open a private browser window and sign in again: in Chrome use the three-dot menu > New Incognito window, and in Safari use File > New Private Window. If the tree or DNA page loads there, your normal browser profile is the likely cause; if it fails, check the status note at the top of this page, which counts user problem reports in 15-minute windows over the last 24 hours and does not test the service.
Clear site data for Ancestry
In Chrome, open Settings > Privacy and security > Delete browsing data, select Cookies and other site data and Cached images and files, then set the time range to All time. That clears other sites too. Sign back in to the service and retry the page that failed.
Update the app and allow photos
On iPhone, open Settings > Ancestry > Photos and choose the access level that lets the app upload images; on Android, open Settings > Apps > Ancestry > Permissions and allow Photos and videos or Files and media. Install the latest app update from the App Store or Google Play, then sign out and back in.
Reinstall the app after signing out
Restart the phone or tablet, sign out in the app, delete the app, then install it again from the App Store or Google Play. If the same page fails in a private browser window on another Wi-Fi or cellular connection, the problem is tied to your account or that specific record.
While Ancestry is down: what to use instead
- Ancestry website Use the browser version when the mobile app stalls or will not open a record.
- FamilySearch Search its records and shared tree when you need a lookup and the app will not load a page.
- Findmypast Try its record collections when you need a census or parish search and the site is not responding.
- MyHeritage Use its tree and DNA match tools when you need to review family connections and the app will not open.
What happens when Ancestry goes down
Ancestry is a genealogy service for building family trees and searching historical records, and it draws people who want to trace a line or check a DNA match. An outage cuts off the record you were searching, the tree you were editing, the source you were saving, and the DNA results you opened to make sense of a branch.
Record search often fails first: the search page loads, but results stall or the record viewer never opens, so you cannot save a source to your tree. The family tree can still show cached pages, yet edits and new people may not save, and the mobile app may sit on a loading screen or show a connection error. DNA pages are hit or miss; matches and ethnicity results may load slowly or fail while the rest of the site works. Outages tend to be partial: one record collection or the tree editor can break while the app and other pages stay reachable, and reports cluster by region when a network path is the cause.
Ancestry IP address, servers and network
Checking ancestry.com from our server…
Ancestry FAQ
Is Ancestry down right now?
Why does the Ancestry app close when I open my family tree?
Why are my AncestryDNA results missing from my account?
Why did my Ancestry subscription renew after I cancelled it?
Why do Ancestry record hints stop loading on my tree?
Service updates from @ancestry
No posts about problems from @ancestry in the last 14 days. The latest is from .
Put the Ancestry status badge on your site
Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.
<a href="https://isitdownrightnow.app/services/ancestry/"><img src="https://isitdownrightnow.app/badge/ancestry.svg" alt="Ancestry status" height="20"></a>[](https://isitdownrightnow.app/services/ancestry/)The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.
How we track Ancestry
The status on this page comes from user-submitted problem reports for Ancestry, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Ancestry, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Ancestry doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.