- Level
- confirmed
- Worst impact
- Degraded
- Components
- AWS US East - prod-us-east-0: Querying, GCP US Central - prod-us-central-0: Querying
- Regions
- us, us-central-0, us-east-0
- Down Index
- 46of 100
Summary
Grafana Cloud says Mimir queries were returning an unexpected response with status code 500 when querying older data. The provider says a fix has been implemented and it is monitoring the results, with the incident in a monitoring state.
Written by anthropic/claude-haiku-5.5 from Grafana Cloud's own updates.
What to do
Check whether you use Grafana Cloud AWS US East - prod-us-east-0: Querying, GCP US Central - prod-us-central-0: Querying in us, us-central-0, us-east-0. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 8h 32m it lasted.
Anything that failed between 2026-11-10 03:38 UTC and 2026-11-10 12:09 UTC may need a replay.Subscribe to Grafana Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=grafana-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Grafana Cloud 6
- identified
We’ve identified an issue querying older data, and are already seeing recovery
provider
- identified
We’ve identified an issue querying older data, and are already seeing recovery.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- resolved
From approximately 03:20 UTC on 10 November, some Grafana Cloud Metrics customers in AWS US East (OH) and GCP US Central saw errors, or failed queries, when reading older data. Service has fully recovered and this incident is now resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-4286df2342
Is Grafana Cloud still down?
No, this incident was resolved 2026-11-10 12:09 UTC. For Grafana Cloud's live state, see https://down.guide/providers/grafana-cloud.
How long did it last?
8h 32m, from 2026-11-10 03:38 UTC to 2026-11-10 12:09 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named AWS US East - prod-us-east-0: Querying, GCP US Central - prod-us-central-0: Querying in us, us-central-0, us-east-0.
What caused it?
Grafana Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Grafana Cloud's official status page, https://status.grafana.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.