GitHub Faces Extended Downtime
We independently review everything we recommend. When you buy through our links, we may earn a commission which is paid directly to our Australia-based writers, editors, and support staff. Thank you for your support!
Quick Read
- GitHub is dealing with a notable service disruption that affects downloads and authentication procedures.
- Enterprise identity solutions such as SAML and OIDC have been impacted.
- Efforts to restore services are in progress with intermittent issues still occurring.
Incident Overview
The code hosting service GitHub is actively working to address an incident that compromised several services overnight, at one point hindering nearly half of all archive and raw repository downloads. The Microsoft-owned platform raised awareness of the situation on August 17 at 11:40pm AEST, indicating that it was looking into reports of performance issues across various services.
Extent and Effects
In under 20 minutes, GitHub included API requests, Actions, webhooks, Issues, and pull requests on the affected services list. By 12:04am on August 18, the error rate had surged to approximately 20 percent for web and API traffic, with archive downloads and raw repository content experiencing a failure rate of about 50 percent. This elevated error frequency presented considerable difficulties for users who depend on the platform’s essential functionalities.
Impact on Enterprise Services
Enterprise clients were similarly impacted at the identity level, with GitHub acknowledging that SAML and OIDC authentication, SCIM provisioning, and Team Sync faced disruptions. These identity services are vital for smooth user authentication and provisioning processes.
Restoration Efforts
During the night, GitHub informed that the issues affecting API requests, Actions, Git operations, Issues, Pages, pull requests, and webhooks had been alleviated, and it was observing for consistent performance. Nevertheless, recovery has been inconsistent, with Git operations, Issues, and the API failing again within two hours of GitHub’s declaration of mitigation.
Ongoing Issues
“We are persistently examining ongoing authentication failures,” GitHub stated in an update, noting that it had partially disabled retries for authentication tokens, observed improvements, and was assessing the impact before fully implementing the mitigations. As per the latest information, neither the root cause nor the specific component responsible for the issue has been identified.
Conclusion
This week’s incident marked the 14th for GitHub this month, underscoring the persistent challenges in maintaining stable service. While GitHub aims for total recovery, users still encounter sporadic issues.
Reader questions
Frequently asked questions
Fast answers to the questions readers ask most about GitHub Faces Extended Downtime.
Which services were impacted during the outage?
The outage influenced numerous services including API requests, Actions, webhooks, Issues, pull requests, and identity solutions like SAML and OIDC.
How long did the outage persist?
The incident was initially reported on August 17, and while efforts to mitigate started promptly, full restoration was not immediate, with ongoing sporadic issues.
What triggered the GitHub outage?
As of the latest update, GitHub has not revealed the underlying cause of the outage.
How many outages has GitHub recorded this month?
The incident was the 14th documented by GitHub this month.
Were enterprise users impacted differently?
Yes, enterprise users faced challenges at the identity level, impacting authentication and provisioning services.
What measures is GitHub implementing to resolve the issue?
GitHub is actively monitoring the situation, has partially disabled authentication token retries, and is applying mitigations as improvements are detected.
