GitHub returning 403 for all Git Sync repositories
Grafana Cloud Git Sync failed for GitHub-backed repositories in all listed AWS regions. GitHub rejected the default User-Agent (nanogit/0), so repositories showed as not authorized and syncs were skipped. Grafana Cloud reports the incident is resolved. It lasted about 118 minutes.
State
Resolved
Started
Lasted
1 h 58 min
Worst impact
Degraded
Timeline
3 updatesIdentified
1 h 7 min 57%
Monitoring
51 min 43%
Updates
Times in UTCAs posted by 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.
The fix has landed in 60% of production. We are currently monitoring as it lands in the remaining clusters.
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.
Affected components
90Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
39
Median duration
2 h 42 min
This incident
28% shorter than the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·October usage report visualization issue
Grafana Cloud reports that October usage shows as 0 in the Cost Management and Billing component. Grafana Cloud has identified the problem and states that the cause is a billing metrics exporter issue. Grafana Cloud is working to backfill the correct data. This is a visualization issue only and did not affect billing.
Grafana Cloud·Increased query latency for Logs in GCP US Central (prod-us-central-0)
Grafana Cloud reports increased query latency for Logs in GCP US Central (prod-us-central-0). The incident is resolved. Logs queries were slower than usual between 12:08 and 12:34 UTC, and the incident lasted 91 minutes.
Grafana Cloud·Elevated Request Errors for Grafana Across Multiple Regions
Grafana request errors affected multiple Grafana Cloud regions, including regions in Australia, Brazil, Canada, Germany, India, Indonesia, Ireland, Japan, Singapore, Sweden, Switzerland, and the UAE. This caused slow-loading or failing dashboards and Explore queries. Grafana Cloud reports that the issue is resolved after about 1 hour 12 minutes.
Grafana Cloud·Grafana Cloud: k6 timeouts
We had a transient database slowdown causing a limited number of customers' k6 cloud runs to time out or abort in a window of a few minutes after Nov 2, 15:00 UTC. We are investigating the cause.
Grafana Cloud·Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1)
Metrics alert and recording rule evaluation did not work correctly in AWS Australia (prod-au-southeast-1). The affected components were Rule Evaluation and Alerting and SLO Rule Evaluation. Grafana Cloud reports that the outage is resolved and that it lasted about 1 hour 40 minutes.
Follow Grafana Cloud
Your coding agent knows when Grafana Cloud is down, and tells you when a failure is theirs, not yours. You can also get Grafana Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "grafana" and tell me if Grafana Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=grafana/feed subscribe https://outages.cc/feed.xml?providers=grafanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane