"is investigating reports of performance problems affecting some of its services," GitHub wrote at 9:40 AM EDT on August 17, 2026 — a line that marked the start of a fast-moving, widespread outage affecting large parts of the platform developers depend on.
Timeline: confirmation, spread, and Copilot impact
GitHub confirmed the outage at 9:40 AM EDT on August 17, 2026 and said it was investigating performance problems affecting some services. Within an hour the incident had expanded: at 10:31 AM EDT GitHub confirmed that Copilot was experiencing degraded availability, extending the outage to the company's AI coding services. GitHub has not disclosed a cause and says its investigation is ongoing.
Which services are degraded and the measured error rates
According to GitHub's status page, the company is seeing error rates of around 20% across its web experience and API traffic. The outage has produced server errors for some users and intermittent failures for others when attempting to load commits, repositories, and Pull Request pages. Several core features developers rely on — API Requests, Actions, Webhooks, Issues, and Pull Requests — are explicitly reported as affected by the incident.

This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildRepository downloads and authentication services hit hardest
The problems are uneven across services. Archive downloads and raw repository content downloads are experiencing error rates of approximately 50%, according to the status reporting — a markedly higher failure rate than the general web and API traffic figures. Authentication-related services are also disrupted: SAML and OIDC authentication, SCIM, and Team Sync are listed as affected, which can prevent organizations from validating or synchronizing user access in affected environments.
CI/CD pipelines, automated workflows, and developer tooling
GitHub Actions is listed as experiencing degraded performance, which the company warned can affect automated builds, tests, deployments, and other workflows that depend on its CI/CD platform. That degradation, combined with issues in API, Webhooks, and Pull Requests, creates a compound impact on end-to-end developer workflows. Copilot — GitHub's AI coding service — was later confirmed to have degraded availability, broadening the incident from platform and CI components into developer-assist tooling.
How developers, enterprises, and CI/CD teams are affected
- Developers: Many users are encountering server errors when accessing repositories or pull requests and are seeing failures when loading commits and repo pages; archive and raw content downloads are failing for roughly half of attempts.
- CI/CD teams and build engineers: Degraded performance in GitHub Actions and webhooks can interrupt automated builds, tests and deployment pipelines that rely on GitHub for triggers, artifacts, or configuration.
- Enterprises and identity managers: With SAML, OIDC, SCIM, and Team Sync affected, organizations that depend on those services for authentication and team provisioning may face sign-on and synchronization failures until the issue is resolved.
Several components remain listed as operational — Git Operations, Packages, Pages, and Codespaces — even as multiple other services report degradation or elevated error rates. GitHub has not provided a root cause and continues to investigate, leaving developers and administrators to monitor the status page and mitigate where possible.
The event underscores the fragility that can follow when central developer platforms experience system-wide errors: a single outage can cascade from simple page loads to authentication flows and automated delivery pipelines. GitHub's public status metrics — 20% error rates for web/API traffic and ~50% for archive/raw downloads — give a numerical snapshot, but the company’s ongoing investigation will be the primary source for confirmation of cause and recovery timing.
Original reporting: BleepingComputer — "Microsoft confirms GitHub is down worldwide"




