- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Bugsnag. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 56m it lasted.
Anything that failed between 2023-11-27 20:33 UTC and 2023-11-27 22:30 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 2
- investigating
We are currently experiencing issues processing received events so there may be a delay before error reports appear in the BugSnag dashboard. The processing delay is currently around 40 minutes. We’re still investigating the root cause.
provider
- 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-d2e9830d26
Is Bugsnag still down?
No, this incident was resolved 2023-11-27 22:30 UTC. For Bugsnag's live state, see https://down.guide/providers/bugsnag.
How long did it last?
1h 56m, from 2023-11-27 20:33 UTC to 2023-11-27 22:30 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.