Grafana incident

GitHub returning 403 for all Git Sync repositories

Ongoing since 03:02 AM UTC, affecting AWS Australia - prod-au-southeast-2 and AWS Brazil - prod-sa-east-1 and 1 more.

monitoring Nov 04, 2026, 04:07 AM UTC

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

Started: Nov 04, 2026, 03:02 AM UTC
Resolved: Ongoing
Duration: ● 1h 22m
Detected by Pingoru: Nov 04, 2026, 03:02 AM UTC

Affected components

AWS Australia - prod-au-southeast-2AWS Brazil - prod-sa-east-1AWS Canada - prod-ca-east-0AWS Germany - prod-eu-west-2AWS Germany - prod-eu-west-4AWS India - prod-ap-south-1AWS Japan - prod-ap-northeast-0AWS UAE - prod-me-central-1AWS Singapore - prod-ap-southeast-1AWS Sweden - prod-eu-north-0

Update timeline

identified Nov 04, 2026, 03:02 AM 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.
monitoring Nov 04, 2026, 04:07 AM UTC

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

Your product runs on more than Grafana

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.