On the evening of August 18, 2026, one of the key platforms of the global IT infrastructure — GitHub — became partially unavailable for millions of developers worldwide. Microsoft, the company owning the service, confirmed a large-scale incident affecting critical functions: from API and Actions to the authentication system and even its flagship AI assistant, Copilot. The outage began in the morning US Eastern Time (17:40 MSK), and by evening the situation had not been fully stabilized.
Scale of the Outage: From API to AI Assistant
According to the official GitHub status page, the error rate on the website and in API traffic reached 20%, while for loading archives and repository content it reached up to 50%. This means that every second request to download code or view commit history could end in an error. Services related to automation were particularly affected: GitHub Actions, Pages, and Codespaces. Developers reported failures in CI/CD pipelines, leading to the halt of builds, tests, and deployments in hundreds of companies.
Particular attention was drawn to the fact that GitHub Copilot — the AI tool for code generation, which has become a de facto standard for many programmers — was also hit. At 18:31 MSK, the company confirmed a reduction in Copilot availability, sparking a wave of criticism on social media: 'If even AI cannot help when the system crashes — that is a worrying signal'.
Authentication and Security: SAML, OIDC, SCIM
The outage affected not only functionality but also security. Authentication services — SAML, OIDC, SCIM, and Team Sync — became unavailable, making it impossible for corporate users utilizing Single Sign-On (SSO) to log in. This led to blocked access to internal repositories in major companies, including banks, fintech startups, and government agencies, where GitHub is used as part of the development infrastructure.
Contradictory Data
While GitHub officially states that the investigation is ongoing and the cause of the outage is currently unknown, some sources point to possible systemic issues accumulated over the last few months. According to VentureBeat, in May 2026 the platform already faced similar outages, and in June a visualization of 'red squares' was published, showing the frequency of downtime over the year. However, Microsoft in its statements emphasizes that the current incident is an 'isolated case' not related to long-term architectural problems.
Furthermore, rumors are circulating in the developer community that the outage may have been caused by an update to the authentication system or data migration to new data centers. However, none of these versions have been officially confirmed. GitHub is not disclosing details of the technical investigation, citing 'security policy'.
Competitors and Alternatives: Time for New Players?
The GitHub outage has once again raised the question of the need for alternative platforms. On the same day the outage occurred, the company Cursor launched its new platform Origin — a code hosting service with built-in AI, positioning it as a 'secure and reliable alternative to GitHub'. Experts note that such events could accelerate the migration of developers to other platforms, especially given the growing pressure from competitors and regular technical outages.
What's Next? Forecasts and Recommendations
At the moment, GitHub continues to work on restoring full functionality. The company promises to provide a detailed report following the investigation within 48 hours. Developers are advised to temporarily switch to local repositories, use caching, and avoid critical operations for the next few hours. Corporate clients are advised to check backups and configure alternative authentication channels.
This incident is yet another reminder of how vulnerable the global IT infrastructure is when dependent on a single service. And while GitHub remains the market leader, its stability is not just a technical issue, but a matter of national and economic security for many countries.
