Airbrake Outage History
4 incidents recorded over the last 365 days, 4 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 Airbrake Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Partial error graph outageWe identified and addressed an infrastructure issue that was impacting service availability. Service has been restored, and we are continuing to monitor system health while working on additional measures to prevent… | 49 min | Resolved |
| Jul 13, 2026 | Metric graphs not loadingThe incident has been resolved and metrics are back online. There will be a dip in metric count graphs while the incident was experienced. Error event data was recorded normally and was unaffected. We apologize for the… | 12h 14m | Resolved |
| Jun 1, 2026 | Email notificationsWe've resolved an issue with our email notifications. The issue was caused by email asset delivery which we've resolved. We apologize for any inconvenience. Please email support at support@airbrake.io if you have any… | 1h 30m | Resolved |
| May 6, 2026 | Error dashboard loading issuesA subset of customers experienced an issue where the error dashboard list was not loading properly. This may have resulted in error filtering being faulty or the errors list being blank. The issue was escalated to our… | 0 min | 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 Airbrake 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 Airbrake 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 Airbrake 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 Airbrake outage in this window ran 12h 14m, against a mean recovery of 3h 38m. If you depend on Airbrake 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.