• Sources: primary
  • Summary: GitHub began investigating degraded performance for Git Operations at 20:57 UTC on 2026-11-03. It identified the issue and started a mitigation at 21:37 UTC, and at 22:05 UTC said the rollout was complete and customers should see improvement. The incident was not yet marked resolved.
  • Why it matters: Clones, fetches and pushes against GitHub may have been slow or failing, which can break CI runs and deploys during that window.
  • Follow-up: Resolution and a root cause in GitHub's availability report.