GitHub · GitHub's AI coding assistant
Is GitHub Copilot down right now?
✓Operational GitHub Copilot looks up. We are not seeing any problems right now.
Last checked at 10:45 UTC. Same verdict since 7 Oct 16:34 UTC.
Our own check
We have no independent check for GitHub Copilot, so this page follows the official feed.
We send an unauthenticated request to the service every five minutes. A sign-in or bot-protection reply still proves it is answering.
Last 24 hours
Last 30 days
Building history. Green is fully operational, amber is having issues, red is down, grey is no data.
Recent incidents
No incidents have been reported on GitHub’s status page since we started watching.
Changes we have observed
We have not seen GitHub Copilot change status since we started watching.
How GitHub Copilot can fail
GitHub's status page covers the whole of GitHub: Git operations, webhooks, the API, issues, pull requests, Actions, packages, Pages, Codespaces, Copilot and a separate component for Copilot's AI model providers. We count only the Copilot component for this page, so an Actions outage does not mark Copilot as having issues. We run no check of our own for this one, so this page follows the official feed.
Page-wide incidents from GitHub are shown for information but do not change the verdict.
- Copilot: The component we count in the verdict.
- Other GitHub components: Actions, Pages, Codespaces and others are not counted.
Network problems that look like outages
Most Copilot problems that are not outages come from the network. GitHub's own documentation on network errors describes these.
- read ETIMEDOUT or read ECONNRESET: Connectivity failures, often caused by a corporate proxy blocking Copilot.
- certificate signature failure, unable to verify the first certificate: A proxy that inspects encrypted traffic, using a certificate your machine does not recognise.
- Proxy settings: GitHub says Copilot does not support proxies whose address begins with https://, and needs basic or Kerberos authentication where one is required.
- VPNs and firewalls: These can stop Copilot reaching GitHub. GitHub publishes an allowlist for firewalls and suggests testing the connection with curl.
Written from the sources below on 8 October 2026. Providers change their documentation, so check it for anything important.
Sources
If GitHub Copilot is not working for you
Check the two signals above first. When both look healthy, try a different device or network, sign out and back in, and switch off any VPN or browser extensions. Hitting a usage limit can look like an outage, so check for a message about limits. Our guide has the full checklist, and another explains why a service can be up but broken for you.
Questions about GitHub Copilot status
Is GitHub Copilot down right now?
GitHub Copilot looks up. We are not seeing any problems right now.
How can I tell if GitHub Copilot is down for everyone or only for me?
Compare what you see with the two signals above. If GitHub's status page and our checks both look healthy, the problem is likely your account, network, browser or a usage limit. Try another device or connection, sign out and back in, and turn off any VPN or browser extensions.
Where is the official GitHub Copilot status page?
GitHub publishes status information at https://www.githubstatus.com.
How often is this page updated?
Our checks run every five minutes, so this page can lag a sudden outage by up to five minutes.
Why does a GitHub Actions outage not show here?
GitHub's status page covers many products. We count only its Copilot component, so an outage elsewhere on GitHub does not turn this page amber.
Copilot fails at work but not at home. Why?
Corporate proxies, custom certificates, VPNs and firewalls are the usual causes, according to GitHub's documentation on Copilot network errors. Your IT team can check the proxy and firewall settings.
Other AI services
ChatGPTClaudeGeminiPerplexityMicrosoft CopilotGrokDeepSeekMistral Le ChatCursor