GitHub Status

We're seeing delays in Dependabot scheduled version update runs. Our team is actively working on a fix and will share updates as the situation develops.

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

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

We are investigating reports of delayed code scanning runs and delayed billing updates.  We will continue to keep users updated on progress towards mitigation.

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

On May 28, 2026, between 19:07 UTC and 19:16 UTC, multiple GitHub services experienced elevated error rates. This was due to a change that was partially deployed to an authentication service, causing errors for dependent services including the web experience, REST API, Git operations, and GitHub Actions. At peak impact, 10% of GitHub Actions runs failed to queue or encountered errors while downloading actions. We mitigated the incident by rolling back the change. We are expanding test coverage and improving our deployment validation process to prevent recurrence of this issue in the future.

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

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.

We are investigating reports of degraded performance for Webhooks

We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests

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

We are investigating reports of degraded performance for Actions and Pages

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.

This is fully mitigated, we will continue to monitor to ensure it does not reoccur.

We have identified and are applying additional mitigation and will continue to monitor for complete mitigation.

We see significant signs of mitigation and are monitoring for full mitigation.

We are seeing signs of mitigation and are continuing to monitor for complete mitigation.  <br /><br />Next update in one hour.

We are continuing to investigate an elevated error rate of authentication failures for app installation tokens.  Next update in one hour.

We are seeing an increased rate of authentication failures for app installation tokens, affecting approximately 1% of tokens.  We are continuing to investigate.

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

We are investigating reports of degraded performance for Actions