Disruption with some GitHub services
On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock acquisition, which interrupted the job. We reverted the change to the internal caching service and restored normal operation by 20:00 UTC. We sincerely apologize for the disruption.
The latest update from GitHub.
State
Resolved
Started
47 d ago
2026-09-15 19:11 UTC
Lasted
49 min
until 2026-09-15 20:00 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
37 min 74%
Monitoring
13 min 26%
Updates
Times in UTCAs posted by GitHub
On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock acquisition, which interrupted the job. We reverted the change to the internal caching service and restored normal operation by 20:00 UTC. We sincerely apologize for the disruption.
The degradation has been mitigated. We are monitoring to ensure stability.
We are investigating reports of impacted performance for some GitHub services.
GitHub in the last 90 days
Full historyIncidents in 90 days
46
Days with an incident
34
Median duration
1 h 29 min
This incident
45% shorter than the median
Other GitHub incidents
All incidentsGitHub·Incident with Dependabot
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
GitHub·Incident with Actions, Pages, and Webhooks
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
GitHub·Disruption with GitHub services
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
GitHub·Disruption with Copilot Cloud services
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
GitHub·Disruption with some Copilot services
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Follow GitHub
Your coding agent knows when GitHub is down, and tells you when a failure is theirs, not yours. You can also get GitHub 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 "github" and tell me if GitHub 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=github/feed subscribe https://outages.cc/feed.xml?providers=githubFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane