Skip to main content
Grafana Cloud

Elevated Latency and Errors for Grafana Cloud Logs in AWS US East (VA)

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

Level
confirmed
Worst impact
Degraded
Components
AWS US East (VA) - prod-us-east-3
Regions
us, us-east-3

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 2h 59m it lasted.

    Anything that failed between 2026-09-30 12:40 UTC and 2026-09-30 15: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 5

  1. investigating

    We are investigating elevated latency and a small number of failed requests for Grafana Cloud Logs in AWS US East (VA). Some customers writing logs to this region may see delayed ingestion or occasional write errors. We are actively investigating and will share more as we learn it. Next update by 13:38 UTC.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. identified

    We have identified a contributing factor to the elevated latency and are rolling out a mitigation to increase write capacity in AWS US East (VA). We continue to investigate a related, longer-running pattern. Next update by 14:40 UTC.

    provider

  4. identified

    An additional brief recurrence affected a small number of requests after our mitigation was deployed, though impact was smaller than earlier today. We continue to monitor and investigate a related, longer-running pattern. Next update by 15:40 UTC.

    provider

  5. resolved

    Between 12:09 and 15:39 UTC on September 30, Grafana Cloud Logs in AWS US East (VA) experienced intermittent elevated latency and a small number of failed requests. Impact has returned to normal levels and all services are operating as expected. Thank you for your patience.

    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-9acd1d9e61

Is Grafana Cloud still down?

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

How long did it last?

2h 59m, from 2026-09-30 12:40 UTC to 2026-09-30 15:39 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.