Istoricul incidentelor Bugsnag

1. 1 octombrie 2026 la 14:34 UTCinvestigating

   Ne confruntăm cu probleme cu API-urile şi API-urile şi investigăm problema. Pot exista pierderi de date în indicatorii de performanță în această perioadă, deși SDK-urile de performanță ale BugSnag vor încerca să retrimită date de urmărire și întindere.

2. 1 octombrie 2026 la 20:18 UTCinvestigating

   Am desfăşurat o misiune şi serviciul s-a stabilizat. Vom continua să monitorizăm performanţele sistemului pe măsură ce investigaţia continuă.

3. 2 octombrie 2026 la 18:38 UTCmonitoring

   A fost implementat un fix permanent și serviciile au revenit la funcționarea tipică. Echipa va continua monitorizarea pentru a asigura o performanță consecventă a sistemului.

4. 3 octombrie 2026 la 13:07 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 17:36 UTCinvestigating

   Procesarea sesiunii noastre este în prezent mai lentă din cauza unei întreruperi a serviciului din regiunea GCP, iar raportarea va avea, de asemenea, o latență ridicată. Continuăm să monitorizăm situaţia.

2. 20 august 2026 la 17:57 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 20 august 2026 la 19:57 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 22 ianuarie 2026 la 16:54 UTCinvestigating

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

2. 22 ianuarie 2026 la 18:10 UTCresolved

   This incident has been resolved.

1. 18 noiembrie 2025 la 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 noiembrie 2025 la 17:43 UTCresolved

   This incident has been resolved.

1. 11 noiembrie 2025 la 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 noiembrie 2025 la 08:55 UTCidentified

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

3. 11 noiembrie 2025 la 08:57 UTCmonitoring

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

4. 11 noiembrie 2025 la 09:26 UTCresolved

   This incident has been resolved.

1. 10 noiembrie 2025 la 11:33 UTCidentified

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

2. 10 noiembrie 2025 la 11:38 UTCmonitoring

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

3. 10 noiembrie 2025 la 11:39 UTCresolved

   This incident has been resolved.

1. 7 noiembrie 2025 la 02:59 UTCinvestigating

   We are currently investigating this issue.

2. 7 noiembrie 2025 la 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 noiembrie 2025 la 03:34 UTCinvestigating

   We’re still investigating the root cause.

4. 7 noiembrie 2025 la 09:33 UTCresolved

   This incident has been resolved.

1. 20 octombrie 2025 la 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 octombrie 2025 la 10:59 UTCresolved

   This incident has been resolved.

1. 29 iunie 2025 la 19:15 UTCidentified

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

2. 29 iunie 2025 la 20:04 UTCresolved

   This incident has been resolved.

1. 2 aprilie 2025 la 22:13 UTCinvestigating

   We are currently investigating this issue.

2. 3 aprilie 2025 la 00:53 UTCresolved

   This incident has been resolved.

1. 21 februarie 2025 la 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 februarie 2025 la 20:31 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 februarie 2025 la 22:47 UTCmonitoring

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

4. 21 februarie 2025 la 22:58 UTCresolved

   This incident has been resolved.

1. 16 ianuarie 2025 la 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 decembrie 2024 la 23:12 UTCinvestigating

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

2. 4 decembrie 2024 la 09:39 UTCresolved

   This incident has been resolved

1. 3 decembrie 2024 la 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 octombrie 2024 la 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 octombrie 2024 la 15:45 UTCmonitoring

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

3. 29 octombrie 2024 la 15:50 UTCresolved

   This incident has been resolved.

1. 30 septembrie 2024 la 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 septembrie 2024 la 22:36 UTCresolved

   This incident has been resolved.

1. 30 septembrie 2024 la 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 septembrie 2024 la 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 septembrie 2024 la 16:49 UTCmonitoring

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

3. 19 septembrie 2024 la 17:37 UTCresolved

   This incident has been resolved.

1. 10 septembrie 2024 la 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 la 14:14 UTCinvestigating

   We are currently investigating issues with slow event processing times.

2. 15 august 2024 la 15:47 UTCinvestigating

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

3. 15 august 2024 la 16:31 UTCidentified

   Event information should now be loading on the Dashboard.

4. 15 august 2024 la 20:31 UTCmonitoring

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

5. 15 august 2024 la 21:17 UTCresolved

   This incident has been resolved.