Critical impactResolvedDevOps

GitHub outage: Disruption with some GitHub services

GitHub reported this critical-impact incident on its official status page on May 6, 2026, 11:21 UTC. It was resolved after 38 min.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
May 6, 2026, 11:21 UTC
started
May 6, 2026, 11:59 UTC
resolved
38 min
duration
Critical
impact
  1. resolvedMay 6, 2026, 11:59 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.

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.

How often does GitHub have incidents?

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

GitHub outage on May 6, 2026: Disruption with some GitHub services · APIStatus.watch