On August 17, 2026, GitHub, the world’s leading code-hosting platform, experienced a significant service disruption that began around 13:40 UTC. This outage has affected developers, enterprises, and DevOps teams globally, with core services such as Pull Requests, Issues, Actions, Webhooks, and Copilot facing degraded performance for over two hours.
According to GitHub’s official status page, the platform is encountering error rates of approximately 20% across general web experiences and API traffic. This rate has remained consistent despite ongoing mitigation efforts by GitHub’s engineering team.
Specific functions are experiencing even more severe issues. Archive downloads and raw repository content downloads are failing at an estimated 50% error rate, significantly impacting the reliability of these operations during the incident.
Enterprise customers are particularly affected, as SAML and OIDC authentication, SCIM provisioning, and Team Sync services are all impacted. This disruption threatens single sign-on access for organizations relying on GitHub Enterprise Cloud.
The progression of the outage has been gradual. GitHub first acknowledged performance issues at 13:40 UTC, subsequently confirming degraded performance in API Requests, Actions, and Webhooks within the following hour. Issues and Pull Requests were added to the list of affected services shortly after, with Copilot joining around 14:31 UTC. Independent monitoring service Downdetector reported a spike in user complaints near 13:30 UTC, aligning with GitHub’s timeline. Microsoft, GitHub’s parent company, has also confirmed the platform is experiencing worldwide issues.
As of the latest update, GitHub’s engineering team is performing mitigations based on their investigation and monitoring for improvement. However, a root cause has not been publicly disclosed. The pattern of escalating status updates without a clear culprit suggests the underlying issue may be related to infrastructure-level saturation or a cascading failure across dependent services, though specifics have not been confirmed.
For individual developers, the outage means pull requests may fail to merge, CI/CD pipelines built on Actions could stall or error out, and issue tracking may become unreliable. Teams relying on webhooks for automation, such as triggering deployments or notifying chat tools, should expect delayed or dropped events until the platform stabilizes.
Currently, there is no user-side workaround. Affected teams are advised to delay non-critical repository operations and monitor GitHub’s status page directly for real-time updates, rather than relying on cached dashboards.
This incident occurs just months after GitHub introduced a more transparent status-reporting framework in April 2026, which includes granular severity tiers and 90-day uptime metrics for each individual service. This framework provides unusually detailed visibility into the current outage compared to past disruptions.
GitHub has not yet provided an estimated time for resolution and is expected to publish a full incident postmortem once services are restored, consistent with its monthly availability report practice.
This outage underscores the critical reliance of the global development community on GitHub’s services. It highlights the importance of robust infrastructure and transparent communication during service disruptions. Developers and organizations should consider implementing contingency plans and diversifying their toolsets to mitigate the impact of such incidents in the future.
