Grafana Cloud unavailibity in the prod-gb-south-0 region
This incident has been resolved.
The latest update from Grafana Cloud.
State
Resolved
Started
12 d ago
2026-10-20 12:43 UTC
Lasted
3 h 50 min
until 2026-10-20 16:33 UTC
Worst impact
Degraded
Timeline
6 updatesIdentified
3 h 50 min 100%
Updates
Times in UTCAs posted by Grafana Cloud
This incident has been resolved.
We are seeing errors in Frontend o11y again. We are continuing to investigate and monitor the impacted services.
Between 06:15 and 12:15 UTC, Grafana Cloud Frontend Observability in GCP UK (prod-gb-south-0) experienced errors accepting incoming telemetry data. This has been resolved and Frontend Observability is operating normally in this region. We are continuing to investigate and monitor the remaining impacted services.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
As of 06:30 UTC, we became aware of to an issue with Grafana Cloud unavailibity in the prod-gb-south-0 region. Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
Affected components
37Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
44
Days with an incident
36
Median duration
2 h 53 min
This incident
1.3× the median
Other Grafana Cloud incidents
All incidentsGrafana 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
Grafana Cloud·Some Grafana Instances Experiencing Issues Coming Online after Restart
This incident has been resolved.
Grafana Cloud·Elevated Trace Ingestion Latency and Errors for Grafana Cloud Traces in AWS Germany
Between 09:31 and 10:13 UTC on 23 October 2026 (42 minutes), Grafana Cloud Traces in AWS Germany experienced elevated ingestion latency and intermittent trace write failures, affecting both direct trace ingestion and ingestion via the OpenTelemetry endpoint. All services are now operating normally.
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