Is Findmypast down?
Checks passingchecked 2 minutes ago
Our checks of Findmypast pass from all 4 regions we check.
As of Nov 5, 2026, 4:46 PM UTC, RealUptime's checks of Findmypast passed in all 4 regions that returned a reading.
Our checks of Findmypast 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 Findmypast works for users.
Email me when our checks of Findmypast fail from two or more distant regions
Findmypast publishes no status feed we can read, so the only reading here is our check reading on the left.
Findmypast response time, by region
Check your own site while you wait on Findmypast
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 Findmypast. It cannot diagnose Findmypast'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: 1014msstatus code: 200checked: Nov 5, 2026, 4:40 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Findmypast normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1420msstatus code: 200checked: Nov 5, 2026, 4:46 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Findmypast normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralNot monitored from this regionFindmypast is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionFindmypast is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionFindmypast 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: 13msstatus code: nonechecked: Nov 5, 2026, 4:40 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Findmypast normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKNot monitored from this regionFindmypast 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: 10msstatus code: nonechecked: Nov 5, 2026, 4:35 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Findmypast normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaNot monitored from this regionFindmypast is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionFindmypast 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 Findmypast, 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 Findmypast yet, which is not evidence that nothing is wrong.
Recent probe events
No probe events on record yet for Findmypast.
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Findmypast 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 Findmypast covering any window you pick, with our check readings and Findmypast's own claim at the time, side by side.
Full check history for Findmypast: 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/findmypast)<a href="https://realuptime.io/outages/findmypast"><img src="https://realuptime.io/outages/findmypast/badge.svg?days=30" alt="Findmypast 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 Findmypast down?", https://realuptime.io/outages/findmypast. The readings change with every check, so give the date you read them.
How our checks compare with Findmypast's stated SLA
At or above your target
Our checks of Findmypast failed for none over the 74h 35m 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 Findmypast'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.findmypast.com