GitHub Status · History · Incident #5202

RESOLVED

Actions and Codespaces APIs experiencing partial failures

Major · Started Jul 7, 2026 · 2:14 PM

  • Duration

    2h 2m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

Actions and Codespaces APIs experiencing partial failures

On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests, though retries were frequently successful. In-progress Actions runs and Codespaces were not impacted and continued successfully. This was due to a recent change that did not deliver the expected performance and, under certain conditions, caused downstream errors.<br /><br />We mitigated the incident by rolling back the change, after which the affected services recovered.<br /><br />We are working to improve the resilience of our services to these conditions and to strengthen our monitoring to reduce our time to detection and mitigation of issues like this one in the future.


  • Started

    Jul 7, 2026 · 2:14 PM

  • Resolved

    Jul 7, 2026 · 4:17 PM

  • Duration

    2h 2m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Jul 7 · 2:14 PM GitHub

    We are investigating reports of degraded performance for Actions and Codespaces

  • Investigating

    Jul 7 · 2:14 PM GitHub

    Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time.<br /><br />Actions runs in progress are continuing successfully.

  • Investigating

    Jul 7 · 2:32 PM GitHub

    Codespaces is experiencing degraded availability. We are continuing to investigate.

  • Investigating

    Jul 7 · 2:47 PM GitHub

    Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time.  Retries may be successful.<br /><br />Actions runs and codespaces  in progress are continuing successfully.<br /><br />We are continuing to investigate the source of these errors.

  • Investigating

    Jul 7 · 3:06 PM GitHub

    Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful.<br /><br />We continue to investigate the source of these errors.

  • Investigating

    Jul 7 · 3:50 PM GitHub

    Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation.

  • Investigating

    Jul 7 · 4:00 PM GitHub

    We have rolled out the mitigation and are seeing recovery.

  • Monitoring

    Jul 7 · 4:02 PM GitHub

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

  • Resolved

    Jul 7 · 4:17 PM GitHub

    On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests, though retries were frequently successful. In-progress Actions runs and Codespaces were not impacted and continued successfully. This was due to a recent change that did not deliver the expected performance and, under certain conditions, caused downstream errors.<br /><br />We mitigated the incident by rolling back the change, after which the affected services recovered.<br /><br />We are working to improve the resilience of our services to these conditions and to strengthen our monitoring to reduce our time to detection and mitigation of issues like this one in the future.

Get alerted before the next GitHub outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free