Provider
GitHubIncident detail
Incident With Blocked GitHub.com Traffic
Resolved incidentMinor
Timeline window
to
Get alerted the next time GitHub breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update GitHub posted, oldest to newest, exactly as it appeared on their official status page.
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.
Keep exploring
More from GitHub
Neighboring incidents on GitHub's timeline and the rest of their record on OutageDeck.