Bugsnag 中断历史

1. 2026年10月1日 UTC 14:34investigating

   我们正面临追踪和间谍API的问题,并正在调查此事。 这一时期你的性能度量可能存在数据损失,尽管BugSnag的性能SDKs会重新尝试发送痕量并跨出数据.

2. 2026年10月1日 UTC 20:18investigating

   我们已经部署了一个工作 服务已经稳定下来。 随着调查的继续进行,我们将继续监测系统运行情况.

3. 2026年10月2日 UTC 18:38monitoring

   已实施永久固定,服务恢复了典型的运作。 该小组将继续进行监测,以确保系统的业绩一致.

4. 2026年10月3日 UTC 13:07resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月20日 UTC 17:36investigating

   由于GCP区域服务中断,我们的会议处理速度目前较慢,报告工作也将面临更高的延迟。 我们继续监视局势.

2. 2026年8月20日 UTC 17:57monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年8月20日 UTC 19:57resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年1月22日 UTC 16:54investigating

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

2. 2026年1月22日 UTC 18:10resolved

   This incident has been resolved.

1. 2025年11月18日 UTC 14:40identified

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

   This incident has been resolved.

1. 2025年11月11日 UTC 08:49investigating

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

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

3. 2025年11月11日 UTC 08:57monitoring

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

4. 2025年11月11日 UTC 09:26resolved

   This incident has been resolved.

1. 2025年11月10日 UTC 11:33identified

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

2. 2025年11月10日 UTC 11:38monitoring

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

3. 2025年11月10日 UTC 11:39resolved

   This incident has been resolved.

1. 2025年11月7日 UTC 02:59investigating

   We are currently investigating this issue.

2. 2025年11月7日 UTC 03:30investigating

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

3. 2025年11月7日 UTC 03:34investigating

   We’re still investigating the root cause.

4. 2025年11月7日 UTC 09:33resolved

   This incident has been resolved.

1. 2025年10月20日 UTC 10:11monitoring

   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. 2025年10月20日 UTC 10:59resolved

   This incident has been resolved.

1. 2025年6月29日 UTC 19:15identified

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

2. 2025年6月29日 UTC 20:04resolved

   This incident has been resolved.

1. 2025年4月2日 UTC 22:13investigating

   We are currently investigating this issue.

2. 2025年4月3日 UTC 00:53resolved

   This incident has been resolved.

1. 2025年2月21日 UTC 19:57investigating

   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. 2025年2月21日 UTC 20:31investigating

   We are continuing to investigate this issue.

3. 2025年2月21日 UTC 22:47monitoring

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

4. 2025年2月21日 UTC 22:58resolved

   This incident has been resolved.

1. 2025年1月16日 UTC 18:02resolved

   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. 2024年12月3日 UTC 23:12investigating

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

2. 2024年12月4日 UTC 09:39resolved

   This incident has been resolved

1. 2024年12月3日 UTC 12:22resolved

   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. 2024年10月29日 UTC 15:00investigating

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

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

3. 2024年10月29日 UTC 15:50resolved

   This incident has been resolved.

1. 2024年9月30日 UTC 16:03monitoring

   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. 2024年9月30日 UTC 22:36resolved

   This incident has been resolved.

1. 2024年9月30日 UTC 15:42resolved

   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. 2024年9月19日 UTC 16:19investigating

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

2. 2024年9月19日 UTC 16:49monitoring

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

3. 2024年9月19日 UTC 17:37resolved

   This incident has been resolved.

1. 2024年9月10日 UTC 08:44resolved

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

1. 2024年8月15日 UTC 14:14investigating

   We are currently investigating issues with slow event processing times.

2. 2024年8月15日 UTC 15:47investigating

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

3. 2024年8月15日 UTC 16:31identified

   Event information should now be loading on the Dashboard.

4. 2024年8月15日 UTC 20:31monitoring

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

5. 2024年8月15日 UTC 21:17resolved

   This incident has been resolved.