Knowledge base · TOPIC-09

How to triage GitHub Copilot network failures

Short answer: a Copilot connection error can originate in the editor, extension, proxy, certificate trust, network path, provider service, or account state. One timeout cannot identify which layer failed.

GitHub’s official troubleshooting guide documents proxy and custom-certificate failures, including ETIMEDOUT, ECONNRESET, and certificate verification errors. Treat that guidance as provider-reported context. Your timestamped DNS, TCP, TLS, and HTTP results are observations; a root-cause statement remains an inference.

Start with the exact client error and time. Check GitHub Status separately. If corporate TLS inspection is present, involve the administrator rather than disabling certificate validation. A controlled alternate network can narrow the path, but it does not prove an entitlement or extension defect. Remove repository names, credentials, cookies, tokens, and private addresses before sharing diagnostics.

Tivor Open Probe V0.1 does not execute a Copilot provider path and cannot test authentication or extension state; Copilot is reported as UNSUPPORTED / NOT_EXECUTED. The Scanner can show limited browser evidence, while Open Probe provides local, read-only context. Related: provider outage or local failure.