GitHub incident: Disruption with some GitHub services

1. resolvedSep 15, 2026, 20:00 UTC

   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.

2. monitoringSep 15, 2026, 19:48 UTC

   The degradation has been mitigated. We are monitoring to ensure stability.

3. investigatingSep 15, 2026, 19:11 UTC

   We are investigating reports of impacted performance for some GitHub services.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Telnyx: Outbound Messaging LatencyMinor · Sep 15, 2026, 15:27 UTC
• ClickHouse Cloud: ClickPipes failing on Kinesis in AWS us-east-1Minor · Sep 15, 2026, 18:57 UTC

How often does GitHub have incidents?

GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history