Webhook delivery is delayed

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 56m it lasted.

  Anything that failed between 2026-03-18 18:51 UTC and 2026-03-18 19:46 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 3

1. investigatingMar 18, 2026, 6:51 PM UTC

   We are investigating reports of degraded performance for Webhooks

   provider

2. investigatingMar 18, 2026, 7:25 PM UTC

   We are seeing recovery and are continuing to monitor the latency for webhook deliveries

   provider

3. resolvedMar 18, 2026, 7:46 PM UTC

   On March 18, 2026, between 18:18 UTC and 19:46 UTC all webhook deliveries experienced elevated latency. During this time, average delivery latency increased from a baseline of approximately 5 seconds to a peak of approximately 160 seconds. This was due to resource constraints in the webhook delivery pipeline, which caused queue backlog growth and increased delivery latency. We mitigated the incident by shifting traffic and adding capacity, after which webhook delivery latency returned to normal. We are working to improve capacity management and detection in the webhook delivery pipeline to help prevent similar issues in the future.

   provider

Corrections

None so far.

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