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 38m it lasted.

  Anything that failed between 2026-05-06 11:21 UTC and 2026-05-06 11:59 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 4

1. investigatingMay 6, 2026, 11:21 AM UTC

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

   provider

2. investigatingMay 6, 2026, 11:25 AM UTC

   We are investigating issues with the ability to start Copilot Cloud Agent sessions and view them.

   provider

3. investigatingMay 6, 2026, 11:59 AM UTC

   We have applied a mitigation and Copilot services have recovered.

   provider

4. resolvedMay 6, 2026, 11:59 AM UTC

   On May 6, 2026 between 11:02 UTC and 11:13 UTC, users were unable to start or view Copilot Cloud Agent or remote sessions. During this time, requests to the session API returned errors, preventing users from creating new sessions or viewing existing ones. The issue was caused by a configuration change to the service's network routing that inadvertently removed the ingress path for the service. The team reverted the change at 11:13 UTC which restored service. The incident remained open until 11:59 UTC while the team verified full recovery. We are taking steps to improve our deployment validation process to prevent similar configuration changes from impacting production traffic 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.