Incident with Webhooks

What to do

• Check whether you use GitHub Git Operations, Webhooks, Issues, Pull Requests and 1 more. 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 51m it lasted.

  Anything that failed between 2026-08-13 14:45 UTC and 2026-08-13 15:36 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 9

1. investigatingAug 13, 2026, 2:45 PM UTC

   We are investigating reports of degraded performance for Webhooks

   provider

2. investigatingAug 13, 2026, 2:46 PM UTC

   Pull Requests is experiencing degraded performance. We are continuing to investigate.

   provider

3. investigatingAug 13, 2026, 2:46 PM UTC

   Issues is experiencing degraded performance. We are continuing to investigate.

   provider

4. investigatingAug 13, 2026, 2:46 PM UTC

   Git Operations is experiencing degraded performance. We are continuing to investigate.

   provider

5. investigatingAug 13, 2026, 2:56 PM UTC

   Packages is experiencing degraded performance. We are continuing to investigate.

   provider

6. investigatingAug 13, 2026, 2:58 PM UTC

   We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence.

   provider

7. monitoringAug 13, 2026, 3:33 PM UTC

   The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

   provider

8. monitoringAug 13, 2026, 3:33 PM UTC

   We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.

   provider

9. resolvedAug 13, 2026, 3:36 PM UTC

   Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the incident at 15:36 UTC. Affected users may have experienced a brief increase in errors and slower responses, primarily when creating, listing, or updating webhooks, with smaller impacts to pull requests, issues, packages, and Git operations. Failures peaked at about 1% for several minutes around 14:37 UTC. To prevent future incidents, we've already shipped an update that turns on the safer deletion path for organizations, along with caps on deletion holds on databases. Building on these changes, we're auditing all bulk deletion and cleanup jobs that write to shared databases to prevent similar issues in future.

   provider

Corrections

None so far.

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