Live / Grafana Cloud / Incident
Grafana Cloud: Increased timeout errors in alert rule evaluations (AWS Germany, prod-eu-west-2)
Grafana Cloud · grafana.comMinor incidentResolved2026-10-21 13:26 UTC
Public — what happened
Summary
Grafana Cloud said it saw more errors than usual when evaluating alert rules that pull data from its hosted Prometheus (Mimir) data sources in its AWS Germany cluster, which it labeled a minor issue. The company said the problem had begun around 20:30 UTC on October 20, and its status entry was opened at 11:48 UTC on October 21. By 12:12 UTC it said it had identified the root cause, and at 13:12 UTC it said fixes were applied and it was watching the recovery. The incident was marked resolved at 13:26 UTC.
Affected
AWS Germany - prod-eu-west-2: Rule Evaluation
Timeline
- Started — 2026-10-21 11:48 UTC
- Investigating — 2026-10-21 11:48 UTC
- Identified — 2026-10-21 12:12 UTC
- Monitoring — 2026-10-21 13:12 UTC
- Resolved — 2026-10-21 13:26 UTC · 1h 38m 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.