Minor impactResolvedDevOps

GitHub incident: Incident with Webhooks

GitHub reported this minor-impact incident on its official status page on Aug 13, 2026, 14:45 UTC. It was resolved after 51 min.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Aug 13, 2026, 14:45 UTC
started
Aug 13, 2026, 15:36 UTC
resolved
51 min
duration
Minor
impact

Affected components

  • Git Operations
  • Issues
  • Packages
  • Pull Requests
  • Webhooks
  1. resolvedAug 13, 2026, 15:36 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. <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 deleti

  2. monitoringAug 13, 2026, 15:33 UTC

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

  3. monitoringAug 13, 2026, 15:33 UTC

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

  4. investigatingAug 13, 2026, 14:58 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.

  5. investigatingAug 13, 2026, 14:56 UTC

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

  6. investigatingAug 13, 2026, 14:46 UTC

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

  7. investigatingAug 13, 2026, 14:46 UTC

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

  8. investigatingAug 13, 2026, 14:46 UTC

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

  9. investigatingAug 13, 2026, 14:45 UTC

    We are investigating reports of degraded performance for Webhooks

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.

How often does GitHub have incidents?

GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history

GitHub incident on Aug 13, 2026: Incident with Webhooks · APIStatus.watch