GitHub Copilot · 43d ago
Disruption with some GitHub services
ResolvedYes — GitHub Copilot had a problem on September 15, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “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.<br /><br />We sincerely apologize for the disruption.”
Timeline
Started: 9/15/2026, 7:11:31 PM
Last update: 9/18/2026, 5:08:48 PM
Resolved: 9/15/2026, 8:00:50 PM
Updates
resolved
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.<br /><br />We sincerely apologize for the disruption.
9/15/2026, 8:00:50 PM
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
9/15/2026, 7:48:02 PM
investigating
We are investigating reports of impacted performance for some GitHub services.
9/15/2026, 7:11:31 PM
More GitHub Copilot incidents
- Incident with Dependabot — resolved, 10h ago
- Incident with Actions, Pages, and Webhooks — resolved, 13h ago
- Disruption with GitHub services — resolved, 16h ago
- Disruption with Copilot Cloud services — resolved, 2d ago
- Incident with Actions — resolved, 9d ago
- Delayed Actions status check results — resolved, 8d ago