Störungsverlauf von Bugsnag

1. 1. Oktober 2026 um 14:34 UTCinvestigating

   Wir haben Probleme mit der Traces and Spans API und untersuchen die Angelegenheit. Es kann zu Datenverlusten in Ihren Leistungsmetriken in diesem Zeitraum kommen, obwohl die Performance-SDKs von BugSnag das Senden von Trace- und Span-Daten wiederholen.

2. 1. Oktober 2026 um 20:18 UTCinvestigating

   Wir haben einen Workaround implementiert und der Service hat sich stabilisiert. Wir werden die Systemleistung weiterhin überwachen, während die Untersuchung fortgesetzt wird.

3. 2. Oktober 2026 um 18:38 UTCmonitoring

   Ein permanenter Fix wurde implementiert und die Dienste sind in den typischen Betrieb zurückgekehrt. Das Team wird die Überwachung fortsetzen, um eine konsistente Systemleistung sicherzustellen.

4. 3. Oktober 2026 um 13:07 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. August 2026 um 17:36 UTCinvestigating

   Unsere Sitzungsverarbeitung ist derzeit aufgrund eines Ausfalls des GCP-Region-Dienstes langsamer, und die Berichterstattung wird auch eine erhöhte Latenz aufweisen. Wir beobachten die Situation weiter.

2. 20. August 2026 um 17:57 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 20. August 2026 um 19:57 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Januar 2026 um 16:54 UTCinvestigating

   We are currently investigating issues with possible disruption to the BugSnag Error Reporting API.

2. 22. Januar 2026 um 18:10 UTCresolved

   This incident has been resolved.

1. 18. November 2025 um 14:40 UTCidentified

   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

2. 18. November 2025 um 17:43 UTCresolved

   This incident has been resolved.

1. 11. November 2025 um 08:49 UTCinvestigating

   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.

2. 11. November 2025 um 08:55 UTCidentified

   The issue has been identified and a fix has been implemented.

3. 11. November 2025 um 08:57 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 11. November 2025 um 09:26 UTCresolved

   This incident has been resolved.

1. 10. November 2025 um 11:33 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 10. November 2025 um 11:38 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 10. November 2025 um 11:39 UTCresolved

   This incident has been resolved.

1. 7. November 2025 um 02:59 UTCinvestigating

   We are currently investigating this issue.

2. 7. November 2025 um 03:30 UTCinvestigating

   We are currently experiencing some issues with loading errors in the BugSnag dashboard. Users may experience delays when trying to view their errors.

3. 7. November 2025 um 03:34 UTCinvestigating

   We’re still investigating the root cause.

4. 7. November 2025 um 09:33 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 10:11 UTCmonitoring

   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

2. 20. Oktober 2025 um 10:59 UTCresolved

   This incident has been resolved.

1. 29. Juni 2025 um 19:15 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 29. Juni 2025 um 20:04 UTCresolved

   This incident has been resolved.

1. 2. April 2025 um 22:13 UTCinvestigating

   We are currently investigating this issue.

2. 3. April 2025 um 00:53 UTCresolved

   This incident has been resolved.

1. 21. Februar 2025 um 19:57 UTCinvestigating

   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.

2. 21. Februar 2025 um 20:31 UTCinvestigating

   We are continuing to investigate this issue.

3. 21. Februar 2025 um 22:47 UTCmonitoring

   Events are processing, but there may still be some delays. We are continuing to monitor this.

4. 21. Februar 2025 um 22:58 UTCresolved

   This incident has been resolved.

1. 16. Januar 2025 um 18:02 UTCresolved

   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.

1. 3. Dezember 2024 um 23:12 UTCinvestigating

   We are currently investigating issues with broken Slack Integration buttons for updating error statuses.

2. 4. Dezember 2024 um 09:39 UTCresolved

   This incident has been resolved

1. 3. Dezember 2024 um 12:22 UTCresolved

   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.

1. 29. Oktober 2024 um 15:00 UTCinvestigating

   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.

2. 29. Oktober 2024 um 15:45 UTCmonitoring

   The dashboard is now accessible and there may be delays to event processing. We are continuing to monitor this.

3. 29. Oktober 2024 um 15:50 UTCresolved

   This incident has been resolved.

1. 30. September 2024 um 16:03 UTCmonitoring

   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.

2. 30. September 2024 um 22:36 UTCresolved

   This incident has been resolved.

1. 30. September 2024 um 15:42 UTCresolved

   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.

1. 19. September 2024 um 16:19 UTCinvestigating

   We are currently experiencing an outage on the BugSnag dashboard, and there may be delays to event processing. We are investigating this.

2. 19. September 2024 um 16:49 UTCmonitoring

   The BugSnag dashboard is now operational. We are continuing to monitor this.

3. 19. September 2024 um 17:37 UTCresolved

   This incident has been resolved.

1. 10. September 2024 um 08:44 UTCresolved

   We experienced a brief outage, resulting in our release and hooks endpoints returning 5xx response's for a few minutes.

1. 15. August 2024 um 14:14 UTCinvestigating

   We are currently investigating issues with slow event processing times.

2. 15. August 2024 um 15:47 UTCinvestigating

   Investigating issues on the Dashboard where event information is not loading.

3. 15. August 2024 um 16:31 UTCidentified

   Event information should now be loading on the Dashboard.

4. 15. August 2024 um 20:31 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 15. August 2024 um 21:17 UTCresolved

   This incident has been resolved.