GitHub is recovering from a widespread outage that affected its website, API, Actions, Pull Requests and several other services used by developers worldwide. The Microsoft-owned platform said it has identified the problematic component and taken corrective action, but some error rates remain elevated. According to GitHub’s latest status update at 10:06 PM IST on August 17, the company said there are ‘strong signs of recovery’ but engineers are still working to completely restore the service.
“We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate,” GitHub status posted on X.
The outage started around 9:30 Pm, with the Microsoft-owned platform initially reporting performance problems across some of its services. The issue then expanded to several important developer tools, including API requests, GitHub Actions, Webhooks, Issues and Pull Requests.
“We identified the problematic component and have taken corrective actions. There are strong signs of recovery but we are still working to completely restore service, with error rates still remaining slightly elevated. We will post further updates as recovery continues,” GitHub said.
At around 9:46 PM IST, the platform said it was seeing error rates of around 20 per cent across its web experience and API traffic.
The outage also affected enterprise and authentication-related services. GitHub said SAML and OIDC authentication, SCIM and Team Sync were impacted during the incident.
Earlier, GitHub said it was still trying to identify the root cause and had started mitigation efforts. However, the company has now confirmed that they have identified the “problematic component and taken corrective action.”
The outage has affected developers who use GitHub for hosting code, managing repositories, reviewing Pull Requests and running automated workflows. User reports also showed problems accessing repositories and other GitHub services during the disruption.
The platform has not yet provided a detailed explanation of what caused the component to fail. The company said it will continue posting updates as recovery progresses.
Currently, the services are recovering but users may continue to see errors or degraded performance until the restoration is fully completed.
