Skip to content
GitHub · Developer toolsJun 11, 2026, 19:42 UTC

Incident with Webhooks

MinorStorageUpdated 16h ago
Jun 11, 19:42 UTCJun 11, 22:19 UTC
Duration
2h 37m
Impact
Minor
Root cause
Storage
GitHub, 90 days
68 incidents
Affected
Not listed by the vendor.
Status page

Final update

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.

Timeline

  1. Resolved · Jun 11, 22:19 UTC
    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.

More from GitHub

Full history
StartedIncidentDuration
Sep 2310:11 UTCIncident across several servicesOngoing
Sep 2022:13 UTCIncident with Pull Requests1h 9m
Sep 1720:59 UTCElevated rate of errors for OpenAI models provided by Copilot50m
Sep 1607:20 UTCDegradation with Gemini 3.8 Flash10h 28m
Sep 1519:11 UTCDisruption with some GitHub services49m
Sep 1509:47 UTCDisruption with some GitHub services1h 30m

Also caused by storage

All
StartedIncidentDuration
Sep 1715:50 UTCAutoOps node metrics temporarily unavailable in some regionsElastic41m
Sep 1015:26 UTCUnresponsive ProjectsSupabase27h 40m
Jul 1909:51 UTCBlock Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1DigitalOcean5h 41m
Mar 720:07 UTCOutage for prod-eu-central-0 due to AWS S3 outage.Grafana Labs36h 52m
Mar 719:53 UTCIncreased Error RatesAWS1h 11m
Nov 2808:28 UTCDelayed Logs in EU RegionMailgun10h 46m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.