About a week ago I noticed a significant increase in IPv6 round trip time between my sonic router and a VPS (virtual private server) I rent in Fremont, CA - it went from ~6ms to ~60ms.
Traceroute from the VPS shows that traffic inbound to Sonic is taking a detour via Chicago and Seattle on its way from Fremont to Santa Clara.
The clearest traceroute-type output I get is from the "mtr" command:
Note that mythic-beasts gets transit from Lumen (Level3.net was acquired by Lumen), while as6453.net is Tata which appears to be the transit provider for Sonic.
I brought this to the attention of the VPS operator (mythic-beasts.com) and they suggested that someone at Sonic ought to look at how they're exchanging IPv6 routes with Tata. Part of their response:
Traceroute from the VPS shows that traffic inbound to Sonic is taking a detour via Chicago and Seattle on its way from Fremont to Santa Clara.
The clearest traceroute-type output I get is from the "mtr" command:
Code: Select all
$ mtr -b -w -c 10 ns1.sonic.net
...
1.|-- vds-fmt2-c.mythic-beasts.com (2a06:1c80::10) 0.0% 10 0.4 0.7 0.3 2.9 0.8
2.|-- lo.router-fmt2-b.mythic-beasts.com (2a04:ad80:2::1) 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 5-2-11.ear3.SanJose1.Level3.net (2001:1900:3000:24::1) 0.0% 10 1.4 1.5 1.4 1.7 0.1
4.|-- 2001:1900::3:208 0.0% 10 2.3 5.5 2.1 21.6 5.9
5.|-- 6453-3356-sjo.sp.lumen.tech (2001:1900:4:3::242) 70.0% 10 2.1 2.2 2.1 2.4 0.2
6.|-- if-bundle-77-2.qcore1.sqn-sanjose.ipv6.as6453.net (2001:5a0:3e02:100::12) 80.0% 10 2.6 2.3 2.0 2.6 0.5
7.|-- if-bundle-2-2.qcore2.sqn-sanjose.ipv6.as6453.net (2001:5a0:3e02:110::3) 60.0% 10 2.2 2.2 1.7 2.8 0.4
8.|-- if-bundle-61-2.qcore2.ct8-chicago.ipv6.as6453.net (2001:5a0:3e02:130::b) 0.0% 10 45.0 45.3 44.7 45.8 0.4
9.|-- if-ae-25-2.tcore2.00s-seattle.ipv6.as6453.net (2001:5a0:4404::) 0.0% 10 53.1 53.7 53.0 57.2 1.4
10.|-- if-ae-2-2.tcore1.00s-seattle.ipv6.as6453.net (2001:5a0:200:400::90) 0.0% 10 53.0 54.3 52.9 65.0 3.8
11.|-- if-ae-45-2.tcore1.sv1-santaclara.ipv6.as6453.net (2001:5a0:200:400::11) 0.0% 10 54.3 54.4 54.3 54.5 0.1
12.|-- if-ae-0-2.tcore2.sv1-santaclara.ipv6.as6453.net (2001:5a0:4e00::2) 0.0% 10 54.2 54.7 54.2 56.9 0.8
13.|-- if-be-11-2.ecore1.epao1-paloalto.ipv6.as6453.net (2001:5a0:e00::4) 80.0% 10 55.0 55.0 55.0 55.0 0.0
14.|-- 2001:5a0:1300::101 0.0% 10 54.5 59.2 54.4 91.5 11.6
15.|-- 202.ae0.cr2.pao1.sonic.net (2001:5a8:5:403f::90:a) 0.0% 10 66.5 96.0 54.9 192.1 48.0
16.|-- 201.ae2.cr2.equinix-sj.sonic.net (2001:5a8:5:403f::8d:a) 0.0% 10 55.0 101.1 55.0 227.1 46.9
17.|-- ae1.cs2.equinix-sj.sonic.net (2001:5a8:5:403f::a7:b) 0.0% 10 60.9 89.7 55.3 353.2 92.7
18.|-- et-0-0-48.vm-dist1-2.equinix-sj.sonic.net (2001:5a8:5:2b::b) 0.0% 10 60.1 94.0 56.7 357.9 93.3
19.|-- ns1.sonic.net (2001:5a8::11) 0.0% 10 54.3 54.4 54.1 56.0 0.6
I brought this to the attention of the VPS operator (mythic-beasts.com) and they suggested that someone at Sonic ought to look at how they're exchanging IPv6 routes with Tata. Part of their response:
I hope someone at Sonic can take a look at this.I wonder if Sonic are missing an IPv6 session with Tata in San Jose?
