- 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 0m it lasted.
Anything that failed between 2023-12-01 13:32 UTC and 2023-12-01 13:32 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
Emails sent from bugsnag.com between 10:30 UTC on 30th November and 13:00 UTC on 1st December may contain broken links. For collaborator invite emails with broken links, please reach out to your BugSnag organisation administrator to resend the invite from the BugSnag dashboard.
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-8bcf35c06c
Is Bugsnag still down?
No, this incident was resolved 2023-12-01 13:32 UTC. For Bugsnag's live state, see https://down.guide/providers/bugsnag.
How long did it last?
0m, from 2023-12-01 13:32 UTC to 2023-12-01 13:32 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.