- Level
- confirmed
- Worst impact
- Degraded
- Components
- AWS US West - prod-us-west-0
- Regions
- us, us-west-0
- Down Index
- 29of 100
What to do
Check whether you use Grafana Cloud AWS US West - prod-us-west-0 in us, us-west-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 5h 13m it lasted.
Anything that failed between 2026-03-10 15:26 UTC and 2026-03-10 20:39 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
- identified
There has been a reoccurrence o the issues on the Read path of Loki services on AWS US West since yesterday 9th around ~17:15UTC. The issue has been identified, and resolutions steps has been taken to restore full service. We are currently monitoring the service status. The impact of this includes timeouts and 5xx errors when query logs for customers on this cluster.
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-39915e96f9
Is Grafana Cloud still down?
No, this incident was resolved 2026-03-10 20:39 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.
How long did it last?
5h 13m, from 2026-03-10 15:26 UTC to 2026-03-10 20:39 UTC, by the times Grafana Cloud posted.
What was affected?
Grafana Cloud named AWS US West - prod-us-west-0 in us, us-west-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.