Data Source Permission Errors
Nov 18, 22:01 UTCNov 18, 22:01 UTC
Duration
0m
Impact
Minor
Root cause
Not disclosed
Grafana Labs, 90 days
71 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Nov 18, 22:01 UTC
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.
More from Grafana Labs
Full historyPlugin installs and updates from the plugin catalog may faillasted 2h 41mIncreased Read Latency In prod-us-central-0 Regionlasted 1h 19mDegraded performance for Grafana Cloud Metrics in prod-us-central-7lasted 1h 36mElevated query errors for Grafana Cloud Metrics in prod-us-east-3lasted 4h 14mCloud Logs writes - Elevated latency and error rates in prod-eu-central-0lasted 17mMimir query unexpected response with status code 500lasted 8h 32m