GitHub Outage Hit Actions And Enterprise Login Paths In Global Disruption
DigiconAsia reported that GitHub’s August 17 outage affected repositories, Actions, API traffic, archive downloads and enterprise identity tools, with Microsoft confirming worldwide platform issues.

GitHub’s August 17 outage disrupted the developer workflow rather than only the public website, DigiconAsia reported, with repository access, code-review queues, automation services and enterprise sign-in tools all affected during the same incident.
The affected services also covered the points where code changes move from review into production, including pull requests, automated actions and identity-managed organization access.
The service timeline began at about 9:40 a.m.
EDT, when GitHub acknowledged reduced performance.
By 10:31 a.m., the affected surface included API Requests, Actions, Webhooks, Issues, Pull Requests and GitHub Copilot, placing both manual development work and automated delivery pipelines inside the disruption.
GitHub’s own update on X put web and API error rates near 20%.
Archive and raw-file retrieval was failing at an estimated 50%, a level that could interrupt teams pulling source packages, running build scripts or using automated tooling that depends on repository downloads rather than browser access alone.
Enterprise access controls created a second operational problem.
SAML and OIDC sign-in, SCIM user provisioning and Team Sync were among the affected functions, so companies using single sign-on risked losing access to organization resources even when their internal credentials remained valid.
User reports showed the incident spreading beyond one market.
Downdetector showed user complaints in both the United States and India.
In India, 79% of complaints involved access to the GitHub website, while other users pointed to login failures or app problems.
Microsoft, GitHub’s parent company, confirmed that platform problems were appearing worldwide.
The timing placed the disruption in a wider run of Microsoft-platform reliability issues, following an Xbox services outage late in the previous month.
GitHub had also recorded a separate Actions incident on August 6, when 71% of workflow runs failed because of infrastructure problems.
For engineering teams, the repeated failures put the reliability of code hosting, automated testing and deployment workflows in the same operational frame.




















