Bugsnag reported "Issues with the Traces and Spans API" on its status page at 2026-10-01 14:34 UTC.

Bugsnag lists these components: BugSnag OTLP Trace Reporting API.

When did the incident start and end?

It started at 2026-10-01 14:34 UTC and ended at 2026-10-03 13:07 UTC. It lasted 46 h 33 min.

How do I get alerts for Bugsnag?

Subscribe to the Bugsnag live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Bugsnag. outages.live reads it every few minutes and keeps every update.

BugsnagIncident · 2026-10-01 14:34 UTC

Issues with the Traces and Spans API

ResolvedOfficial update

This incident has been resolved.

The latest update from Bugsnag.

State

Resolved

Started

31 d ago

2026-10-01 14:34 UTC

Lasted

46 h 33 min

until 2026-10-03 13:07 UTC

Worst impact

Degraded

Timeline

4 updates

Oct 1Oct 2Oct 2Oct 3Oct 3

DegradedUpdate postedDates in UTC

Investigating

28 h 4 min 60%

Monitoring

18 h 29 min 40%

Updates

Times in UTC

As posted by Bugsnag

Resolved2026-10-03 13:07 UTC

This incident has been resolved.

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

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

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

Affected components

BugSnag OTLP Trace Reporting API

Bugsnag in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

24 h 27 min

This incident

1.9× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

46 h 33 min

median 24 h 27 min

90 days agoToday

Other Bugsnag incidents

All incidents

Bugsnag·Sessions processing delays

This incident has been resolved.

Resolvedresolved 73 d ago

Follow Bugsnag

Your coding agent knows when Bugsnag is down, and tells you when a failure is theirs, not yours. You can also get Bugsnag incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "bugsnag" and tell me if Bugsnag has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=bugsnag

Slack

/feed subscribe https://outages.live/feed.xml?providers=bugsnag

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane