- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-0
What to do
Check whether you use Grafana Cloud in us, 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 0m it lasted.
Anything that failed between 2026-10-12 16:07 UTC and 2026-10-12 01:30 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 1
- resolved
Between 14:40 and 15:00 UTC on 2026-10-12 (approximately 20 minutes), customers in AWS US East (OH) - prod-us-east-0, may have experienced failed metric writes to Grafana Cloud Metrics. This has been fully resolved and all services are operating normally.
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-89fe4860e4
Is Grafana Cloud still down?
No, this incident was resolved 2026-10-12 01:30 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
0m, from 2026-10-12 16:07 UTC to 2026-10-12 01:30 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named in us, 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.