Increased latency with webhooks

What to do

• Check whether you use GitHub Webhooks. 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 2h it lasted.

  Anything that failed between 2026-06-15 15:37 UTC and 2026-06-15 17:37 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 4

1. investigatingJun 15, 2026, 3:37 PM UTC

   We are investigating reports of degraded performance for Webhooks

   provider

2. investigatingJun 15, 2026, 4:39 PM UTC

   Webhooks delivery latency has returned to normal levels. The backlog that built up during the incident has been cleared at approximately 4:29 UTC. We consider this incident resolved.

   provider

3. monitoringJun 15, 2026, 4:39 PM UTC

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

   provider

4. resolvedJun 15, 2026, 5:37 PM UTC

   On June 15, 2026, between 15:27 UTC and 16:23 UTC, GitHub webhook deliveries were delayed. During this window, webhook events were delivered later than normal, with average end-to-end delivery latency peaking at approximately 8.8 minutes. No webhook deliveries were lost — delayed events were queued and delivered once processing recovered. This was caused by a temporary throughput constraint in an internal event-processing system that moves webhook events through GitHub's delivery pipeline. The rate at which events were processed for delivery dropped below the incoming volume, creating a backlog. We restarted the affected pipeline service, after which throughput recovered and the backlog fully drained by approximately 16:29 UTC. Webhook delivery latency returned to normal, the incident was mitigated at 16:39 UTC, and fully resolved at 17:37 UTC. To reduce the likelihood and impact of similar incidents, we are working on improving the accuracy of the utilization metrics used to scale our delivery worker pools, reviewing connection and capacity headroom in the delivery pipeline.

   provider

Corrections

None so far.

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