Routing issue around ae1.cr6.rcmdca11.sonic.net & ae0.cr4.colaca01.sonic.net?

General discussions and other topics.
5 posts Page 1 of 1
by psychslimechat » Fri Jan 24, 2025 12:13 am
In the past 2-3 days, I have been suffering from a packet loss issue in the routes for 119.252.32.1 and www.yahoo.co.jp through Sonic.

Seems like there are some routing issues around ae1.cr6.rcmdca11.sonic.net and ae0.cr4.colaca01.sonic.net.

I'm living in San Mateo area in CA.

================

$ ping 119.252.32.1
PING 119.252.32.1 (119.252.32.1): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 119.252.32.1: icmp_seq=1 ttl=240 time=155.653 ms
64 bytes from 119.252.32.1: icmp_seq=2 ttl=240 time=155.342 ms
64 bytes from 119.252.32.1: icmp_seq=3 ttl=240 time=155.187 ms
64 bytes from 119.252.32.1: icmp_seq=4 ttl=240 time=155.076 ms
64 bytes from 119.252.32.1: icmp_seq=5 ttl=240 time=155.231 ms
64 bytes from 119.252.32.1: icmp_seq=6 ttl=240 time=155.184 ms
Request timeout for icmp_seq 7
64 bytes from 119.252.32.1: icmp_seq=8 ttl=240 time=155.238 ms
64 bytes from 119.252.32.1: icmp_seq=9 ttl=240 time=155.350 ms
Request timeout for icmp_seq 10
64 bytes from 119.252.32.1: icmp_seq=11 ttl=240 time=155.364 ms
64 bytes from 119.252.32.1: icmp_seq=12 ttl=240 time=155.315 ms
64 bytes from 119.252.32.1: icmp_seq=13 ttl=240 time=155.291 ms
64 bytes from 119.252.32.1: icmp_seq=14 ttl=240 time=155.226 ms
64 bytes from 119.252.32.1: icmp_seq=15 ttl=240 time=155.219 ms
Request timeout for icmp_seq 16

$ traceroute 119.252.32.1
traceroute to 119.252.32.1 (119.252.32.1), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.363 ms 0.778 ms 0.756 ms
2 lo0.bras1.brlnca01.sonic.net (157.131.132.72) 1.988 ms 2.223 ms 2.009 ms
3 157-131-210-82.static.sonic.net (157.131.210.82) 6.274 ms 8.906 ms 8.379 ms
4 ae5.cr2.colaca01.sonic.net (157.131.210.17) 18.798 ms 21.006 ms
ae2.cr2.lsatca11.sonic.net (157.131.210.21) 22.743 ms
5 ae2.cr1.lsatca11.sonic.net (157.131.209.161) 2.497 ms * *
6 ae0.cr4.colaca01.sonic.net (157.131.243.25) 286.623 ms 214.892 ms *
7 * * *
8 * * *
9 ae1.cr6.rcmdca11.sonic.net (23.93.54.154) 4373.935 ms * *

================

$ ping www.yahoo.co.jp
PING edge12.g.yimg.jp (182.22.16.123): 56 data bytes
64 bytes from 182.22.16.123: icmp_seq=0 ttl=45 time=155.303 ms
64 bytes from 182.22.16.123: icmp_seq=1 ttl=45 time=155.098 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 182.22.16.123: icmp_seq=4 ttl=45 time=155.508 ms
64 bytes from 182.22.16.123: icmp_seq=5 ttl=45 time=155.390 ms
64 bytes from 182.22.16.123: icmp_seq=6 ttl=45 time=155.353 ms
64 bytes from 182.22.16.123: icmp_seq=7 ttl=45 time=155.230 ms
Request timeout for icmp_seq 8
64 bytes from 182.22.16.123: icmp_seq=9 ttl=45 time=155.380 ms
64 bytes from 182.22.16.123: icmp_seq=10 ttl=45 time=155.226 ms
64 bytes from 182.22.16.123: icmp_seq=11 ttl=45 time=155.321 ms
64 bytes from 182.22.16.123: icmp_seq=12 ttl=45 time=155.386 ms
Request timeout for icmp_seq 13
64 bytes from 182.22.16.123: icmp_seq=14 ttl=45 time=155.675 ms
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16

$ traceroute www.yahoo.co.jp
traceroute to edge12.g.yimg.jp (183.79.249.124), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 3.067 ms 0.831 ms 0.731 ms
2 lo0.bras1.brlnca01.sonic.net (157.131.132.72) 2.008 ms 1.966 ms 1.905 ms
3 157-131-210-90.static.sonic.net (157.131.210.90) 10.154 ms 7.429 ms
157-131-210-82.static.sonic.net (157.131.210.82) 6.386 ms
4 ae2.cr2.lsatca11.sonic.net (157.131.210.21) 452.878 ms
ae5.cr2.colaca01.sonic.net (157.131.210.17) 16.459 ms 15.970 ms
5 * * *
6 * ae0.cr4.colaca01.sonic.net (157.131.243.25) 3766.401 ms 1981.135 ms
by jerrielm » Fri Jan 24, 2025 7:54 am
Hello!

Thank you for reaching out! I am sorry to hear about your issues with connecting to JP Yahoo. When you are having packet loss, what issues with loading the page do you have? Do images or videos not load? Packet loss on traceroutes might not indicate a problem and could just be a long wait time for ping to respond to the request. (This helps not to flood other services with request like this)

I look forward to resolving your issues!

Best Wishes!
by psychslimechat » Fri Jan 24, 2025 12:46 pm
Hi!

The issue I'm actually seeing is action loss issue or more than 10s long delays in a realtime online game called Dragon Quest X Online. The packet loss means the game is non-playable. I think one of their server IPs is 119.252.32.1. This packet loss issue started happening in 3-4 days ago. Before that it worked as expected.

We experienced the same issue in October 2020 and reported it here. It also happened around the same hosts within Sonic network.

viewtopic.php?t=18040

In both cases, we didn't send too many packets to the route to servers in Japan.
by spencernash » Fri Jan 24, 2025 7:13 pm
Sonic always has some hops in a traceroute that don't answer pings/traceroutes and show as *'s. If you traceroute to Google or FB you'll see similar hops with no reply, even though you can connect just fine.

I just tested with my work connection to both the IP you listed and Yahoo Japan and saw the similar packet loss and timeouts, using the same route under the ocean. Pings to the first hop in Japan after the transpacific cable, 206.223.116.43, has high loss, so the fiber under the ocean might just be congested. Or not... Pings are low priority and the first thing to be ignored by most routers.

Either way, doesn't look like an issue anywhere in the Sonic network.
by psychslimechat » Fri Jan 24, 2025 10:29 pm
Thanks for your investigation! I think you are right. Seems like 206.223.116.43 has some problems. Seems like the router is managed by KDDI or Equinix and located in San Jose IX. So that's outside of Sonic network. Sorry for the confusion!
5 posts Page 1 of 1

Who is online

In total there is 1 user online :: 0 registered, 0 hidden and 1 guest (based on users active over the past 5 minutes)
Most users ever online was 3912 on Mon Feb 10, 2025 6:15 pm

Users browsing this forum: No registered users and 1 guest