GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Incident with Webhooks

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Aug 13, 2026, 02:45 PM · Resolved Aug 13, 2026, 03:36 PM

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,...

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Affected services

PackagesPull RequestsGit OperationsWebhooksIssues

Updates (9)

  1. Aug 13, 2026, 03:36 PM
    Incident with Webhooks

    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,

    GitHub ↗
  2. Aug 13, 2026, 03:33 PM
    Incident with Webhooks

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

    GitHub ↗
  3. Aug 13, 2026, 03:33 PM
    Incident with Webhooks

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

    GitHub ↗
  4. Aug 13, 2026, 02:58 PM
    Incident with Webhooks

    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.

    GitHub ↗
  5. Aug 13, 2026, 02:56 PM
    Incident with Webhooks

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

    GitHub ↗
  6. Aug 13, 2026, 02:46 PM
    Incident with Webhooks

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

    GitHub ↗
  7. Aug 13, 2026, 02:46 PM
    Incident with Webhooks

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

    GitHub ↗
  8. Aug 13, 2026, 02:46 PM
    Incident with Webhooks

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

    GitHub ↗
  9. Aug 13, 2026, 02:45 PM
    Incident with Webhooks

    We are investigating reports of degraded performance for Webhooks

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.