Fathom Outage History
3 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Fathom Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 16, 2026 | Xero Tracking Categories Update IssueXero have have increased the limit on active and inactive tracking categories included in profit and loss reports, and are continuing to investigate how archived tracking categories are handled. No new incidents are… | 1322h 9m | Resolved |
| Mar 31, 2026 | American Express payment issuesDownstream Payment services providers have been functioning for two weeks without incident. | 2236h 0m | Resolved |
| Mar 24, 2026 | Impacts to paymentsThis incident has been resolved. | 27h 5m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Fathom incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Fathom Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Fathom acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Fathom outage in this window ran 93d 4h, against a mean recovery of 49d 19h. If you depend on Fathom in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.