- 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 2024-03-01 23:33 UTC and 2024-03-01 20:00 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
We experienced a spike in traffic between 19:47 UTC and 19:51 UTC, which caused issues with the Error Reporting API. There may be gaps in your events for this time period, although some platform specific notifiers will retry sending events.
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-e7101ea9b0
Is Bugsnag still down?
No, this incident was resolved 2024-03-01 20:00 UTC. For Bugsnag's live state, see https://down.guide/bugsnag.
How long did it last?
0m, from 2024-03-01 23:33 UTC to 2024-03-01 20:00 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.