Increased query latency for Logs in GCP US Central (prod-us-central-0)
Grafana Cloud reports increased query latency for Logs in GCP US Central (prod-us-central-0). Some Logs queries in this region were slower than usual between 12:08 and 12:34 UTC. Grafana Cloud states that the issue is believed to be mitigated, and monitoring continues while the cause is investigated.
State
Monitoring
Started
Ongoing for
1 h 30 min
Worst impact
Degraded
Timeline
1 updateMonitoring
1 h 30 min 100%
Updates
Times in UTCAs posted by Grafana Cloud
Some Logs queries in GCP US Central (prod-us-central-0) were slower than usual between 12:08 and 12:34 UTC. The issue is believed to be mitigated, and the team is monitoring while the cause is investigated.
Affected components
2Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
48
Days with an incident
38
Median duration
2 h 49 min
This incident
47% shorter than the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·Elevated Request Errors for Grafana Across Multiple Regions
Grafana request errors affected multiple Grafana Cloud regions. Dashboards and Explore queries loaded slowly or failed. Grafana Cloud reports the incident resolved. The incident lasted about 1 hour 12 minutes.
Grafana Cloud·Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1)
Metrics alert and recording rule evaluation failed in Grafana Cloud AWS Australia (prod-au-southeast-1). The affected components were Rule Evaluation and Alerting and SLO. Grafana Cloud reports that the incident is resolved. 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 for Incident Management and Response (IRM). Grafana Cloud is investigating the issue. Grafana Cloud advises users to configure 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.
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