- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AWS US East (OH) - prod-us-east-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4
- Regions
- us, us-central-0, us-central-3, us-central-4, us-east-0
- Down Index
- 50of 100
What to do
Check whether you use Grafana Cloud AWS US East (OH) - prod-us-east-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4 in us, us-central-0, us-central-3, us-central-4. 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 2h 53m it lasted.
Anything that failed between 2026-07-15 18:07 UTC and 2026-07-15 21:00 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 4
- investigating
We are currently investigating an issue impacting a small subset of stacks in the impacted regions. We will provide more details as they become available.
provider
- identified
We believe we have found the cause and are working on remediation. It is also worth mentioning that only stacks on the "slow" release channel are impacted.
provider
- identified
The fix is in the process of being rolled out.
provider
- resolved
This incident has been resolved. Thank you for your patience.
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-5144326bf7
Is Grafana Cloud still down?
No, this incident was resolved 2026-07-15 21:00 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
2h 53m, from 2026-07-15 18:07 UTC to 2026-07-15 21:00 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named AWS US East (OH) - prod-us-east-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4 in us, us-central-0, us-central-3, us-central-4.
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.