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.
State
Resolved
Started
Lasted
1 h 58 min
Worst impact
Degraded
Timeline
3 updatesIdentified
1 h 7 min 57%
Monitoring
50 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
The October usage report in Grafana Cloud Cost Management and Billing shows 0. Grafana Cloud identified the problem and reports that a billing metrics exporter gave wrong usage data at month-end. Grafana Cloud works to backfill the correct data. Billing is not affected.
Grafana Cloud·Increased query latency for Logs in GCP US Central (prod-us-central-0)
Grafana Cloud reports slower than usual Logs queries in GCP US Central (prod-us-central-0). Grafana Cloud also reports delayed Metrics alert and recording rule evaluations in the same region. Grafana Cloud resolved the incident, and the degraded period lasted about 91 minutes.
Grafana Cloud·Elevated Request Errors for Grafana Across Multiple Regions
Grafana request errors affected multiple Grafana Cloud regions. Dashboards and Explore queries loaded slowly or failed. Grafana Cloud reports the incident resolved. The incident lasted 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 failed in Grafana Cloud AWS Australia (prod-au-southeast-1). The affected components were Rule Evaluation and Alerting and SLO. Grafana Cloud reports that the incident is resolved. 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.live/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.live/feed.xml?providers=grafana/feed subscribe https://outages.live/feed.xml?providers=grafanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane