Connection timed out to Copilot authentication on VS Code

[niloct]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

VS Code

Body

Is anyone also getting this timeout today on VS Code?

2026-06-11 09:54:38.824 [info] FetcherService: Electron fetch failed with
error:
net::ERR_CONNECTION_TIMED_OUT
2026-06-11 09:54:49.512 [info] FetcherService: Node fetch failed with
error:
fetch failed
2026-06-11 09:55:10.607 [info] FetcherService: Node http/s failed with
error:
connect ETIMEDOUT 4.228.31.149:443
2026-06-11 09:55:10.607
[error]
net::ERR_CONNECTION_TIMED_OUT

https://www.reddit.com/r/GithubCopilot/comments/1u2yesa/comment/or1j6cu/?screen_view_count=1 lists a workaround, connecting to a USA VPN. This works here in Brazil.

Also, it seems there are some routes in Brazil which can connect to 4.228.31.149:443.

Is the Copilot infra team aware of this?

Thanks for the attention,
Nilo

[Gecko51]

Yeah, this is a routing issue with Azure IP ranges on some Brazilian ISPs. The IP 4.228.31.149 is in Azure's infrastructure, and the path to it from certain carriers in Brazil has been flaky on and off.

The VPN workaround is the right short-term fix. Some people also get it working by switching to a different network (e.g. mobile hotspot), which bypasses the problematic routing path.

As for the infra team, community discussions don't go directly to GitHub engineering. Your best shot at getting this on their radar is filing a support request at https://support.github.com, including the logs you already have plus your ISP name. That kind of specific IP + geo combo is useful for tracing where the routing breaks.

[Darlan82]

I'm having the same error.
It's impossible to authenticate.

microsoft/vscode#321058

[anderbytes]

Add` this temporarily to your local hosts file (Linux).

## Github Temp Fix
4.228.31.150 github.com
140.82.113.6 api.github.com
# 140.82.112.6 api.github.com
# 140.82.114.6 api.github.com
# 140.82.121.6 api.github.com

[Snehajit999]

Yes, IP 4.228.31.149 several users appear to be experiencing connection timeouts with Copilot in VS Code. Based on your logs, the requests are timing out before reaching the Copilot service endpoint.

Since connecting through a US VPN works, the issue may be related to regional network routing, ISP peering, or connectivity between certain regions and GitHub's infrastructure rather than VS Code itself.

If multiple users from Brazil are seeing the same behavior, it would be helpful for the Copilot team to investigate whether there are routing issues affecting access to the affected endpoint. In the meantime, using a VPN may serve as a temporary workaround.

Thanks for providing the logs and workaround details.