GitHub Copilot · 76d ago
Incident With Blocked GitHub.com Traffic
ResolvedYes — GitHub Copilot had a problem on July 24, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “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.”
Timeline
Started: 7/24/2026, 3:56:48 PM
Last update: 7/24/2026, 3:56:48 PM
Resolved: 7/24/2026, 11:00:00 AM
Updates
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.
7/24/2026, 3:56:48 PM
More GitHub Copilot incidents
- Incident with Git Operations, Issues, Actions and Pull Requests — resolved, 20h ago
- Incident with Git Operations, Pull Requests and Actions — resolved, 22h ago
- Several services are degraded — resolved, 2d ago
- Incident with Actions — resolved, 3d ago
- Disruption with some GitHub services — resolved, 3d ago
- Elevated request latency — resolved, 7d ago