Live

Plugin installs and updates from the plugin catalog may fail

0

Plugin installs and updates from the plugin catalog may fail on some Grafana Cloud stacks in several regions for AWS Australia, Brazil, Canada, Germany, India, Indonesia, Ireland, Japan, Singapore, Sweden, Switzerland, and UAE. Grafana Cloud has identified the issue and is working on a resolution.

State

Identified

Started

Ongoing for

57 min

Worst impact

Degraded

Timeline

2 updates
11:5212:0612:2012:3412:49
DegradedUpdate postedTimes in UTC

Investigating

11 min 19%

Identified

46 min 81%

Updates

Times in UTC

As posted by Grafana Cloud

Identified

We are investigating an issue where installing or updating plugins from the plugin catalog may fail for a small number of Grafana Cloud stacks across several Grafana Cloud Regions (prod-ap-south-0, prod-ap-southeast-1, prod-ap-southeast-2, prod-ap-southeast-3, prod-eu-central-0, prod-eu-west-8, prod-me-central-0, prod-me-central-2). Customers may see an error when they try to install or update a plugin. The issue has been identified and we are actively working on a resolution. Next update by 13:00 UTC.

Investigating

We are investigating an issue where installing or updating plugins from the plugin catalog may fail for a small number of Grafana Cloud stacks across all Grafana Cloud Regions. Customers may see an error when they try to install or update a plugin. We are actively working on a resolution. Next update by 12:50 UTC.

Affected components

90
AWS Australia - prod-au-southeast-1AWS Australia - prod-au-southeast-2AWS Brazil - prod-sa-east-1AWS Canada prod-ca-central-1AWS Canada - prod-ca-east-0AWS Germany - prod-eu-west-2AWS Germany - prod-eu-west-4AWS Germany prod-eu-central-1

Grafana Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

59

Days with an incident

48

Median duration

2 h 38 min

This incident

64% 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 38 min
90 days agoToday

Other Grafana Cloud incidents

All incidents

Grafana Cloud·Increased Read Latency In prod-us-central-0 Region

Grafana Cloud reported increased read latency in the prod-us-central-0 region. The affected components were Querying for GCP US Central - prod-us-central-0 and Querying for Metrics - GCP US Central - prod-us-central-0. The incident is resolved and lasted 79 minutes.

Resolved

Grafana Cloud·Data Source Permission Errors

Between November 9 and November 18, 2026, some Grafana Cloud users with Edit or Admin permissions on a data source may have experienced “permission denied” (403) errors when configuring or querying a newly created data source. A change to how data source permissions are stored caused these permissions to be incorrectly evaluated. We rolled back that change on November 18 at 17:27 UTC, preventing newly created permissions from being affected. However, access issues caused by permissions stored before the rollback may persist until an additional fix is deployed.

Resolved

Grafana Cloud·Degraded performance for Grafana Cloud Metrics in prod-us-central-7

Grafana Cloud Metrics, Logs, and Traces had degraded performance in the prod-us-central-7 region. Writes, queries, and rule evaluations failed or were delayed. Grafana Cloud reports that the incident is resolved, and it lasted about 96 minutes.

Resolved

Grafana Cloud·Elevated query errors for Grafana Cloud Metrics in prod-us-east-3

Grafana Cloud Metrics queries failed for some customers in prod-us-east-3. Ingestion was not affected. Grafana Cloud reports that query errors have stopped. The incident is resolved and lasted about 4 hours and 14 minutes.

Resolved

Grafana Cloud·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.

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.

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane