Minor impactResolvedMonitoring

Grafana Cloud incident: Elevated Request Errors for Grafana Across Multiple Regions

Grafana Cloud reported this minor-impact incident on its official status page on Nov 3, 2026, 12:40 UTC. It was resolved after 1h 1m.

Right now Grafana Cloud is operational. Live Grafana Cloud status →

🔔 Get alerted when Grafana Cloud has issuesFree · email alerts · no credit card
Nov 3, 2026, 12:40 UTC
started
Nov 3, 2026, 13:42 UTC
resolved
1h 1m
duration
Minor
impact

Affected components

  • AWS Australia - prod-au-southeast-1
  • AWS Australia - prod-au-southeast-2
  • AWS Brazil - prod-sa-east-1
  • AWS Canada - prod-ca-east-0
  • AWS Canada prod-ca-central-1
  • AWS East (VA) prod-us-east-1
  • 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 - prod-eu-west-6
  • AWS Ireland eu-west-1
  • AWS Japan - prod-ap-northeast-0
  • AWS Singapore - prod-ap-southeast-1
  • AWS Sweden - prod-eu-north-0
  • AWS Sweden eu-north-1
  • 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 US East (OH) - prod-us-east-2
  • AWS US East (VA) - prod-us-east-3

Timeline

updates from Grafana Cloud's status page ↗
  1. resolvedNov 3, 2026, 13:42 UTC

    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.

  2. monitoringNov 3, 2026, 13:28 UTC

    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.

  3. monitoringNov 3, 2026, 13:00 UTC

    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.

  4. identifiedNov 3, 2026, 12:57 UTC

    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.

  5. investigatingNov 3, 2026, 12:40 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Grafana Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Grafana Cloud have incidents?

Grafana Cloud reported 51 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 2h 24m. See Grafana Cloud's uptime and incident history

← Previous: Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1) (Nov 2, 2026)Next: Increased query latency for Logs in GCP US Central (prod-us-central-0) (Nov 3, 2026) →