Disruption with some GitHub services

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 49m it lasted.

  Anything that failed between 2026-09-15 19:11 UTC and 2026-09-15 20:00 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 3

1. investigatingSep 15, 2026, 7:11 PM UTC

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

   provider

2. monitoringSep 15, 2026, 7:48 PM UTC

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

   provider

3. resolvedSep 15, 2026, 8:00 PM 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. We sincerely apologize for the disruption.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.