Is GitHub Copilot down?

We are investigating reports of degraded availability for Copilot and Webhooks

We are investigating multiple unavailable services.

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

We have identified the root problem and are working on mitigation.

The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.

Many services are mitigated and are validating the remaining services.

Webhooks is operating normally.

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.

We are investigating reports of degraded performance for Actions

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

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

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

Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.

A mitigation was applied and services have recovered.  Actions is working through queued work before fully recovering.

The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.

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.

We are investigating reports of degraded performance for Copilot

We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation.

Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate.

The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.

The degradation has been mitigated. We are monitoring to ensure stability.

The success rate for creating and viewing agent sessions has stabilized, and we're continuing to monitor latency, which is trending toward baseline levels.

The degradation has been mitigated. We are monitoring to ensure stability.

The success rate and latency for creating and viewing agent sessions has stabilized at baseline levels, we are continuing to monitor recovery

On April 1, 2026, between 07:29 and 12:41 UTC, some customers experienced elevated 5xx errors and increased latency when using GitHub Copilot features that rely on `/agents/sessions` endpoints (including creating or viewing agent sessions). The issue was caused by resource exhaustion in one of the Copilot backend services handling these requests, in turn, causing timeouts and failed requests. We mitigated the incident by increasing the service’s available compute resources and tuning its runtime concurrency settings. Service health returned to normal and the incident was fully resolved by 12:41 UTC.

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

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

We are investigating reports that Copilot Coding Agent session logs are not available in the UI.

Copilot is operating normally.

On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its backing datastore. We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first. We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.

We are investigating reports of degraded performance for Copilot

We are experiencing degraded availability for the gpt-5.3-codex model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

The issues with our upstream model provider have been resolved, and gpt-5.3-codex is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete.

On March 5th, 2026, between approximately 00:26 and 00:44 UTC, the Copilot service experienced a degradation of the GPT 3.5 Codex model due to an issue with our upstream provider. Users encountered elevated error rates when using GPT 3.5 Codex, impacting approximately 30% of requests. No other models were impacted. The issue was resolved by a mitigation put in place by our provider.