Is GitHub Copilot down?

Check that you are still signed in and running the latest version: coding tools ship updates every week, and old builds lose touch with the backend. Then restart the editor or the terminal session. If this page shows a problem, switch to another model if the tool allows it, or carry on without the assistant for a while — nothing on your computer needs fixing.

Company proxies, firewalls and VPNs are the usual suspects: these tools hold long-lived connections that some networks cut. Plans also differ in limits and in which models they include. Compare the version, the way you are signed in and the network, in that order.

Often it is the model provider behind the tool being overloaded, which is exactly what this page watches. Huge files and repositories slow things down as well. If the status is green, try a small file or a fresh chat to see whether the size of the context is the cause.

No. During an outage the assistant can only fail to answer or stop midway; it doesn't change files by itself. If an agent was interrupted in the middle of an edit, look through the diff before you continue — with version control that takes a minute.

For GitHub Copilot we combine GitHub's official status page, read every minute and reports from people who press the button on this page. The most serious signal that is still fresh sets the verdict, and stale sources are ignored rather than trusted. The page refreshes by itself; the exact thresholds are on our “How we check” page.