Bugsnag had 6 outages in the last 2 years — averaging 0.2 incidents per month.
There were 6 Bugsnag outages since June 29, 2025. Each is summarised below — incident details, duration, and resolution information.
Jan 22, 18:10 UTC Resolved - This incident has been resolved. Jan 22, 16:54 UTC Investigating - We are currently investigating issues with possible disruption to the BugSnag Error Reporting API.
Nov 18, 17:43 UTC Resolved - This incident has been resolved. Nov 18, 14:40 UTC Identified - Due to a reported global Cloudflare outage, the BugSnag marketing site may currently be inaccessible for some users. This will not impact any BugSnag dashboard functionality or BugSnag APIs. Users can still access the BugSnag dashboard by navigating to app.bugsnag.com
Nov 11, 09:26 UTC Resolved - This incident has been resolved. Nov 11, 08:57 UTC Monitoring - A fix has been implemented and we are monitoring the results. Nov 11, 08:55 UTC Identified - The issue has been identified and a fix has been implemented. Nov 11, 08:49 UTC Investigating - We are currently experiencing some issues with loading errors in the BugSnag dashboard. Users may experience delays when trying to upload and view their errors.
Nov 10, 11:39 UTC Resolved - This incident has been resolved. Nov 10, 11:38 UTC Monitoring - A fix has been implemented and we are monitoring the results. Nov 10, 11:33 UTC Identified - The issue has been identified and a fix is being implemented.
Oct 20, 10:59 UTC Resolved - This incident has been resolved. Oct 20, 10:11 UTC Monitoring - An AWS outage occurred, preventing SmartBear ID logins to the BugSnag dashboard and notification emails from being sent. We are monitoring the situation, but we expect that logins and email notifications will now continue to work as normal. All other functionality remained operational throughout the incident. The AWS incident can be tracked here: https://health.aws.amazon.com/health/status#multipleservices-us-east-1_1760954629
Jun 29, 20:04 UTC Resolved - This incident has been resolved. Jun 29, 19:15 UTC Identified - The issue has been identified and a fix is being implemented.