Skip to content

Incident detail

Actions and Codespaces APIs experiencing partial failures

Actions and Codespaces APIs experiencing partial failures

Resolved incidentMajor1 affected service

Timeline window

to

Sponsored placement

Google AdSense placeholder

This slot is reserved for future AdSense placement. It stays as a non-invasive placeholder until a client ID and slot ID are configured.

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    We are investigating reports of degraded performance for Actions and Codespaces

  2. Investigating

    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.

  3. Investigating

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

  4. Investigating

    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.

  5. Investigating

    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.

  6. Investigating

    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.

  7. Investigating

    We have rolled out the mitigation and are seeing recovery.

  8. Monitoring

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

  9. Resolved

    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.