CompaniesBetter StackIncidents
Better Stack: Incorrectly sent out downtime notifications to single-region monitors due to intermittent Internet backbone issue
Affected components: Uptime backend processing health
Timeline of updates
- 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.
- resolved
The issue has been resolved. We apologize for the trouble
Need help? Please let us know at hello@betterstack.com
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived.
Better Stack profileRecent Better Stack incidentsMarkdownJSON