- Sources: GitHub blocked-traffic incident, GitHub multi-service incident, GitHub pull requests incident, npm publish and install incident
- Summary: GitHub published three incidents dated 2026-07-24. An abuse-mitigation configuration update incorrectly classified legitimate traffic and blocked roughly 0.25% of GitHub.com requests routed through Central Europe and South America edge locations from 2026-07-23 18:45 UTC to 2026-07-24 11:19 UTC, mitigated by reverting the update. A separate incident from 16:17 to 17:36 UTC degraded API requests, Actions, Copilot, Issues, Pages, and Pull Requests. A third incident from 19:37 to 20:23 UTC was rated critical and affected pull request creation and availability. Separately, npm reported publish and install failures from 11:08 to 11:38 UTC on 2026-07-24, following intermittent failures the previous day. GitHub says root cause analyses will follow for the two service incidents.
- Why it matters: An edge abuse rule silently blocking a fraction of requests for 16 hours is the failure mode CI pipelines misread as flaky networking rather than a platform incident.
- Follow-up: Watch for the promised root cause analyses and for the validation safeguards GitHub says it is adding to abuse-mitigation changes.
send feedback on this story