Historial de interrupciones de Bugsnag

1. 1 de octubre de 2026 a las 14:34 UTCinvestigating

   Estamos experimentando problemas con la API de Traces y Spans y estamos investigando el asunto. Puede haber pérdida de datos en sus métricas de rendimiento durante este período, aunque los SDKs de rendimiento de BugSnag retratarán el envío de datos de seguimiento y extensión.

2. 1 de octubre de 2026 a las 20:18 UTCinvestigating

   Hemos desplegado una ronda de trabajo y el servicio se ha estabilizado. Seguiremos monitoreando el desempeño del sistema mientras continúe la investigación.

3. 2 de octubre de 2026 a las 18:38 UTCmonitoring

   Se ha aplicado un arreglo permanente y los servicios han regresado a la operación típica. El equipo seguirá vigilando a fin de garantizar el desempeño constante del sistema.

4. 3 de octubre de 2026 a las 13:07 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 20 de agosto de 2026 a las 17:36 UTCinvestigating

   Nuestro proceso de sesión es actualmente más lento debido a la eliminación de servicios de la Región GCP, y la presentación de informes también experimentará latencia elevada. Continuamos monitoreando la situación.

2. 20 de agosto de 2026 a las 17:57 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 20 de agosto de 2026 a las 19:57 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de enero de 2026 a las 16:54 UTCinvestigating

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

2. 22 de enero de 2026 a las 18:10 UTCresolved

   This incident has been resolved.

1. 18 de noviembre de 2025 a las 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 de noviembre de 2025 a las 17:43 UTCresolved

   This incident has been resolved.

1. 11 de noviembre de 2025 a las 8: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 de noviembre de 2025 a las 8:55 UTCidentified

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

3. 11 de noviembre de 2025 a las 8:57 UTCmonitoring

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

4. 11 de noviembre de 2025 a las 9:26 UTCresolved

   This incident has been resolved.

1. 10 de noviembre de 2025 a las 11:33 UTCidentified

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

2. 10 de noviembre de 2025 a las 11:38 UTCmonitoring

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

3. 10 de noviembre de 2025 a las 11:39 UTCresolved

   This incident has been resolved.

1. 7 de noviembre de 2025 a las 2:59 UTCinvestigating

   We are currently investigating this issue.

2. 7 de noviembre de 2025 a las 3: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 de noviembre de 2025 a las 3:34 UTCinvestigating

   We’re still investigating the root cause.

4. 7 de noviembre de 2025 a las 9:33 UTCresolved

   This incident has been resolved.

1. 20 de octubre de 2025 a las 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 de octubre de 2025 a las 10:59 UTCresolved

   This incident has been resolved.

1. 29 de junio de 2025 a las 19:15 UTCidentified

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

2. 29 de junio de 2025 a las 20:04 UTCresolved

   This incident has been resolved.

1. 2 de abril de 2025 a las 22:13 UTCinvestigating

   We are currently investigating this issue.

2. 3 de abril de 2025 a las 0:53 UTCresolved

   This incident has been resolved.

1. 21 de febrero de 2025 a las 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 de febrero de 2025 a las 20:31 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 de febrero de 2025 a las 22:47 UTCmonitoring

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

4. 21 de febrero de 2025 a las 22:58 UTCresolved

   This incident has been resolved.

1. 16 de enero de 2025 a las 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 de diciembre de 2024 a las 23:12 UTCinvestigating

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

2. 4 de diciembre de 2024 a las 9:39 UTCresolved

   This incident has been resolved

1. 3 de diciembre de 2024 a las 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 de octubre de 2024 a las 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 de octubre de 2024 a las 15:45 UTCmonitoring

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

3. 29 de octubre de 2024 a las 15:50 UTCresolved

   This incident has been resolved.

1. 30 de septiembre de 2024 a las 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 de septiembre de 2024 a las 22:36 UTCresolved

   This incident has been resolved.

1. 30 de septiembre de 2024 a las 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 de septiembre de 2024 a las 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 de septiembre de 2024 a las 16:49 UTCmonitoring

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

3. 19 de septiembre de 2024 a las 17:37 UTCresolved

   This incident has been resolved.

1. 10 de septiembre de 2024 a las 8:44 UTCresolved

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

1. 15 de agosto de 2024 a las 14:14 UTCinvestigating

   We are currently investigating issues with slow event processing times.

2. 15 de agosto de 2024 a las 15:47 UTCinvestigating

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

3. 15 de agosto de 2024 a las 16:31 UTCidentified

   Event information should now be loading on the Dashboard.

4. 15 de agosto de 2024 a las 20:31 UTCmonitoring

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

5. 15 de agosto de 2024 a las 21:17 UTCresolved

   This incident has been resolved.