outages.live
Live
BugsnagIncident · 2026-08-20 17:36 UTC

Sessions processing delays

ResolvedOfficial update

This incident has been resolved.

The latest update from Bugsnag.

State

Resolved

Started

73 d ago

2026-08-20 17:36 UTC

Lasted

2 h 21 min

until 2026-08-20 19:57 UTC

Worst impact

Degraded

Timeline

3 updates
17:3618:1118:4619:2119:57
DegradedUpdate postedTimes in UTC

Investigating

21 min 15%

Monitoring

2 h 85%

Updates

Times in UTC

As posted by Bugsnag

Resolved2026-08-20 19:57 UTC

This incident has been resolved.

Monitoring2026-08-20 17:57 UTC

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

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

Affected components

2
BugSnag DashboardBugSnag Sessions API

Bugsnag in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

4

Median duration

24 h 27 min

This incident

90% shorter than 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·Issues with the Traces and Spans API

This incident has been resolved.

Resolvedresolved 30 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