Minor incident

Grafana Cloud: GitHub returning 403 for all Git Sync repositories

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, AWS Ireland - prod-eu-west-6, AWS Japan - prod-ap-northeast-0, AWS Singapore - prod-ap-southeast-1, AWS Sweden eu-north-1, AWS Sweden - prod-eu-north-0, AWS Switzerland - prod-eu-central-0, AWS Switzerland eu-central-2, AWS UAE - prod-me-central-1, AWS UK - prod-gb-south-1, AWS US East (OH) - prod-us-east-0, AWS East (VA) prod-us-east-1, AWS US East (OH) - prod-us-east-2, AWS US West - prod-us-west-0, AWS US East (VA) - prod-us-east-3, AWS West prod-us-west-2, Azure US Central - us-central2, Azure Netherlands - prod-eu-west-3, Azure UAE - prod-me-central-2, GCP Australia - prod-au-southeast-0, GCP Belgium - prod-eu-west-0, GCP Brazil - prod-sa-east-0, GCP India - prod-ap-south-0, GCP Saudi Arabia - prod-me-central-0, GCP Singapore - prod-ap-southeast-0, GCP UK - prod-gb-south-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4, GCP US Central - prod-us-central-7, GCP US East - prod-us-east-1, play.grafana.org, Federal Cloud - AWS US Gov West, Azure Malasia - azure-malaysiawest-0

Current status of Grafana Cloud: Minor issues — live Grafana Cloud status

Timeline

1. Nov 4, 2026, 03:02 UTC
   identified
   Since ~21:40 UTC on Nov 3, GitHub started rejecting the default User-Agent our Git Sync client sends (nanogit/0), so nearly every GitHub-backed repo shows as unhealthy ("not authorized") and syncs are being skipped. Our Engineering team has rolled out a fix to development and validated that the fix works. We will roll out the fix to production shortly and will provide another update.
2. Nov 4, 2026, 04:07 UTC
   monitoring
   The fix has landed in 60% of production. We are currently monitoring as it lands in the remaining clusters.
3. Nov 4, 2026, 04:59 UTC
   resolved
   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.

Updates as published by Grafana Cloud (original).