This summary is created by Generative AI and may differ from the actual content.
Overview
On September 10, 2025, between 13:00 and 14:15 UTC, GitHub Actions users experienced failed jobs and run start delays for Ubuntu 24 and Ubuntu 22 jobs on standard runners in private repositories. Additionally, larger runner customers faced run start delays for runner groups with private networking configured in the eastus2 region. This incident was caused by an outage in an underlying compute service provider in the eastus2 region. GitHub is working on improvements to enhance resilience to single partner region outages for standard runners.Impact
1.06% of Ubuntu 24 jobs and 0.16% of Ubuntu 22 jobs failed. Additionally, jobs for larger runners utilizing private networking in the eastus2 region were completely unable to start throughout the incident.Trigger
An outage in an underlying compute service provider located in the eastus2 region.Detection
The team became aware of the degraded performance for Actions through reports, which initiated an investigation.Resolution
The incident was resolved, likely due to the underlying compute service provider's outage in the eastus2 region being mitigated or resolved. No specific immediate resolution steps taken by GitHub during the incident are detailed in the postmortem.Root Cause
The root cause of the incident was an outage experienced by an underlying compute service provider in the eastus2 region.
