Delays for Pull Requests and Webhook deliveries

Summary

Delays for Pull Requests and Webhook deliveries

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.

• Started

  Oct 21, 2026 · 2:52 PM

• Resolved

  Oct 21, 2026 · 7:22 PM

• Duration

  4h 30m

• Severity

  Critical

• ◐

  Investigating

  Oct 21 · 2:52 PM GitHub

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

• ◐

  Investigating

  Oct 21 · 3:15 PM GitHub

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

• ◐

  Investigating

  Oct 21 · 3:36 PM GitHub

  We are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these mitigations take effect.

• ◐

  Investigating

  Oct 21 · 3:58 PM GitHub

  We continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.

• ◐

  Investigating

  Oct 21 · 4:17 PM GitHub

  Audit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.

• ◐

  Investigating

  Oct 21 · 4:25 PM GitHub

  Audit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will share further updates as we learn more.

• ◐

  Investigating

  Oct 21 · 4:33 PM GitHub

  Pull Requests is operating normally.

• ◐

  Investigating

  Oct 21 · 4:34 PM GitHub

  Audit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more.

• ◐

  Investigating

  Oct 21 · 4:57 PM GitHub

  Actions and Webhooks are operating normally.

• ◐

  Investigating

  Oct 21 · 4:59 PM GitHub

  Actions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues.

• ◐

  Investigating

  Oct 21 · 5:09 PM GitHub

  Pull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates.

• ◐

  Investigating

  Oct 21 · 6:18 PM GitHub

  Audit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow.

• ◐

  Investigating

  Oct 21 · 6:52 PM GitHub

  Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates.

• ◐

  Investigating

  Oct 21 · 7:22 PM GitHub

  Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed.

• ✓

  Resolved

  Oct 21 · 7:22 PM GitHub

  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.