Degradation with Webhooks, Pull Requests and Actions

Summary

Degradation with Webhooks, Pull Requests and Actions

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.

• Started

  Jun 25, 2026 · 5:50 PM

• Resolved

  Jun 25, 2026 · 6:27 PM

• Duration

  37m

• Severity

  Major

• ◐

  Investigating

  Jun 25 · 5:50 PM GitHub

  We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks

• ◐

  Investigating

  Jun 25 · 5:53 PM GitHub

  Actions is experiencing degraded availability. We are continuing to investigate.

• ◐

  Investigating

  Jun 25 · 5:58 PM GitHub

  Issues is experiencing degraded performance. We are continuing to investigate.

• ◉

  Monitoring

  Jun 25 · 6:07 PM GitHub

  The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

• ◉

  Monitoring

  Jun 25 · 6:27 PM GitHub

  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.

• ✓

  Resolved

  Jun 25 · 6:27 PM GitHub

  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.