Elevated request latency

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.

  Anything that failed between 2026-10-01 13:37 UTC and 2026-10-01 13:57 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 4

1. investigatingOct 1, 2026, 1:37 PM UTC

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

   provider

2. investigatingOct 1, 2026, 1:39 PM UTC

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

   provider

3. monitoringOct 1, 2026, 1:51 PM UTC

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

   provider

4. resolvedOct 1, 2026, 1:57 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.