Bugsnag

Affected: BugSnag OTLP Trace Reporting API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 14:34 UTC

   We are experiencing issues with the Traces and Spans API and are investigating the matter. There may be data loss in your performance metrics during this period, although BugSnag's Performance SDKs will retry sending trace and span data.

2. investigating 2026-10-01 20:18 UTC

   We've deployed a workaround and the service has stabilized. We'll continue to monitor system performance as the investigation continues.

3. monitoring 2026-10-02 18:38 UTC

   A permanent fix has been implemented and services have returned to typical operation. The team will continue monitoring to ensure consistent system performance.

4. resolved 2026-10-03 13:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Dashboard, BugSnag Sessions API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. investigating 2026-08-20 17:36 UTC

   Our session processing is currently slower because of a GCP Region service outage, and reporting will also experience elevated latency. We’re continuing to monitor the situation.

2. monitoring 2026-08-20 17:57 UTC

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

3. resolved 2026-08-20 19:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Error Reporting API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-22 16:54 UTC

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

2. resolved 2026-01-22 18:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 14:40 UTC

   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. resolved 2025-11-18 17:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Dashboard, BugSnag Error Reporting API, BugSnag Sessions API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-11 08:49 UTC

   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. identified 2025-11-11 08:55 UTC

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

3. monitoring 2025-11-11 08:57 UTC

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

4. resolved 2025-11-11 09:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Upload API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-10 11:33 UTC

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

2. monitoring 2025-11-10 11:38 UTC

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

3. resolved 2025-11-10 11:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Dashboard, BugSnag Error Reporting API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-07 02:59 UTC

   We are currently investigating this issue.

2. investigating 2025-11-07 03:30 UTC

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

3. investigating 2025-11-07 03:34 UTC

   We’re still investigating the root cause.

4. resolved 2025-11-07 09:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-10-20 10:11 UTC

   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...

2. resolved 2025-10-20 10:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-06-29 19:15 UTC

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

2. resolved 2025-06-29 20:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Error Reporting API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-02 22:13 UTC

   We are currently investigating this issue.

2. resolved 2025-04-03 00:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Error Reporting API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-21 19:57 UTC

   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. investigating 2025-02-21 20:31 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-02-21 22:47 UTC

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

4. resolved 2025-02-21 22:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-01-16 17:15 UTC

   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.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-03 23:12 UTC

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

2. resolved 2024-12-04 09:39 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-12-03 01:55 UTC

   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...

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Dashboard, BugSnag Error Reporting API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-29 15:00 UTC

   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. monitoring 2024-10-29 15:45 UTC

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

3. resolved 2024-10-29 15:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Upload API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-09-30 16:03 UTC

   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....

2. resolved 2024-09-30 22:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-09-25 22:00 UTC

   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.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-19 16:19 UTC

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

2. monitoring 2024-09-19 16:49 UTC

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

3. resolved 2024-09-19 17:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-09-07 10:30 UTC

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

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-15 14:14 UTC

   We are currently investigating issues with slow event processing times.

2. investigating 2024-08-15 15:47 UTC

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

3. identified 2024-08-15 16:31 UTC

   Event information should now be loading on the Dashboard.

4. monitoring 2024-08-15 20:31 UTC

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

5. resolved 2024-08-15 21:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-12 17:18 UTC

   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.

2. monitoring 2024-08-12 19:08 UTC

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

3. resolved 2024-08-12 19:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-09 13:55 UTC

   We are currently investigating issues with availability of the upload API.

2. resolved 2024-08-09 15:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-08-09 08:30 UTC

   Intermittent issues with availability of Upload API

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-08-08 22:00 UTC

   There was an issue with the BugSnag Upload API between 22:20 UTC and 22:25 UTC.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-24 20:12 UTC

   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.

2. resolved 2024-06-24 22:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-06-09 14:10 UTC

   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.

2. identified 2024-06-09 15:21 UTC

   Our service provider has informed us that they have resolved the issue and will begin processing the email backlog shortly.

3. monitoring 2024-06-09 15:31 UTC

   We have confirmed that emails are now being delivered. We will continue monitoring the situation.

4. resolved 2024-06-09 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-06 16:07 UTC

   Saved Filtersets are unavailable on the BugSnag Dashboard. We are currently investigating this issue.

2. identified 2024-06-06 16:39 UTC

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

3. monitoring 2024-06-06 16:40 UTC

   A fix has been implemented and we are continuing to monitor.

4. resolved 2024-06-06 16:43 UTC

   This incident has been solved. Filtersets should now be appearing in the dashboard

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-04 15:11 UTC

   Source map uploads rejected with error code 500

2. identified 2024-06-04 15:57 UTC

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

3. monitoring 2024-06-04 16:12 UTC

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

4. resolved 2024-06-04 16:22 UTC

   This incident has been solved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-05-16 23:37 UTC

   We are currently investigating this issue.

