- Level
- confirmed
- Worst impact
- Degraded
- Components
- Webhooks
- Down Index
- 22of 100
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 38m it lasted.
Anything that failed between 2026-06-11 19:42 UTC and 2026-06-11 22:19 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 5
- investigating
We are investigating reports of degraded performance for Webhooks
provider
- investigating
We are currently experiencing delays in Web Hook delivery and are actively investigating the root cause.
provider
- investigating
We have applied a mitigation and are monitoring for recovery.
provider
- monitoring
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On June 11, 2026, between 19:28 UTC and 21:06 UTC, GitHub webhook deliveries were delayed. Average delivery latency peaked at approximately 3.4 minutes, with some deliveries delayed by as much as 62 minutes at the 99th percentile. No events were lost — delayed events were queued and delivered once processing caught up. This was due to a change in how webhook traffic was distributed across regions: to relieve load on one region, a portion of processing was shifted to another, where higher latency prevented our delivery workers from keeping pace with incoming volume, creating a backlog. We mitigated the incident by rebalancing webhook traffic distribution; as load returned to normal levels, processing caught up and the delivery backlog fully drained. We are working on improving the accuracy of the utilization metrics used to scale our delivery worker pools, and reassess how we distribute webhook traffic across regions, to reduce our time to detection and mitigation of issues like this one in the future.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-5865e05286
Is GitHub still down?
No, this incident was resolved 2026-06-11 22:19 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
2h 38m, from 2026-06-11 19:42 UTC to 2026-06-11 22:19 UTC, by the times GitHub posted.
What was affected?
GitHub named Webhooks.
What caused it?
GitHub hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.