A widespread GitHub outage disrupted software development around the world on Monday, August 17, affecting the code-hosting platform's website, application programming interfaces, pull requests, automation tools and artificial-intelligence services. GitHub opened an incident at 13:40 UTC after receiving reports of impaired performance and said engineers were investigating multiple connected services.
GitHub's official status page reported error rates of about 20 percent across web experiences and API traffic during the incident. Downloads of repository archives and raw source-code content experienced error rates near 50 percent, while some users encountered server errors or could not reliably load commits, repositories and pull-request pages, according to GitHub and BleepingComputer.
The disruption spread across API Requests, Actions, Webhooks, Issues, Pull Requests, Pages and Git Operations. GitHub also reported degraded availability for Copilot, its AI coding assistant, from 14:31 UTC. Authentication and enterprise-management systems, including SAML and OIDC sign-in, SCIM provisioning and Team Sync, were affected, potentially blocking both individual developers and company teams from routine work.
GitHub said at 16:36 UTC that it had identified the problematic component and taken corrective action, with strong signs of recovery but slightly elevated error rates. It marked several services as mitigated at 16:59 UTC, yet later reported residual impact across numerous services. At 18:11 UTC, the company said sporadic authentication failures remained and that additional mitigations and investigation were continuing.
The outage mattered beyond access to stored code because GitHub Actions supports automated building, testing and deployment for many software projects. Failures or delays can therefore interrupt release pipelines and other continuous-integration processes even when local copies of code remain available. GitHub had not publicly identified the root cause by the latest status update, and there was no verified evidence that a cyberattack or AI traffic caused the disruption.
GitHub said it would continue applying mitigations and examining the remaining impact. Developers and organizations were advised through the incident record to monitor the official status page as recovery progressed. A detailed cause, the final duration and the full scale of customer impact were not yet available, leaving the incident open as of the latest verified update.
Comments