Status.io Outage History
3 incidents recorded over the last 365 days, 1 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 Status.io Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 18, 2026 | Deploy Version 1.9.0Scheduled Maintenance | 30 min | Scheduled |
| Oct 29, 2026 | Deploy Version 1.8.9Scheduled Maintenance | 30 min | Scheduled |
| Oct 22, 2026 | Incorrect Metric Failure NotificationsWe are investigating an issue that caused metric failure email notifications to be sent to some customers this morning. We suspect the issue may be related to our Pingdom metrics integration, but the root cause has… | 5h 55m | 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 Status.io 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 Status.io 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 Status.io 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 Status.io outage in this window ran 5h 55m, against a mean recovery of 2h 18m. If you depend on Status.io 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.