- 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 46m it lasted.
Anything that failed between 2024-01-24 09:37 UTC and 2024-01-24 10:23 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 have been experiencing an outage to our emails since 01:56 AM UTC resulting in emails not being sent and are investigating the cause.
provider
- resolved
This incident has been resolved. Unfortunately all emails that would have been delivered during this outage have been lost - please accept our apologies for any inconvenience caused by this. BugSnag uses a third-party supplier to deliver emails. That supplier had temporarily suspended our account and they have acknowledged that this was due to a false positive with their internal tooling. Please rest assured that we are taking steps to ensure this does not happen again in the future.
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-d30665d5dd
Is Bugsnag still down?
No, this incident was resolved 2024-01-24 10:23 UTC. For Bugsnag's live state, see https://down.guide/providers/bugsnag.
How long did it last?
46m, from 2024-01-24 09:37 UTC to 2024-01-24 10:23 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.