- Level
- confirmed
- Worst impact
- Degraded
- Components
- GCP US Central - prod-us-central-0
- Regions
- us, us-central-0, us-central-5
- Down Index
- 35of 100
What to do
Check whether you use Grafana Cloud GCP US Central - prod-us-central-0 in us, us-central-0, us-central-5. 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 1d 3h it lasted.
Anything that failed between 2026-03-09 18:03 UTC and 2026-03-10 21:17 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 2
- monitoring
From 15:30 to 15:45 UTC and from 16:53 to 17:03 UTC, the prod-us-central-0 and prod-us-central-5 regions saw elevated latency and error rates on the write path. We're monitoring now.
provider
- resolved
This incident has been 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-636165a936
Is Grafana Cloud still down?
No, this incident was resolved 2026-03-10 21:17 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
1d 3h, from 2026-03-09 18:03 UTC to 2026-03-10 21:17 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named GCP US Central - prod-us-central-0 in us, us-central-0, us-central-5.
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.