github.com intermittently unreachable from Argentina: 140.82.114.4 (and at times 140.82.113.4) time out, other front-end IPs work #207965
Unanswered
gguille077
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 1 comment
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Other
Body
Summary
From Argentina, some github.com front-end IPs are unreachable (TCP connect timeout, 100% ping loss) while the rest of the pool works fine. Because DNS rotates the answer, github.com fails intermittently for users whose resolver returns a bad IP.
api.github.com,githubassets.comandgithubusercontent.comkeep working.A second user on a different Argentine ISP reports the same symptom, so this looks like a regional routing/peering problem rather than a single ISP.
Environment
Per-IP test (
curl --resolve github.com:443:<ip> https://github.com/)140.82.114.4 has been consistently unreachable for over 24 hours.
Traceroutes
Working IP (140.82.112.4), path via GTT (AS3257):
Failing IP (140.82.114.4), traffic never reaches GTT:
Intermittently failing IP (140.82.113.4, traced ~1 minute after the timeout above) reaches GTT and then goes dark:
Ask
Could the network team check reachability and route announcements for 140.82.114.0/24 (and 140.82.113.4) toward South America / via AS3257? Happy to run more tests (mtr, specific source ports, etc.) if useful.
All reactions