Cloud Logs writes - Elevated latency and error rates in prod-eu-central-0
Grafana Cloud Cloud Logs writes had high latency and error rates in prod-eu-central-0. The affected components were AWS Switzerland - prod-eu-central-0 and Logs - AWS Switzerland - prod-eu-central-0. Grafana Cloud reports that this incident is resolved, and it lasted about 17 minutes.
State
Resolved
Started
Lasted
17 min
Worst impact
Notice
Timeline
2 updatesMonitoring
17 min 100%
Updates
Times in UTCAs posted by Grafana Cloud
We're observing a continued period of recovery and will mark this as resolved.
Cloud Logs writes have experienced elevated latency and error rates in prod-eu-central-0 from 07:05 UTC to 07:08 UTC, and 07:25 UTC to 07:45 UTC. The latency has been mitigated and we are currently monitoring.
Affected components
2Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
54
Days with an incident
43
Median duration
2 h 42 min
This incident
89% shorter than the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·Mimir query unexpected response with status code 500
Mimir queries for older data fail with status code 500 in the AWS US East prod-us-east-0 and GCP US Central prod-us-central-0 querying components. Grafana Cloud identified the issue and implemented a fix. Grafana Cloud now monitors the results, and the incident continues.
Grafana Cloud·Synthetic Monitoring — Jakarta Public Probe Degradation
Between 08:31 and 09:17 UTC on 6 November 2026, a network issue at the Jakarta public probe caused elevated check failures for monitors running from that location. - DNS checks: failure rate increased from ~0.3% to ~15% - HTTP, ping, traceroute, and browser checks: <1% failure rate - Browser checks: some delays and retries observed - TCP checks: not affected - All other probe locations: not affected
Grafana Cloud·GitHub returning 403 for all Git Sync repositories
Grafana Cloud Git Sync repositories showed as unhealthy and syncs were skipped in all listed AWS regions. The provider identified the problem, deployed a fix to all production clusters, and monitored the result. Grafana Cloud resolved the incident after 1 hour and 58 minutes.
Grafana Cloud·October usage report visualization issue
Grafana Cloud reported that the October usage in its Cost Management and Billing app showed as 0. Grafana Cloud stated this was a visualization issue and did not affect billing. The incident is resolved and lasted about 3 days.
Grafana Cloud·Increased query latency for Logs in GCP US Central (prod-us-central-0)
Grafana Cloud reports slower than usual Logs queries in GCP US Central (prod-us-central-0). Grafana Cloud also reports delayed Metrics alert and recording rule evaluations in the same region. Grafana Cloud resolved the incident, and the degraded period lasted about 91 minutes.
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.live/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.live/feed.xml?providers=grafana/feed subscribe https://outages.live/feed.xml?providers=grafanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane