Fastmail Outage History

6 incidents recorded over the last 365 days, 6 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.

Live Fastmail status100.00% uptime history

Every Recorded Fastmail Incident

Fastmail incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Support emails not generating tickets1h 30mResolved
Oct 7, 2026Interrupted access to Fastmail services5h 26mResolved
Oct 5, 2026Support emails not generating tickets55h 46mResolved
Sep 23, 2026Replies sent using masked email addresses are bouncing11h 15mResolved
Sep 4, 2026Interrupted access to Fastmail services1h 13mResolved
Aug 25, 2026Interrupted access to Fastmail services8h 20mResolved

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 Fastmail 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 Fastmail 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 Fastmail 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 Fastmail outage in this window ran 2d 7h, against a mean recovery of 13h 55m. If you depend on Fastmail 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.