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

We’ve been seeing very similar behavior recently as well, especially on SSH fetches involving larger packfiles.

A few observations from our side that may help narrow it down:

• Initial SSH negotiation/auth is fast and healthy (ssh -T git@github.com completes instantly).
• The slowdown starts specifically during packfile transfer (Receiving objects), matching your description.
• HTTPS clones from the same machines/networks are significantly faster and more stable.
• Reproduced across multiple regions/providers, so it doesn’t seem isolated to a single ISP or local routing issue.

Some temporary mitigations that improved things slightly for us:

• Using HTTPS instead of SSH for heavy CI fetches/clones
• Reducing fetch depth (--depth=1)
• Disabling compression in some environments:
  git config --global core.compression 0
• Testing over ssh.github.com:443 helped stability for a few hosts, but not throughput

This definitely feels more like an issue in the SSH git-transfer path/CDN routing layer than a client-side Git problem, especially given the consistency across providers and regions.

Hope GitHub engineering takes a closer look, because multiple users seem to be hitting the same pattern lately.