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.
Is it down, or is it just you?
A 401 or 403 error is almost always your own auth — an expired token or a session that needs re-login, not an outage. A run of 5xx errors, or a 529 "overloaded" response, during an incident that's actually listed on the vendor's status page is on them, not you.
Before you conclude it's a real outage: try a second surface (the web app instead of the CLI, or vice versa), rule out your own network or VPN, and only then treat the vendor's official status page as the final word.
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 the Copilot component, so you see Copilot's state specifically — not just GitHub's overall banner.
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.