Major impactResolvedDevOps

GitHub outage: Actions and Codespaces APIs experiencing partial failures

GitHub reported this major-impact incident on its official status page on Jul 7, 2026, 14:14 UTC. It was resolved after 2h 3m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Jul 7, 2026, 14:14 UTC
started
Jul 7, 2026, 16:17 UTC
resolved
2h 3m
duration
Major
impact
  1. resolvedJul 7, 2026, 16:17 UTC

    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.We mitigated the incident by rolling back the change, after which the affected services recovered.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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub outage on Jul 7, 2026: Actions and Codespaces APIs experiencing partial failures · APIStatus.watch