1 Message
Massive packet loss to website in Singapore starting around April 2, 2024
Since around April 2, 2024, my Internet access to a site in Singapore, www.dasko.org, has experienced massive packet loss.
The problem started when traffic stopped being routed (I think) through Colorado Springs or somewhere, through some sites that seem to be in China and Hong Kong. See my traceroute report below:
My traceroute [v0.95]
hvblue (192.168.1.219) -> www.dasko.org (165.22.111.1282024-04-09T10:08:54-0400
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. dsldevice.attlocal.net 0.0% 393 1.8 1.8 1.0 12.7 0.7
2. 108-201-8-1.lightspeed.clmboh.sb 0.0% 393 3.4 5.9 1.8 115.3 9.9
3. 71.151.141.140 0.0% 393 4.2 5.8 2.7 88.2 7.2
4. (waiting for reply)
5. 32.130.17.77 0.0% 392 19.7 19.6 13.1 135.6 8.9
6. cgcil402igs.ip.att.net 0.0% 392 21.6 20.5 13.2 118.7 10.6
7. chi-b23-link.ip.twelve99.net 96.4% 392 15.4 18.2 14.0 37.9 6.8
8. chi-bb2-link.ip.twelve99.net 12.2% 392 16.2 17.4 13.9 93.0 5.1
9. kanc-b2-link.ip.twelve99.net 0.0% 392 41.0 40.1 36.6 154.5 9.1
10. sjo-b23-link.ip.twelve99.net 0.0% 392 63.2 63.5 59.4 256.8 15.8
11. tky-b2-link.ip.twelve99.net 0.0% 392 177.4 175.8 171.0 333.0 10.3
12. osa-b1-link.ip.twelve99.net 0.0% 392 250.9 245.0 240.9 332.0 8.3
13. hnk-b4-link.ip.twelve99.net 10.2% 392 221.0 334.5 219.5 589.0 142.2
14. hnk-b1-link.ip.twelve99.net 0.0% 392 245.8 247.6 243.9 435.7 11.8
15. snge-b4-link.ip.twelve99.net 37.1% 392 592.9 566.4 450.4 737.4 18.9
16. snge-b7-link.ip.twelve99.net 98.2% 392 258.4 246.3 242.9 258.4 5.4
17. snge-b5-link.ip.twelve99.net 96.7% 392 589.8 592.5 575.0 641.1 16.2
18. digitalocean-ic-378004.ip.twelve 7.7% 392 279.3 261.9 254.0 335.1 5.7
19. (waiting for reply)
20. (waiting for reply)
21. (waiting for reply)
22. (waiting for reply)
23. (waiting for reply)
24. (waiting for reply)
25. www.dasko.org 0.0% 392 272.9 268.7 264.2 403.5 11.2
Accepted Solution
JefferMC
ACE - Expert
•
36K Messages
3 months ago
Your traceroute is not showing any actual packet loss to the ultimate destination (hop 25, www . dasko . org). The "packet loss" in the intervening hops is not significant. Backbone routers are often configured to rate limit error responses (such as the TTL expired errors used by traceroute). While packet loss that starts at one of them and continues through to the end is significant; spot "loss" like you're seeing is not.
The increased latency is probably somewhat traffic related, but you're using multiple undersea cables, if not satellite links, so some increased latency is not too surprising.
0
JefferMC
ACE - Expert
•
36K Messages
3 months ago
Judging solely by the host names, your traffic is getting routed from Columbus to
(edited)
0