Incident with Actions, we are investigating reports of degraded availability

Summary

Incident with Actions, we are investigating reports of degraded availability

On May 6, 2026, from approximately 06:45 UTC to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were degraded. 17.1% of jobs requesting a standard runner failed.<br /><br />This was caused by an unexpected data shape in the allocation configuration data for standard runners. That data was introduced as part of post-incident remediation work for an incident the previous day and caused new allocations to be blocked as load ramped up for the day. Removing that data at 08:51 allowed allocations to proceed and hosted runner pools to scale up and recover.<br /><br />We are updating the filter logic for this allocation data to be resilient to abnormal data shapes and improving monitoring to alert when allocations are blocked, allowing the team to respond before customer impact starts.

• Started

  May 6, 2026 · 7:19 AM

• Resolved

  May 6, 2026 · 9:44 AM

• Duration

  2h 25m

• Severity

  Major

• ◐

  Investigating

  May 6 · 7:19 AM GitHub

  We are investigating reports of degraded availability for Actions

• ◐

  Investigating

  May 6 · 8:00 AM GitHub

  Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue

• ◐

  Investigating

  May 6 · 9:08 AM GitHub

  We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.

• ◉

  Monitoring

  May 6 · 9:19 AM GitHub

  The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

• ◉

  Monitoring

  May 6 · 9:44 AM GitHub

  Actions wait times have fully recovered.

• ✓

  Resolved

  May 6 · 9:44 AM GitHub

  On May 6, 2026, from approximately 06:45 UTC to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were degraded. 17.1% of jobs requesting a standard runner failed.<br /><br />This was caused by an unexpected data shape in the allocation configuration data for standard runners. That data was introduced as part of post-incident remediation work for an incident the previous day and caused new allocations to be blocked as load ramped up for the day. Removing that data at 08:51 allowed allocations to proceed and hosted runner pools to scale up and recover.<br /><br />We are updating the filter logic for this allocation data to be resilient to abnormal data shapes and improving monitoring to alert when allocations are blocked, allowing the team to respond before customer impact starts.