- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 21of 100
What to do
Check whether you use Better Stack 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 41m it lasted.
Anything that failed between 2026-05-08 19:24 UTC and 2026-05-08 20:05 UTC may need a replay.Subscribe to Better Stack's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=betterstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Better Stack 2
- update
We're mitigating. Need help? Let us know at hello@betterstack.com
provider
- resolved
The attack has been successfully mitigated by our DDoS protection. Sincere apologies for the inconvenience. Need help? Let us know at hello@betterstack.com.
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-db18717860
Is Better Stack still down?
No, this incident was resolved 2026-05-08 20:05 UTC. For Better Stack's live state, see https://down.guide/betterstack.
How long did it last?
41m, from 2026-05-08 19:24 UTC to 2026-05-08 20:05 UTC, by the times Better Stack posted.
What was affected?
Better Stack named in us.
What caused it?
Better Stack hasn't published a root cause. If it does, it shows here.
Where does this come from?
Better Stack's official status page, https://status.betterstack.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.