Skip to main content
Bugsnag

Sessions processing delays

Degraded Lasted 2h 21m · started · Bugsnag's page

Level
confirmed
Worst impact
Degraded
Components
BugSnag Dashboard, BugSnag Sessions API
Down Index
25of 100

What to do

  • Check whether you use Bugsnag BugSnag Dashboard, BugSnag Sessions API. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 21m it lasted.

    Anything that failed between 2026-08-20 17:36 UTC and 2026-08-20 19:57 UTC may need a replay.
  • Subscribe to Bugsnag's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=bugsnag works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Bugsnag 3

  1. investigating

    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.

    provider

  2. monitoring

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

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5ebd60313d

Is Bugsnag still down?

No, this incident was resolved 2026-08-20 19:57 UTC. For Bugsnag's live state, see https://down.guide/bugsnag.

How long did it last?

2h 21m, from 2026-08-20 17:36 UTC to 2026-08-20 19:57 UTC, by the times Bugsnag posted.

What was affected?

Bugsnag named BugSnag Dashboard, BugSnag Sessions API.

What caused it?

Bugsnag hasn't published a root cause. If it does, it shows here.

Where does this come from?

Bugsnag's official status page, https://bugsnag.status.smartbear.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.