GitHub Copilot incident

Degraded performance for multiple GitHub services

Minor Resolved Upstream link ↗

Started

November 5, 2026 at 11:36 PM UTC

Duration

44 min

Resolved

November 6, 2026 at 12:20 AM UTC

Updates timeline

  1. Investigating

    We are investigating reports of degraded performance for Actions and Pages

  2. Investigating

    We're investigating degraded performance and errors affecting several GitHub services, including Git operations, Issues, Actions, and API access. Some users may see failed requests or slow responses. We'll post another update by 00:05 UTC.

  3. Investigating

    Issues is experiencing degraded performance. We are continuing to investigate.

  4. Monitoring

    The degradation affecting Actions, Issues and Pages has been mitigated. We are monitoring to ensure stability.

  5. Monitoring

    We've applied a mitigation and are seeing recovery across affected services, including Git operations, Issues, Actions, and API access. We're monitoring to confirm stability and will post another update by 00:35 UTC.

  6. Investigating

    Git Operations is operating normally.

  7. Monitoring

    This incident has been resolved. All affected services, including Git operations, Issues, Actions, and API access, have recovered and remained stable. Thank you for your patience. We'll share more details in our availability report.

  8. Resolved

    On November 5, 2026, between 23:21 and approximately 23:26 UTC, several GitHub services experienced elevated errors, including Git operations, Issues, Actions, authentication, and API requests. Customers may have encountered failed requests and Git pushes, and some Actions workflow runs were delayed. <br /><br />This incident was caused by a bug in our database failover automation during planned maintenance. The automation stopped before completing the switch to a replacement database primary, leaving the existing primary unable to accept writes. We mitigated the disruption by restoring writes on the original primary. We subsequently completed the maintenance and monitored services to confirm recovery. <br /><br />We are fixing the automation bug and strengthening our pre-maintenance checks and recovery procedures to prevent similar disruptions and restore service more quickly if a failure occurs.

Get an email the next time GitHub Copilot goes down

Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

Live GitHub Copilot status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader