Skip to main content
Grafana Cloud

Service degradation on Logs Read path in AWS US West (us-west-0)

Degraded Lasted 6h 14m · started · Grafana Cloud's page

Level
confirmed
Worst impact
Degraded
Components
AWS US West - prod-us-west-0
Regions
us, us-west-0
Down Index
30of 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 6h 14m it lasted.

    Anything that failed between 2026-03-08 14:17 UTC and 2026-03-08 20:31 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 3

  1. investigating

    Our engineering team is investigating issues on the read path of Loki services on AWS US West since today aroun ~13:25UTC. These issues can cause timeouts and 5xx errors when query logs for customers on the cluster. The team is currently working to restore the service.

    provider

  2. monitoring

    Since 16:35 UTC we have experienced stability and services are recovering. We are actively monitoring and working to fully stabilize

    provider

  3. resolved

    We continue to observe a continued period of stability since 19:40 UTC. At this time, we are considering this issue 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-1c5038dd49

Is Grafana Cloud still down?

No, this incident was resolved 2026-03-08 20:31 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.

How long did it last?

6h 14m, from 2026-03-08 14:17 UTC to 2026-03-08 20:31 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.