GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Incident with Webhooks

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Jul 14, 2026, 05:38 PM · Resolved Jul 14, 2026, 06:01 PM

On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to not be written to our webhook deliveries store after being processed and delivered successfully. Affected deliveries would be missing from the webhook delivery UI and API and won’t be available for redelivery. The root cause was an uncoordinated rollout: a change to how delivery records are handed off between pipeline components was deployed before the upstream components producing those records were updated to match. While the rollout was in...

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

Webhooks

Updates (4)

  1. Jul 14, 2026, 06:01 PM
    Incident with Webhooks

    On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to not be written to our webhook deliveries store after being processed and delivered successfully. Affected deliveries would be missing from the webhook delivery UI and API and won’t be available for redelivery. The root cause was an uncoordinated rollout: a change to how delivery records are handed off between pipeline components was deployed before the upstream components producing those records were updated to match. While the rollout was in p

    GitHub ↗
  2. Jul 14, 2026, 05:55 PM
    Incident with Webhooks

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

    GitHub ↗
  3. Jul 14, 2026, 05:55 PM
    Incident with Webhooks

    Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when deliveries were accepted and processed. Customers may notice missing webhook deliveries in the UI, and these deliveries will not be retryable.<br /><br />Impact resolved automatically once the deployment completed.

    GitHub ↗
  4. Jul 14, 2026, 05:38 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.