Live / Grafana Cloud / Incident
Grafana Cloud: Mimir query unexpected response with status code 500
Grafana Cloud · grafana.comMinor incidentResolved2026-11-10 12:09 UTC
Public — what happened
Summary
Grafana Cloud reported a minor incident in which queries to Mimir returned an unexpected error (status code 500). The company said the problem affected queries for older data, and it began at 03:38 UTC on 2026-11-10. Grafana Cloud said it had identified the issue and was already seeing recovery, and by 04:42 UTC it said a fix had been put in place. The incident is not marked resolved, as the company said it is still monitoring the results.
Affected
AWS US East - prod-us-east-0: Querying, GCP US Central - prod-us-central-0: Querying
Timeline
- Started — 2026-11-10 03:38 UTC
- Identified — 2026-11-10 03:38 UTC (2 updates)
- Monitoring — 2026-11-10 04:42 UTC (3 updates)
- Resolved — 2026-11-10 12:09 UTC · 8h 32m 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 47, 2026, our weekly internet health report.