GitHub incident: Disruption with some GitHub services

1. resolvedMay 26, 2026, 16:35 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.

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.

• Inngest: Issues connecting to data store for events/runs/metrics pagesMajor · May 26, 2026, 09:26 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Twilio: Subset of AU Sender ID Registration Submissions Directly Transitioning to REJECTEDMinor · May 15, 2026, 20:51 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Twilio: SMS Delivery Failures from Network Subscribers to Twilio Denmark Phone NumbersMinor · May 20, 2026, 07:58 UTC
• OVHcloud: [GRA/RBX/DE][Storage and Backups] - Object Storage Incident NotificationMinor · May 22, 2026, 15:04 UTC
• Twilio: SMS Delivery Delays from Twilio to Tigo HondurasMinor · May 26, 2026, 11:56 UTC

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