Skip to main content
Grafana Cloud

ingestion errors in mimir-prod-66

Degraded Lasted 1h · started · Grafana Cloud's page

Level
confirmed
Worst impact
Degraded
Components
AWS US East (VA) - prod-us-east-3
Regions
us, us-east-3
Down Index
25of 100

What to do

  • Check whether you use Grafana Cloud AWS US East (VA) - prod-us-east-3 in us, us-east-3. 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 1h it lasted.

    Anything that failed between 2026-10-26 02:13 UTC and 2026-10-26 03:13 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. identified

    The issue has been identified, we are working on a fix

    provider

  2. identified

    read path is also affected.

    provider

  3. resolved

    the issue is resolved now, we're watching the cell

    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-85fa4fcff2

Is Grafana Cloud still down?

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

How long did it last?

1h, from 2026-10-26 02:13 UTC to 2026-10-26 03:13 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named AWS US East (VA) - prod-us-east-3 in us, us-east-3.

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.