Delays for Pull Requests and Webhook deliveries
On October 21, 2026, between 13:22 UTC and 19:22 UTC, several GitHub services were delayed due to degradation of our internal event streaming platform. <br /><br />Pull request updates, push webhooks, and push-triggered Actions workflows were delayed by up to 33 minutes until 15:36 UTC. Actions status updates were delayed by up to 33 minutes until 16:16 UTC, holding up some merges and deployments that wait on checks. Webhook deliveries and live updates were delayed by up to 25 minutes until 16:52 UTC. Audit log events were delayed by up to two hours. <br /><br />This was due to servers in the platform running out of memory caused by client reconnections without sufficient retry backoff. We mitigated the incident by moving the busiest workloads to less-loaded servers and adding capacity. <br /><br />We have since added reconnection backoff and added server capacity. We are building a solution for auto-rebalancing connections across servers, and splitting the platform into smaller, isolated clusters to reduce blast radius and time to mitigation of issues like this one in the future.
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.
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.
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.
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.
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.
Actions and Webhooks are operating normally.
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.
Pull Requests is operating normally.
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.
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.
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.
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.
Actions is experiencing degraded performance. We are continuing to investigate.
We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
เกี่ยวกับข้อมูลนี้
ข้อมูลเหตุขัดข้องของ GitHub มาจากไหน?
ข้อมูลมาจากหน้าสถานะทางการของ GitHub ซิงค์ทุก 5 นาที และครอบคลุม 90 วัน หน้ารายละเอียดมีลิงก์ไปยังรายงานต้นฉบับ
อ่านแถบสถานะส่วนประกอบอย่างไร?
แต่ละช่องคือหนึ่งวัน สีเขียวคือไม่มีรายงานปัญหา สีเหลืองคือประสิทธิภาพลดลง สีแดงคือขัดข้องรุนแรง สีเทาคือไม่มีข้อมูล สถิติครอบคลุม 90 วันที่ผ่านมา
ทำไมบางบริการจึงไม่มีประวัติ?
แสดงเฉพาะบริการที่มีหน้าสถานะทางการแบบสาธารณะ
คำนวณระยะเวลาอย่างไร?
นับจากเวลาเริ่มตามรายงานทางการจนถึงเวลากู้คืน หรือถึงเวลาปัจจุบันหากยังไม่สิ้นสุด เหตุการณ์หลายวันจะแสดงในทุกวันที่ได้รับผลกระทบ
ดูรายการบริการและสถานะปัจจุบันใน ภาพรวมสถานะ