# Grafana Cloud: GitHub returning 403 for all Git Sync repositories

> Grafana Cloud Git Sync repositories showed as unhealthy and syncs were skipped in all listed AWS regions. The provider identified the problem, deployed a fix to all production clusters, and monitored the result. Grafana Cloud resolved the incident after 1 hour and 58 minutes.

- Provider: [Grafana Cloud](https://outages.live/grafana.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-11-04 03:02 UTC
- Resolved: 2026-11-04 04:59 UTC (lasted 1 h 58 min)
- Components: 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, Grafana - AWS Australia - prod-au-southeast-1, Grafana - AWS Australia - prod-au-southeast-2, Grafana - AWS Brazil - prod-sa-east-1, Grafana - AWS Canada prod-ca-central-1, Grafana - AWS Canada - prod-ca-east-0, Grafana - AWS Germany - prod-eu-west-2, Grafana - AWS Germany - prod-eu-west-4, Grafana - AWS Germany prod-eu-central-1, Grafana - AWS India - prod-ap-south-1, Grafana - AWS Indonesia - prod-ap-southeast-2, Grafana - AWS Indonesia - prod-ap-southeast-3, Grafana - AWS Ireland eu-west-1, Grafana - AWS Ireland - prod-eu-west-6, Grafana - AWS Japan - prod-ap-northeast-0, Grafana - AWS Singapore - prod-ap-southeast-1, Grafana - AWS Sweden eu-north-1, Grafana - AWS Sweden - prod-eu-north-0, Grafana - AWS Switzerland - prod-eu-central-0, Grafana - AWS Switzerland eu-central-2, Grafana - AWS UAE - prod-me-central-1, Grafana - AWS UK - prod-gb-south-1, Grafana - AWS US East (OH) - prod-us-east-0, Grafana - AWS East (VA) prod-us-east-1, Grafana - AWS US East (OH) - prod-us-east-2, Grafana - AWS US West - prod-us-west-0, Grafana - AWS US East (VA) - prod-us-east-3, Grafana - AWS West prod-us-west-2, Grafana - Azure US Central - us-central2, Grafana - Azure Netherlands - prod-eu-west-3, Grafana - Azure UAE - prod-me-central-2, Grafana - GCP Australia - prod-au-southeast-0, Grafana - GCP Belgium - prod-eu-west-0, Grafana - GCP Brazil - prod-sa-east-0, Grafana - GCP India - prod-ap-south-0, Grafana - GCP Saudi Arabia - prod-me-central-0, Grafana - GCP Singapore - prod-ap-southeast-0, Grafana - GCP UK - prod-gb-south-0, Grafana - GCP US Central - prod-us-central-0, Grafana - GCP US Central - prod-us-central-3, Grafana - GCP US Central - prod-us-central-4, Grafana - GCP US Central - prod-us-central-7, Grafana - GCP US East - prod-us-east-1, Grafana - play.grafana.org, Grafana - Federal Cloud - AWS US Gov West, Grafana - Azure Malasia - azure-malaysiawest-0
- Official update: https://stspg.io/c1s5cmykytmk

## Updates from Grafana Cloud

### resolved, 2026-11-04 04:59 UTC

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.

### monitoring, 2026-11-04 04:09 UTC

The fix has landed in 60% of production. We are currently monitoring as it lands in the remaining clusters.

### identified, 2026-11-04 03:03 UTC

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.