Live / Grafana Cloud / Incident
Grafana Cloud: Tempo Write Failures in prod-us-central-0
Grafana Cloud · grafana.comMajor incidentResolved2026-10-15 21:53 UTC
Public — what happened
Summary
Grafana Cloud said it was looking into intermittent failures when writing data to its Tempo tracing service in the prod-us-central-0 region, starting at 16:10 UTC on 2026-10-15. The company attributed the problem to internal errors at Google Cloud Storage. By 18:00 UTC it reported that things were beginning to recover and that it was monitoring, and the incident was marked resolved at 21:53 UTC.
Affected
GCP US Central - prod-us-central-0: Ingestion
Timeline
- Started — 2026-10-15 16:10 UTC
- Investigating — 2026-10-15 16:10 UTC
- Monitoring — 2026-10-15 18:00 UTC
- Resolved — 2026-10-15 21:53 UTC · 5h 43m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Grafana Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Grafana Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Grafana Cloud report →
More from Grafana Cloud
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.