Fathomstatus history & uptime
How reliable has Fathombeen? We record a status check every few minutes and keep the history — uptime, recent incidents, and the upstream providers whose outages cascade here. We never invent numbers; where we're still collecting, we say so.
Uptime & history
Tracking since Jun 22, 2026Currently up for 28d 9h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
99.45%
0 incidents · no downtime
2016 checks
Operational · 30d
99.37%
2 incidents · ≈1h 35m degraded
8639 checks
Operational · since Jun 22, 2026
97.66%
3 incidents · ≈1d 16h degraded
27145 checks
% of our checks that found Fathom fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.
Recent checks
oldernow
Past incidents
- Some calls slow to start and processSep 21, 2026 · ongoing · monitoring
- GCP incident impacting application connectivity and performanceSep 1, 2026 · ongoing · identified
- List meetings endpoint returns an error when the calendar_invitees_domains parameter is providedAug 13, 2026 · ongoing · identified
History is recorded from Fathom's official status plus our own independent checks. AIDownCheck is independent and not affiliated with Fathom.