Is GitHub Copilot down?
How to check GitHub Copilot's status properly
Copilot has its own component on githubstatus.com — filter for it, because a green GitHub homepage says nothing about Copilot.
Copilot incidents can be feature-scoped: completions, chat, or the coding agent can fail independently.
GitHub tracks "Copilot AI Model Providers" as a second, separate component. That is the one that carries most Copilot incidents, and it is the row to read when completions start erroring.
What GitHub Copilot's incident history actually looks like
Copilot is the calmest tool on this board. Thirteen incidents in the 58 days to 13 August 2026, about one and a half a week, with a median resolution of 65 minutes and nothing in the window running past two hours and 35 minutes.
Whose fault they were is the interesting part. Nine of the 13 hit the component GitHub calls Copilot AI Model Providers rather than Copilot itself: "Errors with the Fable 5 Model in Copilot", "Several GPT models degraded", "Disruption with GPT 5.3 Codex". GitHub's own Copilot component was named in four.
So the useful reflex when Copilot dies is not to load github.com. It is to look at which model you are on and change it, because the model vendors are what usually broke.
13 incidents, 16 June – 13 August 2026. Counted from githubstatus.com/api/v2/incidents.json (Copilot components), pulled . The live board at the
top of this page is current; these numbers are a snapshot and will drift.
Is GitHub Copilot down, or is it just you?
- GitHub being green tells you nothing at all. Copilot and its model providers are separate components on that same page, and either can be red while Git operations, Actions and pull requests are fine.
- Completions dead while chat still answers is a documented incident shape here, not a corrupt install. Read which surface the incident names before you reinstall anything.
- An expired extension token imitates an outage perfectly. Sign out of the Copilot extension and back in before you conclude GitHub broke.
- A hard stop can be billing rather than availability. One incident in this window was "Delays in copilot budget limits resets for some users" — if you are suddenly cut off, check your budget before your network.
What to do while GitHub Copilot is down
- Completions dead but chat alive (or vice versa) is a known incident pattern — check the incident text for which surface is affected.
- IDE-side auth expiry mimics an outage: sign out and back into the Copilot extension before blaming GitHub.
- During longer Copilot outages, a local-completion fallback or a CLI agent keeps the flow going.
Frequently asked questions
How do I check if GitHub Copilot is down?
The live board above reads githubstatus.com's official API and filters to both Copilot components — "Copilot" and "Copilot AI Model Providers" — so you see Copilot's state specifically rather than GitHub's overall banner. The 30-day counts below the verdict are scoped the same way.
Is it GitHub that broke, or the AI model behind Copilot?
Usually the model. Of the 13 Copilot incidents in the 58 days to 13 August 2026, nine hit the component GitHub calls Copilot AI Model Providers rather than Copilot itself — titles like "Several GPT models degraded" and "Errors with the Fable 5 Model in Copilot". Changing model is a better first move than waiting for GitHub.
Can GitHub be up while Copilot is down?
Yes. Copilot is tracked as its own component on GitHub's status page, and Copilot-only incidents happen. That's why checking the component beats checking github.com.