copilot with intermittent access

[CaioLucioRodrigues]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

VS Code

Body

GitHub Copilot appears to be down for our whole team.

We are located in Brazil and all developers are getting timeout errors when connecting to api.github.com / Copilot services.

Example from VS Code Copilot logs:

• connect ETIMEDOUT 4.228.31.149:443
• electron-fetch timed out
• node-fetch failed
• DNS resolves api.github.com to 4.228.31.149
• No proxy configured

PowerShell test:

Test-NetConnection api.github.com -Port 443
TcpTestSucceeded: False

This started intermittently yesterday and is happening again today for multiple users in the same team/network.

Is anyone else experiencing this?

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

[ronisbr]

Me too! I cannot login in copilot-cli, it returns the error:

Error during sign-in: TypeError: fetch failed

Also, if I try to update copilot using copilot update, I get:

❯ copilot update
Checking for updates...
Checking GitHub for the latest release...
Error during update: Failed to fetch latest release: HttpError: Connect Timeout Error (attempted address: api.github.com:443, timeout: 10000ms)

I cannot use copilot inline suggestion in VSCode or Neovim.

[CaioLucioRodrigues]

I needed to use Cloudflare VPN. Now I have access to the Copilot API again. Strange.

[debashish-5]

1. The 2-Second Web UI Trick: Delete the Branch

If the stuck run is on a feature branch, delete the branch from the GitHub UI.

• Why it works: GitHub's backend automatically and instantly terminates all active or queued workflows associated with a deleted branch.
• The fix: Delete it, let the zombie run die, and click Restore branch immediately.

2. The 5-Second Terminal Command

If you already have the GitHub CLI (gh) authenticated on your machine, don't mess around with complex curl headers. Run this single command:

gh run cancel <RUN_ID>

(Grab the <RUN_ID> straight from the URL of the stuck page).

3. The 10-Second File Rename (For main/master branches)

If the run is stuck on a protected branch that you cannot delete, push a lightning-fast commit that renames the workflow YAML file (e.g., change build.yml to build-temp.yml).

• Why it works: Changing the file path breaks the backend listener tracking that specific queue, forcing GitHub to drop the zombie run. You can rename it back to normal on your next commit.