Disruption with some GitHub services

What to do

• Check whether you use GitHub Copilot Copilot. 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 52m it lasted.

  Anything that failed between 2026-05-26 15:44 UTC and 2026-05-26 16:35 UTC may need a replay.

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

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

Updates from GitHub Copilot 4

1. investigatingMay 26, 2026, 3:44 PM UTC

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

   provider

2. investigatingMay 26, 2026, 3:48 PM UTC

   Copilot is experiencing degraded performance. We are continuing to investigate.

   provider

3. monitoringMay 26, 2026, 4:24 PM UTC

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

   provider

4. resolvedMay 26, 2026, 4:35 PM UTC

   On May 26, 2026, between 15:10 UTC and 16:35 UTC the Copilot service was degraded and many models were no longer available for use. On average, the error rate was ~5% and peaked at 11% of requests to the service. This was due to a change that introduced a configuration mismatch in HMAC signing credentials which caused the list of available models to be truncated. This was mitigated by rolling back the change. This rollback was complete by 15:34 UTC though users continued to see impact until cache TTLs expired. We are working to improve our monitoring and error handling to reduce time to detection and better experience for issues like this in the future.

   provider

Corrections

None so far.

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