Live / Grafana Cloud / Incident
Grafana Cloud: Elevated Trace Ingestion Latency and Errors for Grafana Cloud Traces in AWS Germany
Grafana Cloud · grafana.comMajor incidentResolved2026-10-23 10:16 UTC
Public — what happened
Summary
Grafana Cloud reported a major incident affecting Grafana Cloud Traces in its AWS Germany region, starting at 09:31 UTC on 2026-10-23. The company said customers might see slow trace ingestion and some trace writes failing. Its only posted update said it was investigating, and no cause was given in the text provided. The incident is marked resolved as of 10:16.
Affected
AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2: Ingestion
Timeline
- Started — 2026-10-23 09:31 UTC
- Investigating — 2026-10-23 09:31 UTC
- Resolved — 2026-10-23 10:16 UTC · 45 min 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 44, 2026, our weekly internet health report.