zumatools.

Popular right now

Add Prefix / Suffix to LinesPaste one item per line, then add text around each line, join them with a separator,…Tally CounterTap the big card to count up, use the minus button to correct mistakes, and add as…Love CalculatorEnter two names and get a playful compatibility score — the same pair of names always…Photo to Pencil SketchConvert any picture into a hand-drawn pencil sketch directly in your browser, with…Tic Tac ToePlay against a friend on the same device or challenge the computer on easy or…Random Pair GeneratorPaste names below and split them into random pairs or groups of three, shuffled fairly…
Free tools. Right here in your browser.esc to close

GitHub · Service status

Is GitHub Copilot down right now?

GitHub Copilot is GitHub’s AI coding assistant. It offers code completions, chat and agent features in VS Code, Visual Studio, JetBrains IDEs and other editors, and also works on github.com and in the terminal.

Live status · GitHub Copilot

Checking live status…

Reading the official status page, our reachability checks and recent user reports.

Official status page
—githubstatus.com
Our reachability check
—Checked every minute from our server
User reports
—From visitors to this page

Having trouble with GitHub Copilot?

Tell us what’s wrong. One report per person every 30 minutes; nothing else is collected.

GitHub Copilot in the last 24 hours

Loading the last 24 hours…

Reachability (our checks)No data
  • Reachable
  • Partly reachable
  • Not reachable
  • No data
Response timeNo data
User reportsNo data

If GitHub Copilot isn’t working for you

When the live checks above look normal, the problem is usually on your side or limited to one feature. These are the fixes that help most often with GitHub Copilot:

  1. Check the Copilot components on githubstatus.com

    GitHub lists Copilot and Copilot AI Model Providers as separate components on githubstatus.com. If either shows degraded performance or an outage, the problem is on GitHub’s side, even if Git, Issues and Pull Requests all show green.

  2. “GitHub Copilot could not connect to server. Extension activation failed”

    According to GitHub’s docs, this usually means the account has no active Copilot subscription or there’s a problem with the API token. Sign out of GitHub in your IDE and sign back in, confirm Copilot is enabled for your account, and check githubstatus.com for incidents.

  3. Re-authenticate in VS Code

    Click the Accounts icon and sign out of GitHub, run “Developer: Reload Window” from the Command Palette, then sign back in. In Visual Studio, make sure the GitHub account signed in there is the one with Copilot access.

  4. Proxy, firewall and certificate errors

    Errors such as “read ECONNRESET” or “unable to verify the first certificate” usually come from a corporate proxy or TLS-inspecting firewall. Your network must allow the domains in GitHub’s Copilot allowlist reference, such as *.githubcopilot.com and api.github.com, and custom certificates should be installed in the OS trust store.

  5. Status bar icon with a line through it

    If the Copilot icon in your IDE’s status bar has a diagonal line through it, Copilot is disabled for that file — often because an organization admin set a content exclusion. Exclusion changes can take up to 30 minutes to reach an IDE that’s already open.

  6. Rate limit or usage limit errors

    Copilot has rate limits, and plans come with a monthly usage allowance. If you hit one, requests fail with a limit error even though the service is up. Rate limits are temporary: wait and try again, and contact GitHub Support if it keeps happening.

Official GitHub Copilot sources

Questions about GitHub Copilot outages

GitHub is up. Why is Copilot not working?

Copilot has its own components on githubstatus.com, so it can be degraded while the rest of GitHub is fine. It can also fail locally because of an old extension, an expired sign-in or a network block. This page combines the official status page, our own reachability checks every minute and user reports.

Does a Copilot outage affect all IDEs?

A server-side Copilot incident affects every client: VS Code, Visual Studio, JetBrains, github.com and the CLI. If Copilot fails in only one editor, look at that editor’s extension version and sign-in first.

Why doesn’t Copilot suggest anything in some files?

Your organization or repository admin may have excluded those files; the status bar icon then shows a diagonal line. Exclusions can take up to 30 minutes to apply or clear in an IDE that is already open.

Where do I find Copilot logs?

Each IDE keeps Copilot logs — in VS Code they’re in the Output panel under the GitHub Copilot channels. GitHub’s docs explain how to view them in each environment, and these logs are what GitHub Support will ask for.

How this page decides

The answer at the top combines three signals: what GitHub reports on its official status page, our own check that GitHub Copilot is reachable (every minute, with response time), and reports from people on this page. Problems are flagged when the official source reports an incident, our checks start failing, or reports rise well above the usual level for GitHub Copilot. It’s an independent page — not affiliated with GitHub. See all AI services.

Check another AI service