rewindex

CompaniesGitHub CopilotIncidents

GitHub Copilot: Incident With Blocked GitHub.com Traffic

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatewww.githubstatus.com (opens in new tab)

Timeline of updates

  1. resolved

    Between July 23, 2026 at 18:45 UTC and July 24, 2026 at 11:19 UTC, an abuse mitigation update caused some legitimate customers whose traffic was routed through our Central Europe and South America edge locations to be incorrectly blocked from GitHub.com. We estimate that approximately 0.25% of GitHub.com requests were affected during this period. This was caused by an abuse mitigation configuration that incorrectly classified legitimate traffic. We mitigated the incident by reverting the update. We are adding validation and safeguards to prevent similar incorrect blocking in the future.

From GitHub Copilot’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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.

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

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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

Cite this

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

Title
Incident With Blocked GitHub.com Traffic
Vendor
GitHub Copilot
Date
URL
https://rewindex.com/company/github-copilot/incidents/594m87r8sw13

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