Grafana Cloud outage, 4 November 2026
GitHub returning 403 for all Git Sync repositories
- Started
- Resolved
- 4 Nov 2026, 04:59 UTC (after 1 h 57 min)
- Impact
- Minor
- Affected
- AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada prod-ca-central-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS Germany prod-eu-central-1, AWS India - prod-ap-south-1, AWS Indonesia - prod-ap-southeast-2, AWS Indonesia - prod-ap-southeast-3, AWS Ireland eu-west-1
Is this still happening?
No. Grafana Cloud marked this incident resolved on 4 Nov 2026, 04:59 UTC, 1 h 57 min after it began.
Right now: Grafana Cloud reports a partial outage. (as of 4 Nov, 05:20 UTC) Live Grafana Cloud status
Last update from Grafana Cloud
The fix has been deployed to all production clusters and we are observing a continued period of stability. At this time, we are marking the incident as resolved.
Read the full incident on the official Grafana Cloud status page
Similar Grafana Cloud incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 1 h 1 min
-
, resolved after 4 h 42 min
Some Grafana Instances Experiencing Issues Coming Online after Restart
-
, resolved after 14 min
-
, resolved after 28 min
-
, resolved after 45 min
Elevated Trace Ingestion Latency and Errors for Grafana Cloud Traces in AWS Germany