Live

Degraded data source queries

Incident started around 15:51 UTC, resolved around 18:11 UTC. After investigation, we found that no customer queries were affected; only our internal metrics systems were impacted.

The latest update from Grafana Cloud.

State

Resolved

Started

28 d ago

2026-10-04 18:20 UTC

Lasted

14 min

until 2026-10-04 18:33 UTC

Worst impact

Degraded

Timeline

2 updates
18:2018:2318:2718:3018:33
DegradedUpdate postedTimes in UTC

Investigating

14 min 100%

Updates

Times in UTC

As posted by Grafana Cloud

Resolved2026-10-04 18:33 UTC

Incident started around 15:51 UTC, resolved around 18:11 UTC. After investigation, we found that no customer queries were affected; only our internal metrics systems were impacted.

Investigating2026-10-04 18:20 UTC

We are investigating reduced query throughput for some data source plugins in multiple regions. Some queries may fail or be slow.

Affected components

10
AWS Germany - prod-eu-west-2AWS Germany - prod-eu-west-4AWS US East (OH) - prod-us-east-2GCP Australia - prod-au-southeast-0GCP US Central - prod-us-central-4Grafana - AWS Germany - prod-eu-west-2Grafana - AWS Germany - prod-eu-west-4Grafana - AWS US East - prod-us-east-2

Grafana Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

44

Days with an incident

36

Median duration

2 h 53 min

This incident

92% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

14 days
median 2 h 53 min
90 days agoToday

Other Grafana Cloud incidents

All incidents

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=grafana
Slack
/feed subscribe https://outages.cc/feed.xml?providers=grafana

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane