GitHub Copilot Down? Live Status & Outage Checker
Check whether GitHub Copilot is currently down, failing to suggest code, or unable to connect. This page tracks GitHub’s Copilot component specifically, not GitHub as a whole.
The latest status signal does not show a major service disruption for this tool.
Is GitHub Copilot Down Right Now?
The card above reads the Copilot component on GitHub’s official status page. That distinction matters more here than on any other page we track: GitHub publishes a single overall indicator covering Actions, Pull Requests, Pages, Codespaces and much else, and that indicator goes red for problems that have nothing to do with Copilot.
Reading the overall GitHub indicator would tell you Copilot is down during an Actions outage, and tell you it is fine during a Copilot-only incident. Both answers would be wrong. This page deliberately follows the Copilot component on its own so the signal matches the question you are asking.
Copilot and Copilot AI Model Providers Are Different Things
GitHub reports on two related components. Copilot covers GitHub’s own service — authentication, routing your request, returning the completion. Copilot AI Model Providers covers the upstream model vendors whose models actually generate the code.
An incident on the model-provider component is the classic case of suggestions failing while GitHub’s Copilot service is technically healthy. If the live card shows an incident, read what it names. If it shows operational and suggestions still will not appear, the checklist below separates an editor or network problem from a service one.
What Causes GitHub Copilot Downtime?
Genuine Copilot outages usually trace to one of three things: an incident in GitHub’s Copilot service itself, a problem at the upstream model providers, or a wider GitHub authentication failure that stops the extension proving who you are. The last one is worth noting because it presents as Copilot being broken when the actual fault is GitHub sign-in.
Far more day-to-day interruptions are not outages at all. Expired or stale authentication tokens are the most common, and they produce connection errors that look exactly like a service failure. Organisation policy is the next most common: an administrator can disable Copilot, restrict it to certain repositories, or block suggestions matching public code, and each of those quietly stops suggestions for reasons no status page will ever show. Extension version mismatches and corporate firewalls account for most of the rest.
⚠️ Common GitHub Copilot Problems Users Report
No Suggestions Appearing
The most reported symptom, and most often a stale token or a policy restriction rather than an outage.
Sign-In Loop or Auth Errors
The extension cannot prove your identity. Signing out of GitHub in the editor and back in usually clears it.
Copilot Chat Fails While Completions Work
Chat and inline completions take different paths, so one can fail while the other is fine.
Blocked by Organisation Policy
Admins can disable Copilot, limit it to some repositories, or block matches to public code. No status page reports this.
Extension Out of Date
An old extension against a changed API produces connection errors that resemble a service outage.
Premium Request Limits Reached
Paid plans meter premium model requests. Hitting the ceiling stops responses in a way that reads like a fault.
✅ What to Check First
- 1Read the live card above. It tracks the Copilot component specifically, so an incident there is genuinely Copilot.
- 2Ignore GitHub’s overall status banner for this purpose — it goes red for Actions and Pages problems that do not affect Copilot.
- 3Sign out of GitHub inside your editor and sign back in. A stale token is the single most common cause.
- 4Update the Copilot extension, then reload the editor window.
- 5Check whether your organisation has restricted Copilot, especially if it stopped in one repository but works in another.
- 6Try Copilot Chat and inline completions separately — if only one fails, it is not a full outage.
- 7Test off the corporate network. Firewalls and proxies block the endpoints Copilot needs.
- 8Check whether you have hit your plan’s premium request allowance.
🌐 Down for Everyone or Just Me?
🔴 Signs it’s a platform-wide issue
- The live card above reports an incident on the Copilot component
- Suggestions fail across several editors and machines
- Colleagues in your organisation report the same thing at the same time
- Both Chat and inline completions stop together
🟡 Signs it’s a local or account issue
- Only one editor or one machine is affected
- It fails in one repository but works in another, which points to policy
- Signing out and back in restores it
- The error names a limit, quota or premium request allowance
How Reliable Is GitHub Copilot?
The uptime figure on the card is GitHub’s own published 90-day number for the Copilot component. It usually sits well above 99%, and it is noticeably better than the figure you would get from GitHub’s platform as a whole, because the wider platform absorbs incidents in Actions and other services that never touch Copilot.
That gap is the reason this page exists in the form it does. A status page that reported GitHub-wide numbers would consistently understate Copilot’s availability and would raise alarms on days when Copilot itself ran perfectly.
When Will GitHub Copilot Be Back?
Copilot incidents tend to be short, and GitHub posts updates on its status page as they progress. Problems traced to the model providers last as long as the provider incident does. Authentication problems that affect GitHub sign-in more broadly usually clear alongside the wider fix.
If the live card reports everything operational, waiting will not help, because nothing is being fixed. Work through the checklist above instead — in practice a stale token or an organisation policy explains most cases where Copilot stops for one person while the service is healthy.
❓ GitHub Copilot Down — Frequently Asked Questions
Not necessarily, and usually not. GitHub’s overall indicator covers Actions, Pull Requests, Pages, Codespaces and more, so it turns red for incidents that leave Copilot completely unaffected. The card on this page follows the Copilot component on its own, which is why it can show operational while GitHub’s headline banner shows a problem.
The usual causes are a stale authentication token, an out-of-date extension, or an organisation policy restricting Copilot. Sign out of GitHub in your editor and back in first, since that fixes the largest share of cases. If it works in one repository but not another, the cause is almost certainly policy.
Chat and inline completions follow different paths through the service and can fail independently. It is a normal pattern during partial incidents, and it is also why "Copilot is down" is worth narrowing to which part stopped.
It covers the upstream model vendors that generate the completions, as distinct from GitHub’s own Copilot service. When that component has an incident, suggestions can fail even though GitHub’s Copilot infrastructure is healthy.
Yes. Organisation administrators control whether Copilot is enabled, which repositories it covers, and whether suggestions matching public code are blocked. None of that appears on any status page, so a sudden stop confined to work repositories is worth raising with whoever administers your organisation.
🔗 Related AI Status Checks