ANybody else having pull/clone troubles with github.com? It's been.... excrutiation slow, had to switch to Vanilla to get stuff pulled.
Code:My traceroute [v0.93] BumbleBee.local (10.1.1.9) 2020-03-23T22:32:45+0200 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 10.1.1.1 2.7% 1533 2.2 2.8 0.9 711.1 25.7 2. as-vuma.cp-gwf-4-01.za.ws.net.za 3.1% 1533 26.7 6.7 2.9 665.3 24.6 3. 160.119.233.130 2.8% 1533 3.6 7.5 2.9 613.5 25.9 4. core.as-01.cp1.za.ws.net.za 4.2% 1533 2.8 4.0 1.7 559.6 22.3 5. core.cr-01.cp1.za.ws.net.za 3.7% 1532 2.0 3.8 1.7 508.5 19.5 6. core.pe-xe-ip01.cp1.za.ws.net.za 3.1% 1532 2.2 4.8 1.8 1530. 43.0 7. 165-69-148-197.as37497.za.net 2.7% 1532 4.1 5.0 1.9 1481. 41.3 8. 162-68-148-197.as37497.za.net 2.5% 1532 35.2 6.6 2.0 1430. 53.1 9. 54-71-148-197.as37497.za.net 2.2% 1532 143.0 146.3 142.0 1531. 51.5 10. 213.130.47.125 3.3% 1532 143.5 148.0 142.8 1479. 51.2 11. ae-2.r25.londen12.uk.bb.gin.ntt.net 3.6% 1532 143.2 148.9 142.6 1431. 49.5 12. ae-1.r24.londen12.uk.bb.gin.ntt.net 2.6% 1532 144.6 148.6 142.7 1379. 47.7 13. ae-7.r20.nwrknj03.us.bb.gin.ntt.net 47.5% 1532 214.4 219.8 210.1 2532. 93.5 14. ae-0.r21.nwrknj03.us.bb.gin.ntt.net 66.6% 1532 211.0 214.2 210.2 366.6 10.9 15. ae-3.r22.asbnva02.us.bb.gin.ntt.net 24.7% 1532 217.4 219.9 215.0 1219. 33.8 16. ae-1.r05.asbnva02.us.bb.gin.ntt.net 4.6% 1532 216.8 219.2 214.9 1234. 39.1 17. ce-0-9-0-2.r05.asbnva02.us.ce.gin.nt 3.4% 1532 217.1 220.3 215.9 1186. 36.7 18. (waiting for reply) 19. (waiting for reply) 20. (waiting for reply) 21. lb-140-82-113-3-iad.github.com 4.3% 1532 219.0 223.1 218.9 980.3 31.0
Struggling with a git pull myself right now. Looking into this. Forward route seems good. Reverse route is identical if I test from NTT Ashurn (hop 17). No congestion along this route from what I can see. But picking up on losses on the last hop particularly. So could be an issue that end?
Actually looks like I'm pulling from the exact same server. Small world. This doesn't mean that Github's return route to us is the same. Not picking up any losses through to the edge of NTT's network (17). Whereas we see packet loss at hop 21.