Degradation with Webhooks, Pull Requests and Actions
Summary
On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances. <br /><br />The issue was mitigated by replacing the problem node at 17:49, after which all services saw recove
Impact
major
Timeline
[investigating] We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
via statuspage[investigating] Actions is experiencing degraded availability. We are continuing to investigate.
via statuspage[investigating] Issues is experiencing degraded performance. We are continuing to investigate.
via statuspage[monitoring] The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
via statuspage[monitoring] We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered.
via statuspage[resolved] This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
via statuspage[resolved] On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances. <br /><br />The issue was mitigated by replacing the problem node at 17:49, after which all services saw recovery by 18:07.
via statuspageLessons Learned
⚠GitHub has experienced 114 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to api, routing have occurred 769 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: Network / Routing, API Issue. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Networking in BLR1
DigitalOcean · Jul 19, 2026
Service is operating normally: [RESOLVED] Inaccurate Estimated Billing Data
AWS · Jul 18, 2026
Service impact: Inaccurate Estimated Billing Data
AWS · Jul 18, 2026
Service impact: Inaccurate Estimated Billing Data
AWS · Jul 18, 2026
Service impact: Inaccurate Estimated Billing Data
AWS · Jul 17, 2026