Skip to main content
Grafana Cloud

Elevated Request Errors for Grafana Across Multiple Regions

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

Level
confirmed
Worst impact
Degraded
Components
AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada prod-ca-central-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS Germany prod-eu-central-1, AWS India - prod-ap-south-1, AWS Indonesia - prod-ap-southeast-2, AWS Indonesia - prod-ap-southeast-3, AWS Ireland eu-west-1, AWS Ireland - prod-eu-west-6, AWS Japan - prod-ap-northeast-0, AWS Singapore - prod-ap-southeast-1, AWS Sweden eu-north-1, AWS Sweden - prod-eu-north-0, AWS Switzerland - prod-eu-central-0, AWS Switzerland eu-central-2, AWS UAE - prod-me-central-1, AWS UK - prod-gb-south-1, AWS US East (OH) - prod-us-east-0, AWS East (VA) prod-us-east-1, AWS US East (OH) - prod-us-east-2, AWS US West - prod-us-west-0, AWS US East (VA) - prod-us-east-3, AWS West prod-us-west-2, Azure US Central - us-central2, Azure Netherlands - prod-eu-west-3, Azure UAE - prod-me-central-2, GCP Australia - prod-au-southeast-0, GCP Belgium - prod-eu-west-0, GCP Brazil - prod-sa-east-0, GCP India - prod-ap-south-0, GCP Saudi Arabia - prod-me-central-0, GCP Singapore - prod-ap-southeast-0, GCP UK - prod-gb-south-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4, GCP US Central - prod-us-central-7, GCP US East - prod-us-east-1, play.grafana.org, Federal Cloud - AWS US Gov West
Regions
ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-0, ap-southeast-1, ap-southeast-2, ap-southeast-3, apac, au, ca, ca-central-1, ca-east-0, eu, eu-central-0, eu-central-1, eu-central-2, eu-north-0, eu-north-1, eu-west-0, eu-west-1, eu-west-2, eu-west-3, eu-west-4, eu-west-6, in, jp, latam, me, me-central-0, me-central-1, me-central-2, sa-east-0, sa-east-1, us, us-central-0, us-central-3, us-central-4, us-central-7, us-central2, us-east-0, us-east-1, us-east-2, us-east-3, us-west-0, us-west-2
Down Index
37of 100

What to do

  • Check whether you use Grafana Cloud AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada prod-ca-central-1 and 40 more in ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-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 1h 1m it lasted.

    Anything that failed between 2026-11-03 12:40 UTC and 2026-11-03 13:42 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 some failed requests affecting Grafana across multiple Grafana Cloud regions, beginning at approximately 12:10 UTC. Customers may see slow-loading or failing dashboards and Explore queries, and some requests may time out or be cancelled. Our engineers are actively investigating. Next update by 13:30 UTC.

    provider

  2. identified

    We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and are applying mitigation. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 13:30 UTC.

    provider

  3. monitoring

    We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and have applied a mitigation. We are seeing early signs of recovery and are monitoring closely. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 13:30 UTC.

    provider

  4. monitoring

    We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and have applied a mitigation. We are seeing signs of recovery and are continuing to monitor closely. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 14:00 UTC.

    provider

  5. resolved

    Between approximately 12:10 UTC and 13:22 UTC on 3 November (about 1 hour 12 minutes), Grafana across multiple Grafana Cloud regions experienced elevated request errors, causing slow-loading or failing dashboards and Explore queries. The issue has been resolved and service has been fully restored.

    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-b8be3392ed

Is Grafana Cloud still down?

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

How long did it last?

1h 1m, from 2026-11-03 12:40 UTC to 2026-11-03 13:42 UTC, by the times Grafana Cloud posted.

What was affected?

Grafana Cloud named AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada prod-ca-central-1 and 40 more in ap-northeast-0, ap-south-0, ap-south-1, ap-southeast-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.