Skip to main content
Grafana Cloud

Tempo and Mimir Read and Write Failures

Degraded Lasted 2h 42m · started · Grafana Cloud's page

Level
confirmed
Worst impact
Degraded
Components
AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion, AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion
Regions
us, us-west-0
Down Index
28of 100

What to do

  • Check whether you use Grafana Cloud AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion, AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion 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 2h 42m it lasted.

    Anything that failed between 2026-09-03 22:13 UTC and 2026-09-04 00:55 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

  1. identified

    The issue has been identified and a fix is being implemented.

    provider

  2. identified

    Cluster Metrics are healthy for the last 15 minutes

    provider

  3. monitoring

    Tempo recovered.

    provider

  4. 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-d117d68baf

Is Grafana Cloud still down?

No, this incident was resolved 2026-09-04 00:55 UTC. For Grafana Cloud's live state, see https://down.guide/grafana-cloud.

How long did it last?

2h 42m, from 2026-09-03 22:13 UTC to 2026-09-04 00:55 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion, AWS US West - prod-us-west-0: Querying, AWS US West - prod-us-west-0: Ingestion 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.