GitHub Experiences Major Global Outage Affecting API, Actions, Copilot and Multiple Core Services

On August 17, GitHub suffered a widespread outage that impacted nearly all major platform functions including the web interface, API, Issues, Pull Requests, Actions, Webhooks, Pages, Git Operations, and Copilot. Approximately 20% of requests to the site and API failed during peak impact, with archive and raw repository content loads reaching around 50% error rates. Corporate authentication mechanisms such as SAML and OIDC, along with SCIM and Team Sync services, were also disrupted while Codespaces remained operational. The incident began around 13:40 UTC with progressive degradation across components, prompting GitHub to identify and mitigate the root cause. Services are gradually recovering but error rates remain slightly elevated, and the incident has not yet been fully closed. Parallel issues were reported in other Microsoft services including Teams and Copilot, with unconfirmed speculation linking the event to Amazon Web Services network problems.

AntiMalwareTranslated from Russian

Read at source

GitHub encountered a significant global outage on 17 August that affected almost every core function of the platform.

Home users, corporations, and Microsoft services all reported problems as the disruption spread across the web interface, API, Issues, Pull Requests, Actions, Webhooks, Pages, Git Operations, and Copilot.

At the height of the incident roughly 20 percent of requests to the website and API returned errors, while loads of repository archives and raw content saw failure rates near 50 percent.

Enterprise authentication systems including SAML and OIDC, as well as SCIM and Team Sync, were also impacted.

Codespaces continued to function normally throughout the event.

The first signs of degradation appeared around 13:40 UTC, after which problems sequentially emerged in API Requests, Actions, Webhooks, Issues, Pull Requests, Copilot, Pages, and Git operations.

GitHub engineers identified the faulty component and applied remediation steps. Latest updates indicate services are recovering, although error levels remain marginally above normal and the incident remains open.

Users simultaneously reported issues with other Microsoft ecosystem products such as Teams and Copilot. Experts suggested a possible connection to network problems at Amazon Web Services, but GitHub has not officially confirmed this hypothesis or disclosed the root cause.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Other

Mail.ru Reduces Lifetime 1TB Cloud Storage Promo to Standard 8GB Quota for Select Users
Kimi K3 Open Model Surpasses Closed AI Leaders with Million-Token Context and 896 Experts
Innostage Completes Functional Testing of PT NGFW 1.10.3 Across 156 Criteria