Skip to main content
Better Stack

Incorrectly sent out downtime notifications to single-region monitors due to intermittent Internet backbone issue

Degraded Lasted 39m · started · Better Stack's page

Level
confirmed
Worst impact
Degraded
Components
Uptime backend processing health
Down Index
21of 100

What to do

  • Check whether you use Better Stack Uptime backend processing health. 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 39m it lasted.

    Anything that failed between 2026-10-21 18:30 UTC and 2026-10-21 19:09 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

  1. degraded

    An intermittent network issue between Tier 1 network providers one of our cloud provider relies on triggered incidents for customers relying on single-region uptime Monitors. We're sincerely sorry for the trouble. We think this is unacceptable and consider it a priority to make our incident detection even more robust to correctly detect partial intermittent backbone issues. To fully mitigate immediately, we recommend enabling more than 1-region for your monitors. Need help? Let us know at hello@betterstack.com, we're here for you.

    provider

  2. resolved

    The issue has been resolved. We apologize for the trouble Need help? Please 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-809b28ef66

Is Better Stack still down?

No, this incident was resolved 2026-10-21 19:09 UTC. For Better Stack's live state, see https://down.guide/betterstack.

How long did it last?

39m, from 2026-10-21 18:30 UTC to 2026-10-21 19:09 UTC, by the times Better Stack posted.

What was affected?

Better Stack named Uptime backend processing health.

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.