VS Code / GitHub Authentication falha com “network error” ao acessar api.github.com

[AlexandreMuskus]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

On May 15, 2026, I was unable to sign in to GitHub from Visual Studio Code / GitHub Authentication. The sign-in flow starts, but the authentication fails with a network error.

Symptoms
github.com opens normally in the browser.
vscode.dev opens normally in the browser.
api.github.com does not open in the browser and returns a timeout.
Visual Studio Code shows:
Sign in failed: Error: network error
Error while turning on Settings Sync: network error
VS Code / GitHub Authentication log evidence
The VS Code log indicates that the OAuth/token exchange succeeds, but the next HTTPS request fails:

Token exchange success!
Getting user info...
FetcherService: Node fetch failed with error: fetch failed
Node http/s failed with error: connect ETIMEDOUT 4.228.31.149:443
Error: network error
Local diagnostics already performed
PowerShell tests from the affected machine show:

nslookup api.github.com resolves to 4.228.31.149
Test-NetConnection api.github.com -Port 443 fails
Browser access to api.github.com times out
Browser access to github.com works normally
This suggests DNS resolution is working, but the HTTPS connection to api.github.com:443 is timing out from this environment.

Impact
Unable to sign in to GitHub in VS Code
Unable to use GitHub Authentication-dependent features
Settings Sync also fails due to the same network error
Request
Please help confirm whether there is any platform-side issue affecting access to api.github.com, or whether you can identify any GitHub-side condition that would explain successful token exchange followed by timeout when requesting user info.

I can provide additional logs, screenshots, and timestamps if needed.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[zhiru]

Same here!

[leoplantmanager]

Urgent ! The same problem here...2 hours ago...and offline yet

[leoplantmanager]

no issues on githubstatus ? :-|

[zhiru]

sem issues lá como se nada tivesse acontecido

[zhiru]

vi um pessoal a uma hora atras relatando o mesmo e falando que estao conseguindo acessar por vpn mas aqui direto no BR nao está acessando a api mesmo

[edneic]

Também. Estou com o mesmo problema aqui e em outra rede e computador fisico

[Spinelli666]

Same here!

[itzvini]

Same here

[YagoROliveira]

same here!

[leoplantmanager]

nobody from github ? no support ? nothing ? No status ? really bad...

[zhiru]

back online here :)

[edneic]

Segue o comando para quem quiser fazer o teste também no (para windows) Powershell:

Test-NetConnection api.github.com -Port 443

[leoplantmanager]

back !

[ozikcode]

Mesmo problema aqui. Ja está assim desde ontem.

[jpedrosouza]

Através dos logs (e os comandos de pings enviados nesta discussão) é possível ver que o não esta sendo possível acessar o IP 4.228.31.149

Se realizarmos uma simples busca na internet sobre este IP, é possível ver que ele esta em Campinas SP.

Aparentemente este erro só esta acontecendo para nós brasileiros, por isso que na página de Status não aparece nada. Vi em algum post aleatório por ai que bastaria alterar este IP (4.228.31.149) para um outro nas configurações de host do windows (ou do seu OS) para que o VS Code passasse a "chamar" ele em vez do IP que esta com erro. É por isso que alguns estão relatando que com VPN o sistema volta a funcionar.