GitHub incident: Webhook APIs and UI Degraded

1. resolvedMay 28, 2026, 01:32 UTC

   On May 28, 2026, between 00:54 UTC and 01:19 UTC, some users experienced errors when interacting with the Webhooks API, including webhook delivery history and configuration endpoints. On average, the error rate was 0.28% and peaked at 0.45%. This was due to a bug that caused a single Kubernetes pod to enter a CrashLoopBackOff after receiving a 500 with an empty response body from Cosmos DB.We mitigated the incident by restarting the service. To prevent future incidents, we are pushing a change to handle this response scenario from Cosmos DB appropriately.

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.

• OVHcloud: [AP-SOUTH-MUM/EU-SOUTH-MIL/EU-WEST-PAR/RBX][Containers & Orchestration] - Managed Kubernetes Service Incident NotificationMajor · May 27, 2026, 15:27 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
• OVHcloud: [GRA/RBX/DE][Storage and Backups] - Object Storage Incident NotificationMinor · May 22, 2026, 15:04 UTC
• Twilio: SMS and MMS Delivery Delays from Twilio to Verizon United StatesMinor · May 27, 2026, 17:13 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to EcuadorMinor · May 27, 2026, 23:15 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