Resolved after 6 hours 42 minutes, affecting GitHub Runners and Northern Virginia, US, on October 6, 2026.
We see partial recovery after mitigations were applied, but networking continues to show degradation in the high percentiles. The team is working on deploying additional capacity to work towards a full recovery.
Affected components
Update timeline
- identified Oct 06, 2026, 04:43 PM UTC
We're seeing increased queue time for a subset of jobs, the team is working on mitigation.
- identified Oct 06, 2026, 05:06 PM UTC
We're seeing severely degraded checkout performance, we're investigating the cause. This causes to increased runtime and concurrency exhaustion, leading to increased queue time.
- identified Oct 06, 2026, 05:27 PM UTC
Checkout performance continues to be degraded, the team is root-causing the issue and working on mitigation options.
- identified Oct 06, 2026, 05:57 PM UTC
We continue seeing degraded networking performance, the team is working on establishing an alternative transit path.
- identified Oct 06, 2026, 07:29 PM UTC
We see partial recovery after mitigations were applied, but networking continues to show degradation in the high percentiles. The team is working on deploying additional capacity to work towards a full recovery.
- resolved Oct 06, 2026, 11:26 PM UTC
All systems are operational.
Your product runs on more than Namespace
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services