- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Bugsnag. 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 0m it lasted.
Anything that failed between 2025-01-16 17:15 UTC and 2025-01-16 17:15 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 1
- resolved
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.
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-53ab100d33
Is Bugsnag still down?
No, this incident was resolved 2025-01-16 17:15 UTC. For Bugsnag's live state, see https://down.guide/bugsnag.
How long did it last?
0m, from 2025-01-16 17:15 UTC to 2025-01-16 17:15 UTC, by the times Bugsnag posted.
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.