Fathom outage history

We hold 51 Fathom incidents from Fathom's status page, the newest from Nov 16, 2026. 51 of the 51 listed carry Fathom's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 1d 20h since the last recorded problem.
Operational · 24h
97.92%
0 incidents · no downtime
288 checks
Operational · 7d
83.33%
1 incident · ≈1d 3h degraded
2015 checks
Operational · 30d
95.51%
1 incident · ≈1d 3h degraded
8638 checks
Operational · since Jun 22, 2026
96.69%
4 incidents · ≈2d 20h degraded
41651 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

How Fathom fails

Since Jul 4, 2026, Fathom's status page has marked 11 Fathom components as impaired, across 986 of our five-minute readings. API accounts for the most: 466 readings (about 39 hours) on 3 days, most recently on Nov 7, 2026. Next is In-Call Processing (Google Meet), with 349 readings on 3 days. We hold 51 Fathom incidents from Fathom's status page, the earliest from Oct 17, 2023. Of the 50 that Fathom closed with an end time, the median lasted 1 h 26 min.

ComponentOutageDegradedMaint.DaysLast
API—4664843Nov 7, 2026
In-Call Processing (Google Meet)—3495493Nov 19, 2026
Post-Call Processing—195611Nov 19, 2026
In-Call Processing (Microsoft Teams)—195491Nov 19, 2026
In-Call Processing (Zoom)—195491Nov 19, 2026
Microsoft Calendar Sync—195431Nov 7, 2026
Salesforce—195431Nov 7, 2026
HubSpot—195431Nov 7, 2026

Incidents by month: Mar 2026: 2 · May 2026: 1 · Jun 2026: 1 · Aug 2026: 1 · Sep 2026: 2 · Nov 2026: 1

Counts are five-minute readings of Fathom's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 1

September 2026 · 2

February 2026 · 1

January 2026 · 1

November 2025 · 1

October 2025 · 1

September 2025 · 2

July 2025 · 1

June 2025 · 1

April 2025 · 2

March 2025 · 2

November 2024 · 1

October 2024 · 2

September 2024 · 1

March 2024 · 3

February 2024 · 4

January 2024 · 4

December 2023 · 6

November 2023 · 3

Incidents and their updates are Fathom's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Fathom.