Resolved incident

Incident with Webhooks

GitHub · Minor · Started

Duration
51m
Severity
Minor
Status
Resolved

Summary

Minor · Resolved

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. <br /><br />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. <br /><br />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.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Investigating

    GitHub

    We are investigating reports of degraded performance for Webhooks

  2. Investigating

    GitHub

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

  3. Investigating

    GitHub

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

  4. Investigating

    GitHub

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

  5. Investigating

    GitHub

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

  6. Investigating

    GitHub

    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.

  7. Monitoring

    GitHub

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

  8. Monitoring

    GitHub

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

  9. Resolved

    GitHub

    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. <br /><br />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. <br /><br />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.