GitHub reports multiple service issues

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.

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

We have rolled out the mitigation and are seeing recovery.

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.

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

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

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

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

We are investigating reports of degraded performance for Actions and Codespaces

On July 1, 2026, between approximately 00:00 UTC and 13:04 UTC, some GitHub Copilot customers whose budget was exhausted before the monthly reset remained incorrectly blocked from paid Copilot usage after the new billing month began, even though their budgets had reset. Some budget changes also took longer than usual to apply. Only customers with an exhausted budget were affected, which limited the impact.This was caused by a caching issue at the monthly reset: for some users, a pre-reset "budget exhausted" status was re-saved and served even though their budget had reset, so they stayed blocked. We had built a safeguard ahead of the reset to prevent this, but it did not take effect because an internal configuration service did not load its settings correctly. We resolved the incident by deploying a change that discards the outdated status and recomputes access from current budget data independently of that configuration, and by working through the backlog of budget updates.To prevent recurrence, we are ensuring pre-reset status cannot survive the monthly budget reset, adding alerting for this failure mode, and increasing capacity to absorb the monthly surge of budget updates.

The fix has been deployed globally and we are monitoring the results

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

A fix for the delayed resets is currently being deployed.

We have identified the likely reason for the delays and are working on a solution.

We are investigating reports of degraded performance for Copilot

Between 15:19 UTC and 15:49 UTC on June 30, 2026, users were unable to complete the signup flow for GitHub.com/signup. Approximately 62% of new user signups failed for about 30 minutes during this window.This was caused by a configuration change to the signup flow that unintentionally blocked users from completing signup.We mitigated the incident by reverting the change, which restored successful signups. To reduce the likelihood and impact of similar issues, we are adopting staged, incremental rollouts for changes on the signup path, improving our ability to test these changes before they reach production, and adding checks to verify signup health before and during any change that affects this flow.

We are investigating reports of impacted performance for some GitHub services.