Is GitHub Copilot down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, api.githubcopilot.com is responding normally to HostTracker's monitoring network, and has been up for 39d 23h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, api.githubcopilot.com is responding normally to HostTracker's monitoring network, and has been up for 39d 23h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, api.githubcopilot.com is responding normally to HostTracker's monitoring network, and has been up for 39d 23h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

It can be, even with github.com loading normally. Copilot's completion backend and GitHub's main website are different systems that share the same account layer but not the same infrastructure, so a problem in model serving can silence suggestions while everything else on GitHub works as expected. Checking api.githubcopilot.com directly, rather than judging by whether github.com loads, tells you whether the piece Copilot actually depends on is reachable.

This is more often a local authentication problem than an outage. Editor extensions cache a Copilot session token, and an IDE update, a permissions change, or a token that simply expired can leave the extension unable to authenticate even though the service is healthy. Signing out of the Copilot extension and back in resolves most of these. If suggestions fail for many people at the same time and this page also shows the API unreachable, that points at a real incident instead.

A corporate proxy or firewall blocking outbound calls to api.githubcopilot.com produces symptoms that look exactly like an outage from inside the editor - no suggestions, no clear error. The distinguishing test is whether the endpoint is reachable from outside your company network: if an independent check shows it up while your editor still fails, the block is local to your network configuration, and it's worth raising with whoever manages the proxy rather than waiting on GitHub.

Yes, and it's one of the more common false alarms. Copilot plans cap the number of completions or premium requests available in a period, and once that cap is reached, suggestions stop in a way that isn't always clearly labeled inside the editor - it can read as the extension simply not working. Checking your plan's usage against its limit before assuming a service failure saves a lot of confusion, since the underlying service is often working normally the whole time.