Bugsnag had 22 outages in the last 2 years totaling 40h 0m of downtime — averaging 0.9 incidents per month.
There were 22 Bugsnag outages since June 4, 2024 totaling 40h 0m of downtime. 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.
We are currently investigating this issue.
This incident has been resolved.
As of 19:49 UTC, we are currently experiencing issues processing received events so there may be a delay before error reports appear in the BugSnag dashboard. We’re still investigating the root cause.
We are continuing to investigate this issue.
Events are processing, but there may still be some delays. We are continuing to monitor this.
This incident has been resolved.
Degraded performance between 17:15 and 17:40 UTC which included a backlog in Unity event processing. Customers may experience delays in integration processing (e.g. webhooks) between 17:15 and 18:02 UTC.
We are currently investigating issues with broken Slack Integration buttons for updating error statuses.
This incident has been resolved
The BugSnag Error Reporting API encountered a small period of increased latency, and an elevated rate of 502 responses between 1:55am - 2:00am UTC on Tuesday, 3rd of December. Events that were attempted to be reported during this time may have been lost, but some notifiers will have retried and successfully reported events that initially failed.
We are currently experiencing an outage. The dashboard may not be accessible and there may be delays to event processing. We are investigating this issue.
The dashboard is now accessible and there may be delays to event processing. We are continuing to monitor this.
This incident has been resolved.
Some mapping files uploaded between 10 and 11 AM UTC may not be available for the symbolication of events. Resolution is underway to make these available and is complete for Proguard, .so mappings, and soon dSYMs. Processing of all affected source maps will take a little longer. Any uploads since 11 AM UTC are not affected.
This incident has been resolved.
From 26/09/2024 10:00 AM UTC to 30/09/2024 10:00 AM UTC there was an issue where one of our services failed to correctly fetch and apply source maps from remote storage. This issue resulted in mapping files not being applied to certain frames in some events.
We are currently experiencing an outage on the BugSnag dashboard, and there may be delays to event processing. We are investigating this.
The BugSnag dashboard is now operational. We are continuing to monitor this.
This incident has been resolved.
We experienced a brief outage, resulting in our release and hooks endpoints returning 5xx response's for a few minutes.
We are currently investigating issues with slow event processing times.
Investigating issues on the Dashboard where event information is not loading.
Event information should now be loading on the Dashboard.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating issues with slow uploads for the BugSnag Upload API. For better performance, you can use BugSnag's https://upload.bugsnag.com/sourcemap or https://upload.bugsnag.com/proguard endpoints for uploading your corresponding mapping files of that type.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue where Integrations and Email notifications with Advanced filters on a Saved filterset are currently unable to be created or saved.
This incident has been resolved.
We are currently investigating an issue with our service provider that means we are unable to send any emails. This affects notification emails, but also sign up and password reset emails. Please bear with us while we resolve this issue.
Our service provider has informed us that they have resolved the issue and will begin processing the email backlog shortly.
We have confirmed that emails are now being delivered. We will continue monitoring the situation.
This incident has been resolved.
Saved Filtersets are unavailable on the BugSnag Dashboard. We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are continuing to monitor.
This incident has been solved. Filtersets should now be appearing in the dashboard
Source map uploads rejected with error code 500
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been solved.