GitHub incident

Incident with Actions

Critical Resolved View vendor source →

GitHub experienced a critical incident on May 5, 2026 affecting Actions, lasting 3h 48m. The incident has been resolved; the full update timeline is below.

Started
May 05, 2026, 01:37 PM UTC
Resolved
May 05, 2026, 05:26 PM UTC
Duration
3h 48m
Detected by Pingoru
May 05, 2026, 01:37 PM UTC

Affected components

Actions

Update timeline

  1. investigating May 05, 2026, 01:37 PM UTC

    We are investigating reports of degraded availability for Actions

  2. investigating May 05, 2026, 01:48 PM UTC

    We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs

  3. investigating May 05, 2026, 02:14 PM UTC

    We are investigating elevated queue times and failures on Actions Jobs running on Hosted Runners in East US affecting 8% of runs. Hosted Runners with private networking can fail over to a different Azure region to mitigate the issue.

  4. investigating May 05, 2026, 03:12 PM UTC

    We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US region affecting 10% of runs. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.

  5. investigating May 05, 2026, 03:54 PM UTC

    We've applied a mitigation for long queue times and failures on Standard Hosted Runners and are monitoring for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.

  6. investigating May 05, 2026, 04:33 PM UTC

    We've seen signs of recovery for Standard Hosted Runners and are continuing to monitor for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.

  7. investigating May 05, 2026, 05:11 PM UTC

    Standard hosted runners have now reached full recovery. Hosted Runners with Private Networking in the East US region remain degraded as we continue working with our compute provider to restore capacity. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.

  8. investigating May 05, 2026, 05:11 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  9. resolved May 05, 2026, 05:26 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.