GitHub incident

Incident with Copilot

Notice Resolved View vendor source →

GitHub experienced a notice incident on May 19, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 19, 2026, 05:30 AM UTC
Resolved
May 19, 2026, 05:30 AM UTC
Duration
Detected by Pingoru
May 19, 2026, 05:30 AM UTC

Update timeline

  1. resolved May 28, 2026, 12:40 PM UTC

    On May 19, 2026, between 05:30 UTC and 14:50 UTC, GitHub Copilot API requests supporting completions, chat sessions, and agent interactions experienced elevated error rates. At peak impact, approximately 13% of API requests failed, and approximately 24% of remote sessions failed to initialize. A partial mitigation at 08:16 UTC reduced the Copilot API error rate to approximately 0.3%, but intermittent failures persisted until a full fix was deployed at 14:15 UTC and recovery was verified by 14:50 UTC. The incident was caused by an internal rate limit being exceeded on a dependency shared by two Copilot backend services. A recently enabled feature increased call volume to this dependency, and both services were counted under the same rate limit scope. The combined volume exceeded the limit as traffic increased during business hours. We mitigated the incident by deploying a caching layer to reduce call volume. To prevent recurrence, we are separating rate limit scopes between services, fixing monitoring gaps for internal dependency rate limiting, and reducing redundant calls.