GitHub Status · History · Incident #233

RESOLVED

Disruption with some GitHub services

Critical · Started May 6, 2026 · 11:21 AM

  • Duration

    38m

  • Severity

    Critical

  • Detection lead

  • User reports

Summary

Disruption with some GitHub services

On May 6, 2026 between 11:02 UTC and 11:13 UTC, users were unable to start or view Copilot Cloud Agent or remote sessions. During this time, requests to the session API returned errors, preventing users from creating new sessions or viewing existing ones. The issue was caused by a configuration change to the service's network routing that inadvertently removed the ingress path for the service. The team reverted the change at 11:13 UTC which restored service. The incident remained open until 11:59 UTC while the team verified full recovery. We are taking steps to improve our deployment validation process to prevent similar configuration changes from impacting production traffic in the future.


  • Started

    May 6, 2026 · 11:21 AM

  • Resolved

    May 6, 2026 · 11:59 AM

  • Duration

    38m

  • Severity

    Critical

Event timeline

How this incident unfolded

  • Investigating

    May 6 · 11:21 AM GitHub

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

  • Investigating

    May 6 · 11:25 AM GitHub

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

  • Investigating

    May 6 · 11:59 AM GitHub

    We have applied a mitigation and Copilot services have recovered.

  • Resolved

    May 6 · 11:59 AM GitHub

    On May 6, 2026 between 11:02 UTC and 11:13 UTC, users were unable to start or view Copilot Cloud Agent or remote sessions. During this time, requests to the session API returned errors, preventing users from creating new sessions or viewing existing ones. The issue was caused by a configuration change to the service's network routing that inadvertently removed the ingress path for the service. The team reverted the change at 11:13 UTC which restored service. The incident remained open until 11:59 UTC while the team verified full recovery. We are taking steps to improve our deployment validation process to prevent similar configuration changes from impacting production traffic in the future.

Get alerted before the next GitHub outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free
Hey there 👋  Friends from designmodo are here to help!