GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Elevated request latency

ResolvedminorOfficial source confirmedFirst recorded update Oct 1, 2026, 01:37 PM · Resolved Oct 1, 2026, 01:57 PM

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...

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Updates (4)

  1. Oct 1, 2026, 01:57 PM
    Elevated request latency

    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 infrastructu

    GitHub ↗
  2. Oct 1, 2026, 01:51 PM
    Elevated request latency

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

    GitHub ↗
  3. Oct 1, 2026, 01:39 PM
    Elevated request latency

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

    GitHub ↗
  4. Oct 1, 2026, 01:37 PM
    Elevated request latency

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

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.