rewindex

CompaniesGitHub CopilotIncidents

GitHub Copilot: Degraded Git Operations over SSH

No impact listedStatus: resolvedStarted Resolved (-3919 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. resolved

    On August 21, 2026, between 14:00 and 14:07 UTC, dotcom Git operations over SSH were degraded. Successful Git operations over SSH fell by more than 95% for during the peak impact window, making clone, fetch, or push over SSH effectively unavailable to most users for approximately four minutes. Git operations over HTTPS were not affected.

    The incident was caused by a software defect in our load-balancing infrastructure that was triggered by a configuration change. The defect only occurred when connections passed through multiple layers of load balancers running the new configuration, which meant it was not detected during canary testing.

    We mitigated the incident by rolling back the configuration change.

    We are adding regression coverage for multi-layer load-balancer configurations and improving monitoring and alerting for Git operations over SSH to reduce our time to detection and mitigation of similar issues in the future.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by GitHub Copilot, started 2026-08-24 07:19 UTC, resolved after -3919 min, 1 update(s).

Title
Degraded Git Operations over SSH
Vendor
GitHub Copilot
Date
URL
https://rewindex.com/company/github-copilot/incidents/wms44hv62t3p

GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on August 24, 2026GitHub Copilot in August 2026MarkdownJSON