Minor impactResolvedDevOps

GitHub incident: Elevated request latency

GitHub reported this minor-impact incident on its official status page on Oct 1, 2026, 13:37 UTC. It was resolved after 20 min.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Oct 1, 2026, 13:37 UTC
started
Oct 1, 2026, 13:57 UTC
resolved
20 min
duration
Minor
impact
  1. resolvedOct 1, 2026, 13:57 UTC

    On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returned to normal as the traffic subsided, and we have since applied additional traffic filtering to protect against similar traffic. We are improving alerting for delays in our traffic-handling infrastructure and strengthening our automated traffic protections to reduce our time to detection and mitigation.

  2. monitoringOct 1, 2026, 13:51 UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  3. investigatingOct 1, 2026, 13:39 UTC

    We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available.

  4. investigatingOct 1, 2026, 13:37 UTC

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

What APIStatus.watch saw

  • Oct 1, 2026, 14:50 UTCoperational → degraded

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 67 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 1h 15m. See GitHub's uptime and incident history