GitHub incident

Disruption with some GitHub services

Critical Resolved View vendor source →

GitHub experienced a critical incident on May 6, 2026, lasting 38m. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 11:21 AM UTC
Resolved
May 06, 2026, 11:59 AM UTC
Duration
38m
Detected by Pingoru
May 06, 2026, 11:21 AM UTC

Update timeline

  1. investigating May 06, 2026, 11:21 AM UTC

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

  2. investigating May 06, 2026, 11:25 AM UTC

    We are investigating issues with the ability to start Copilot Cloud Agent sessions and view them.

  3. investigating May 06, 2026, 11:59 AM UTC

    We have applied a mitigation and Copilot services have recovered.

  4. resolved May 06, 2026, 11:59 AM 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.

Looking to track GitHub downtime and outages?

Pingoru polls GitHub's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GitHub reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GitHub alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GitHub for free

5 free monitors · No credit card required