• Sources: primary, discussion
  • Summary: GitHub opened an incident at 10:36 UTC on 2026-11-08 for degraded performance primarily affecting unauthenticated users, listed API Requests as degraded at 11:20 UTC, and said at 11:50 UTC it had identified a problematic component and was redeploying it. GitHub marked the degradation mitigated at 11:56 UTC, with the incident still in monitoring and no root cause published.
  • Why it matters: CI pipelines and installers that fetch release assets or tools from GitHub without a token can fail during these incidents, so authenticated fetches or a local mirror reduce exposure.
  • Follow-up: GitHub's root cause analysis for the 2026-11-08 incident.
  • Comments: The Hacker News thread drew 99 points and 96 comments. Users reported 504 and 503 errors for logged-out web and release downloads while logged-in browsing worked, broken CI steps that fetch tools such as gitleaks, failing Nix and Elixir builds, and Terraform runs that could not download providers. Several noted the status page stayed green for roughly an hour before the incident was posted.