Bugsnag Outage History

8 incidents recorded over the last 365 days, 7 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 Bugsnag status100.00% uptime history

Every Recorded Bugsnag Incident

Bugsnag incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 1, 2026Issues with the Traces and Spans APIThis incident has been resolved.46h 33mResolved
Aug 20, 2026Sessions processing delaysThis incident has been resolved.2h 20mResolved
Jul 25, 2026SmartBear ID MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jan 22, 2026Issues with the BugSnag Error Reporting APIThis incident has been resolved.1h 15mResolved
Nov 18, 2025BugSnag Marketing Site DownThis incident has been resolved.3h 2mResolved
Nov 11, 2025Issues with BugSnag DashboardThis incident has been resolved.36 minResolved
Nov 10, 2025Some uploads are failing with a 403 forbidden error messageThis incident has been resolved.5 minResolved
Nov 7, 2025Issues with BugSnag DashboardThis incident has been resolved.6h 2mResolved

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 Bugsnag 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 Bugsnag 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 Bugsnag 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 Bugsnag outage in this window ran 1d 22h, against a mean recovery of 7h 59m. If you depend on Bugsnag 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.