Better Stack
Apps and SaaS. Source: Better Stack status page.
History starts 2026-08-20 14:39 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 4+
- Median to mitigation
- not reported
- Median to resolution
- 14h 22m
- p95 to resolution
- 2d 5h
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| Network, DNS, routing or connectivity failure | 1 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 1 |
| A schema or data migration caused the failure | 1 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Incorrectly sent out downtime notifications to single-region monitors due to intermittent Internet backbone issue
Affected: Uptime backend processing health
Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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...
-
resolved
The issue has been resolved. We apologize for the trouble Need help? Please let us know at hello@betterstack.com
Excerpts are shortened. Read the full incident on Better Stack's status page.
Delayed data processing in the Europe region
Affected: Telemetry
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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...
-
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.
-
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.
-
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...
Excerpts are shortened. Read the full incident on Better Stack's status page.
Delayed data processing in the Europe region
Affected: Telemetry
Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
degraded
We're seeing delayed data processing for some sources located in the Europe region following the scheduled migration. There's no data loss, all incoming data is ingested and will become visible as the system catches up. If you have any questions, feel free to reach out at...
-
resolved
Data processing in the Europe region has returned to normal following yesterday's migration. No data was lost. Some remaining historical data is catching up and will be filled shortly. We apologize for the trouble and thank you for your patience! Please reach out to...
Excerpts are shortened. Read the full incident on Better Stack's status page.
Degraded Telemetry performance
Affected: Telemetry
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
degraded
Telemetry dashboard might be unavailable for some customers due to a database issue, we're investigating.
-
resolved
The issue was resolved, we apologize for the incovenience, please let us know if we can help with anything at hello@betterstack.com.
Excerpts are shortened. Read the full incident on Better Stack's status page.