Honeybadger.io 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 Honeybadger.io Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 15, 2026 | Elevated failure rates on the US error reporting APIBetween 19:54 and 20:07 UTC on August 15, requests to our US error reporting API (api.honeybadger.io) experienced an elevated failure rate. During this window, a majority of requests to submit errors and events timed… | 0 min | Resolved |
| Jul 8, 2026 | Elevated error rates on the US error reporting APIBetween 06:22 and 08:23 UTC on July 8, requests to our US error reporting API (api.honeybadger.io) experienced a highly elevated failure rate. During this window, a majority of requests to submit errors, events, and… | 0 min | Resolved |
| Mar 12, 2026 | Delays with notificationsWe had a backlog in our notifications queue that prevented timely delivery of alerts to channels such as Email, Slack, etc. The backlog has been processed as of 19:20 UTC. Our autoscaling rules for this service had a… | 0 min | Resolved |
| Jan 14, 2026 | Outage in check-in processingThis incident has been resolved. | 7 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 Honeybadger.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 Honeybadger.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 Honeybadger.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 Honeybadger.io outage in this window ran 7 min, against a mean recovery of 2 min. If you depend on Honeybadger.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.