rewindex

ChangesGrafana CloudMimir query unexpected response with status code 500

Grafana Cloud: Incident updated: Mimir query unexpected response with status code 500

Incident updateNot classified yetChanged status.grafana.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Grafana Cloud removed; blue is what they added. Muted text is unchanged context.

AddedUpdatemonitoring#1
Before: not present
After: Our mitigation remains in place and query behavior in AWS US East (OH) and GCP US Central continues to improve. Some customers may still see occasional, brief query errors in the meantime.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayTuesday, November 10Tue, Nov 10

4 incident changes

Cite this

Incident updated: Mimir query unexpected response with status code 500 on Grafana Cloud’s status page, changed 2026-11-10 11:23 UTC (change 3 of 4).

Title
Incident updated: Mimir query unexpected response with status code 500
Vendor
Grafana Cloud
Date
URL
https://rewindex.com/change/r41921229e36860

All Grafana Cloud changesGrafana Cloud profileMarkdownJSON