Incident with Git Operations

What to do

• Check whether you use GitHub Git Operations. 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 1h 44m it lasted.

  Anything that failed between 2026-11-03 20:57 UTC and 2026-11-03 22:41 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 6

1. investigatingNov 3, 2026, 8:57 PM UTC

   We are investigating reports of degraded performance for Git Operations

   provider

2. investigatingNov 3, 2026, 9:37 PM UTC

   We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery.

   provider

3. investigatingNov 3, 2026, 10:05 PM UTC

   Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.

   provider

4. investigatingNov 3, 2026, 10:37 PM UTC

   We are seeing significant improvement, though some Git Operations may be slow for a small set of customers. We are marking this as mitigated and will continue to monitor.

   provider

5. monitoringNov 3, 2026, 10:37 PM UTC

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

   provider

6. resolvedNov 3, 2026, 10:41 PM UTC

   This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

   provider

Corrections

None so far.

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