Elevated Request Errors for Grafana Across Multiple Regions
Grafana request errors affected multiple Grafana Cloud regions, including regions in Australia, Brazil, Canada, Germany, India, Indonesia, Ireland, Japan, Singapore, Sweden, Switzerland, and the UAE. This caused slow-loading or failing dashboards and Explore queries. Grafana Cloud reports that the issue is resolved after about 1 hour 12 minutes.
State
Resolved
Started
Lasted
1 h 1 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
20 min 32%
Identified
3 min 5%
Monitoring
39 min 63%
Updates
Times in UTCAs posted by Grafana Cloud
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.
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.
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.
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.
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.
Affected components
88Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
47
Days with an incident
38
Median duration
2 h 49 min
This incident
64% shorter than the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1)
Metrics alert and recording rule evaluation did not work correctly in AWS Australia (prod-au-southeast-1). The affected components were Rule Evaluation and Alerting and SLO Rule Evaluation. Grafana Cloud reports that the outage is resolved and that it lasted about 1 hour 40 minutes.
Grafana Cloud·IRM Unable to Voice Call Brazil Numbers
Grafana Cloud reports that voice calls to Brazil do not work in Incident Management and Response (IRM). Grafana Cloud is investigating the issue. As a workaround, Grafana Cloud states that users can set mobile push or SMS as notifications.
Grafana Cloud·Frontend Observability Outage in prod-eu-west-2
This incident has been resolved.
Grafana Cloud·Degraded Cloud Integrations
This incident has been resolved.
Grafana Cloud·ingestion errors in mimir-prod-66
the issue is resolved now, we're watching the cell
Follow Grafana Cloud
Your coding agent knows when Grafana Cloud is down, and tells you when a failure is theirs, not yours. You can also get Grafana Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "grafana" and tell me if Grafana Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=grafana/feed subscribe https://outages.cc/feed.xml?providers=grafanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane