rewindex

CompaniesGitHub CopilotIncidents

GitHub Copilot: Degradation in repos contents API

MinorStatus: resolvedStarted Resolved (21 min)2 updatesstspg.io (opens in new tab)

Timeline of updates

  1. investigating

    We are investigating reports of impacted performance for some GitHub services.

  2. resolved

    On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.

    The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity sat idle. We resolved the incident by reverting the change and letting traffic rebalance.

    We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence.

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: minor) posted by GitHub Copilot, started 2026-09-04 22:02 UTC, resolved after 21 min, 2 update(s).

Title
Degradation in repos contents API
Vendor
GitHub Copilot
Date
URL
https://rewindex.com/company/github-copilot/incidents/r05vk75c594j

GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on September 4, 2026GitHub Copilot in September 2026MarkdownJSON