Webhook APIs and UI Degraded

What to do

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

  Anything that failed between 2026-05-28 01:13 UTC and 2026-05-28 01:32 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 3

1. investigatingMay 28, 2026, 1:13 AM UTC

   We are investigating reports of degraded performance for Webhooks

   provider

2. monitoringMay 28, 2026, 1:27 AM UTC

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

   provider

3. resolvedMay 28, 2026, 1:32 AM 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.

   provider

Corrections

None so far.

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