- Level
- confirmed
- Worst impact
- Degraded
- Components
- BugSnag Dashboard
- Regions
- us
- Down Index
- 21of 100
What to do
Check whether you use Bugsnag BugSnag Dashboard in us. 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 48m it lasted.
Anything that failed between 2025-10-20 10:11 UTC and 2025-10-20 10:59 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
- monitoring
An AWS outage occurred, preventing SmartBear ID logins to the BugSnag dashboard and notification emails from being sent. We are monitoring the situation, but we expect that logins and email notifications will now continue to work as normal. All other functionality remained operational throughout the incident. The AWS incident can be tracked here: https://health.aws.amazon.com/health/status#multipleservices-us-east-1_1760954629
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-8bd4b54377
Is Bugsnag still down?
No, this incident was resolved 2025-10-20 10:59 UTC. For Bugsnag's live state, see https://down.guide/bugsnag.
How long did it last?
48m, from 2025-10-20 10:11 UTC to 2025-10-20 10:59 UTC, by the times Bugsnag posted.
What was affected?
Bugsnag named BugSnag Dashboard in us.
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.