Is Better Stack down?

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 [email protected], we're here for you.

The issue has been resolved. We apologize for the trouble Need help? Please let us know at [email protected]

We're seeing delayed data processing for some sources located in the Europe region again. The team is looking into resolving as soon as possible. There has been no data loss, all incoming data is ingested and will become visible as the system catches up. If you have any questions, please reach out to [email protected]. Thank you for your patience!

This incident is now resolved. All sources in the Europe region are processing in real time and the delayed backlog has been processed in full. What happened: On September 3, we consolidated several EU Telemetry clusters onto new, higher-capacity infrastructure. The cutover multiplied concurrent write streams on the cluster, and the volume of concurrent inserts saturated per-host write throughput on I/O contention. Ingestion fell behind, and affected sources saw delays in Live tail, dashboards, alerts, and queries. Our initial fixes, tuning the write path and adding capacity, restored real-time ingestion within a day, but draining the backlog alongside live traffic re-created the contention. We then rebuilt the recovery pipeline and held live data with strict priority while separately replaying the backlog at a controlled rate. Replaying several days of data was the slowest part of the recovery by design, as we rate-limited the replay so that real-time ingestion wasn't put at risk. We know teams rely on this data to operate their own systems, and losing that visibility for days is serious. We are sorry, both for the disruption and for turning what we originally announced as 90-minute maintenance into a multi-day incident. The fixes we made here are permanent, and this kind of contention can't happen again. Thank you very much for your patience. Please reach out to [email protected] if you have any questions.

Telemetry dashboard might be unavailable for some customers due to a database issue, we're investigating.

The issue was resolved, we apologize for the incovenience, please let us know if we can help with anything at [email protected].