Increased Execution Time for Browser Checks in Synthetic Monitoring
Between September 9 and September 15, 2026, some browser checks in Synthetic Monitoring experienced longer than usual execution times, with impact varying by location. This has been resolved and check execution times have returned to baseline. Thank you for your patience.
The latest update from Grafana Cloud.
State
Resolved
Started
47 d ago
2026-09-15 10:00 UTC
Lasted
1 h 17 min
until 2026-09-15 11:17 UTC
Worst impact
Degraded
Timeline
4 updatesIdentified
58 min 76%
Monitoring
19 min 24%
Updates
Times in UTCAs posted by Grafana Cloud
Between September 9 and September 15, 2026, some browser checks in Synthetic Monitoring experienced longer than usual execution times, with impact varying by location. This has been resolved and check execution times have returned to baseline. Thank you for your patience.
A fix has been deployed and CPU throttling is returning to normal. Check execution times should return to baseline shortly. We will continue monitoring recovery. Next update by 11:56 UTC.
A fix has been merged and is now being rolled out across affected locations. We are monitoring deployment progress. Next update by 11:49 UTC.
Since September 9, 2026, some browser checks in Synthetic Monitoring may take longer to complete than usual, with impact varying by location. We have identified the cause and are actively working on a fix. Next update by 10:49 UTC.
Affected components
56Grafana 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
56% shorter than 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