Title: GitHub Copilot token fetch fails in VS Code due to timeout against api.github.com

[francobertinatti]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

VS Code

Body

Description:
GitHub Copilot fails to activate in Visual Studio Code after GitHub device authentication succeeds.

Environment:

OS: Windows
IDE: Visual Studio Code
Account type: Personal GitHub account
No corporate VPN
No WinHTTP proxy configured
No HTTP_PROXY / HTTPS_PROXY environment variables configured

Observed behavior:

GitHub device login succeeds in browser.
Browser shows: "Congratulations, you're all set! Your device is now connected."
VS Code still fails to activate GitHub Copilot.
GitHub Copilot logs show token fetch failure.
The error includes connection timeout against 4.228.31.149:443.

Network tests:

api.githubcopilot.com/_ping returns HTTP 200 OK.
copilot-proxy.githubusercontent.com/_ping returns HTTP 200 OK.
github.com:443 works.
api.github.com resolves to 4.228.31.149.
curl.exe -v https://api.github.com/rate_limit times out.
Test-NetConnection 4.228.31.149 -Port 443 fails.
Test-NetConnection 4.228.31.150 -Port 443 succeeds.
WinHTTP proxy is set to direct access.
Env:PROXY is empty.

Relevant error:
GitHub Copilot could not connect to server.
Extension activation failed.
Failed to get copilot token. reason: RequestFailed.
connect ETIMEDOUT 4.228.31.149:443.

Expected behavior:
After successful GitHub device authentication, VS Code should obtain the Copilot token and activate GitHub Copilot.

[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. ⭐

[pbalduino]

The API is unreachable for hours