- Level
- confirmed
- Worst impact
- Degraded
- Components
- Telemetry
- Regions
- eu
- Down Index
- 28of 100
What to do
Check whether you use Better Stack Telemetry in eu. 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 2d 5h it lasted.
Anything that failed between 2026-09-04 13:50 UTC and 2026-09-06 19:13 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 4
- degraded
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 [hello@betterstack.com](mailto:hello@betterstack.com). Thank you for your patience!
provider
- degraded
Processing of new data in the Europe region is starting to recover. Backfilling delayed data will take longer, so older timestamps may still be missing. No data has been lost.
provider
- degraded
Live data is coming in. Historical data is backfilling at a steady rate, we expect several more hours until all data is processed. Thank you for your patience. Please reach out to [hello@betterstack.com](mailto:hello@betterstack.com) with any questions.
provider
- resolved
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 [hello@betterstack.com](mailto:hello@betterstack.com) if you have any questions.
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-499cf3ea2c
Is Better Stack still down?
No, this incident was resolved 2026-09-06 19:13 UTC. For Better Stack's live state, see https://down.guide/betterstack.
How long did it last?
2d 5h, from 2026-09-04 13:50 UTC to 2026-09-06 19:13 UTC, by the times Better Stack posted.
What was affected?
Better Stack named Telemetry in eu.
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.