- Level
- confirmed
- Worst impact
- Degraded
- Components
- BugSnag Error Reporting API
- Down Index
- 23of 100
What to do
Check whether you use Bugsnag BugSnag Error Reporting API. 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 3h 1m it lasted.
Anything that failed between 2025-02-21 19:57 UTC and 2025-02-21 22:58 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 4
- investigating
As of 19:49 UTC, we are currently experiencing issues processing received events so there may be a delay before error reports appear in the BugSnag dashboard. We’re still investigating the root cause.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
Events are processing, but there may still be some delays. We are continuing to monitor this.
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-7613fc704f
Is Bugsnag still down?
No, this incident was resolved 2025-02-21 22:58 UTC. For Bugsnag's live state, see https://down.guide/bugsnag.
How long did it last?
3h 1m, from 2025-02-21 19:57 UTC to 2025-02-21 22:58 UTC, by the times Bugsnag posted.
What was affected?
Bugsnag named BugSnag Error Reporting API.
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.