Skip to content- Sources: primary
- Summary: On 2026-10-05, Actions jobs sat queued for about 3 hours 45 minutes. A partial cloud network failure made the runner assignment service wait on timeouts until it ran out of memory, and the failover region lacked capacity. The 2026-10-07 write outages exposed an unsafe interaction between database orchestration and production routing. A 2026-10-29 Azure network disruption hit all three Central US availability zones and at least 34,128 signed-in users. The East US 3 buildout is a week late, with its first traffic ramp due in the first week of December.
- Why it matters: Teams that depend on hosted Actions runners should expect more migration risk through December and plan around queued jobs during regional failover.