[CLSTR]
< Back to situations

Monitor this situation.

[SITUATION] · [QUIET] · [TECHNOLOGY]

2 clusters · 2 sources · 15 days · First seen · Last updated

GitHub service outages

Overview

GitHub experienced two significant service disruptions in late 2026.

On August 17, a major global outage lasted approximately eight hours, causing error rates of roughly 20% for web and API traffic and nearly 50% for archive and raw content downloads. The disruption affected core services including Pull Requests, Issues, Actions, Webhooks, and GitHub Copilot. GitHub attributed the incident to network saturation on load balancers in its Central US facility, caused by an Istio sidecar reaching concurrency limits and a misconfigured autoscaling policy. Recovery was hindered by a latent retry bug in Visual Studio Code. This outage occurred alongside the launch of Origin, a new Git-hosting platform from Cursor.

On September 1, GitHub Actions suffered another major outage. According to the official GitHub status page, this incident ranks as the second-longest major outage in the history of the service, preventing developers from running automated builds, tests, and code deployment procedures.

Entities

GitHub · GitHub Actions · Vlad Fedorov · Microsoft · Vladimir Fedorov

Timeline

  1. 10 days ago

    [TECHNOLOGY] 2 sources
    GitHub Actions suffers second-longest outage in its history

    GitHub Actions experienced its second-longest service outage in history, disrupting automated builds, testing, and code deployments for developers globally.

  2. 25 days ago

    [TECHNOLOGY] 27 sources
    GitHub suffers major global outage affecting core developer services

    GitHub suffered a major eight-hour global outage on August 17, affecting core services like API, Actions, and Copilot. The disruption coincided with the launch of Cursor's new AI-centric platform, Origin.

Sources

bithub.si · surfingcomplexity.blog