2. resolved 2024-05-17 00:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Affected: BugSnag Dashboard, BugSnag Data Access API, BugSnag OTLP Trace Reporting API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-14 02:46 UTC

   We are currently investigating this issue.

2. monitoring 2024-05-14 04:51 UTC

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

3. monitoring 2024-05-14 04:53 UTC

   We are continuing to monitor for any further issues.

4. resolved 2024-05-14 05:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-16 15:06 UTC

   There is a backlog of Unity and Default events to be processed and we are currently monitoring this.

2. monitoring 2024-04-16 15:18 UTC

   The Default backlog has been processed. We are still processing a backlog of Unity events and continue to monitor this.

3. resolved 2024-04-16 15:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-03 15:49 UTC

   There is a backlog of Unity events to be processed and we are currently monitoring this.

2. resolved 2024-04-03 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-03-26 16:00 UTC

   We experienced issues with the Traces and Spans API between 15:43 UTC and 16:00 UTC. There may be data loss in your performance metrics for this time period, although BugSnag's Performance SDKs will retry sending trace and span data.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-03-01 20:00 UTC

   We experienced a spike in traffic between 19:47 UTC and 19:51 UTC, which caused issues with the Error Reporting API. There may be gaps in your events for this time period, although some platform specific notifiers will retry sending events.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-27 19:00 UTC

   We're currently experiencing delays in event processing for React Native events. We're investigating this issue.

2. resolved 2024-02-27 19:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-23 14:09 UTC

   There may be a delay in processing for Unity events, and potentially some slow responses from the notify API endpoint. We are currently investigating this issue.

2. resolved 2024-02-23 15:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-08 20:19 UTC

   We are currently experiencing a delay in the processing of Unity events. We expect this to be resolved shortly.

2. resolved 2024-02-08 20:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-08 00:46 UTC

   We're currently experiencing delays in event processing for Android events. We're investigating this issue.

2. monitoring 2024-02-08 03:53 UTC

   We are processing events as normal, however some events that occurred between 00:20 UTC and 02:16 UTC may not yet be visible on your dashboard. We expect this to be resolved in the next few hours.

3. resolved 2024-02-08 09:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-01-29 16:37 UTC

   We are currently experiencing issues processing received events so there may be a delay before error reports appear in the BugSnag dashboard.

2. resolved 2024-01-29 18:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-01-24 09:37 UTC

   We have been experiencing an outage to our emails since 01:56 AM UTC resulting in emails not being sent and are investigating the cause.

2. resolved 2024-01-24 10:23 UTC

   This incident has been resolved. Unfortunately all emails that would have been delivered during this outage have been lost - please accept our apologies for any inconvenience caused by this. BugSnag uses a third-party supplier to deliver emails. That supplier had temporarily...

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-12-19 18:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-12-01 13:32 UTC

   Emails sent from bugsnag.com between 10:30 UTC on 30th November and 13:00 UTC on 1st December may contain broken links. For collaborator invite emails with broken links, please reach out to your BugSnag organisation administrator to resend the invite from the BugSnag dashboard.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-11-27 20:33 UTC

   We are currently experiencing issues processing received events so there may be a delay before error reports appear in the BugSnag dashboard. The processing delay is currently around 40 minutes. We’re still investigating the root cause.

2. resolved 2023-11-27 22:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-11-09 16:13 UTC

   We're currently experiencing delays in event processing for React Native events. We're investigating this issue.

2. resolved 2023-11-09 17:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-09-01 19:33 UTC

   We are currently investigating this issue.

2. resolved 2023-09-01 20:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-08-28 17:27 UTC

   We are currently investigating this issue.

2. resolved 2023-08-28 18:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2023-08-10 15:16 UTC

   We are currently experiencing a small delay in processing of Unity events. We expect this to be resolved shortly.

2. resolved 2023-08-10 15:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-02 09:26 UTC

   We are aware of some issues with symbolication failure. This may cause some events not to symbolicate correctly and create new groupings. We are investigating.

2. resolved 2023-08-02 15:00 UTC

   This issue will have affected mapping files uploaded between 09:32 UTC yesterday and 13:00 UTC today, causing any events relying on those source maps to not symbolicate properly and create new groupings. This is now resolved, so any uploaded mapping files, including those...

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-19 15:39 UTC

   We are currently investigating this issue.

2. resolved 2023-07-19 16:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2023-05-23 14:53 UTC

   We are currently investigating this issue. Customers may experience errors uploading some types of mapping files to our upload.bugsnag.com endpoints, including JavaScript/React Native source maps, Breakpad files, NDK symbols, Dart Symbols and Nintendo Switch symbols.

2. monitoring 2023-05-23 18:59 UTC

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

3. resolved 2023-05-23 19:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bugsnag's status page.