-TrenchTracing route to 8.12.64.130 over a maximum of 30 hops
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [xx.xx.xx.xx]
2 3 ms 4 ms 4 ms L100.DLLSTX-VFTTP-75.verizon-gni.net [xx.xx.xx.xx]
3 6 ms 9 ms 10 ms G0-5-1-3.DLLSTX-LCR-21.verizon-gni.net [130.81.129.42]
4 * * * Request timed out.
5 33 ms 32 ms 32 ms 0.ae1.XL3.CHI13.ALTER.NET [140.222.225.179]
6 35 ms 39 ms 36 ms TenGigE0-6-1-0.GW2.CHI13.ALTER.NET [152.63.65.133]
7 33 ms 34 ms 31 ms tinet-gw.customer.alter.net [152.179.92.6]
8 59 ms 59 ms 62 ms xe-9-1-0.dal33.ip4.gtt.net [89.149.181.149]
9 35 ms 34 ms 35 ms gtt-gw.ip4.gtt.net [173.241.130.138]
10 * 65 ms * ae1-70g.cr2.dfw1.us.as4436.gtt.net [69.31.63.185]
11 32 ms 37 ms 82 ms 0.ae2.XL4.CHI13.ALTER.NET [140.222.225.191]
12 35 ms 37 ms 34 ms TenGigE0-5-0-0.GW2.CHI13.ALTER.NET [152.63.66.110]
13 34 ms 34 ms 62 ms 0.xe-11-1-0.BR3.CHI13.ALTER.NET [152.63.70.25]
14 35 ms 35 ms 34 ms 0.ae2.XL4.CHI13.ALTER.NET [140.222.225.191]
15 34 ms 34 ms 37 ms TenGigE0-5-0-0.GW2.CHI13.ALTER.NET [152.63.66.110]
16 31 ms 32 ms 35 ms 0.xe-9-0-0.BR3.CHI13.ALTER.NET [152.63.69.221]
17 64 ms 32 ms 34 ms 0.ae2.XL4.CHI13.ALTER.NET [140.222.225.191]
18 32 ms 34 ms 34 ms 0.xe-9-0-0.BR3.CHI13.ALTER.NET [152.63.69.221]
19 36 ms 99 ms 44 ms 0.ae2.XL3.CHI13.ALTER.NET [140.222.225.187]
20 60 ms 59 ms 59 ms 0.ae2.BR1.IAD8.ALTER.NET [140.222.229.165]
21 59 ms 62 ms 59 ms 0.ae1.BR1.IAD8.ALTER.NET [140.222.229.163]
22 58 ms 57 ms 57 ms 0.xe-10-0-1.XL2.IAD8.ALTER.NET [152.63.41.170]
23 62 ms 62 ms 59 ms 0.ae1.BR1.IAD8.ALTER.NET [140.222.229.163]
24 59 ms 59 ms 59 ms 0.xe-10-0-1.XL2.IAD8.ALTER.NET [152.63.41.170]
25 88 ms 49 ms 112 ms 0.xe-2-0-2.XT2.NYC4.ALTER.NET [152.63.0.153]
26 116 ms 102 ms 127 ms 0.xe-2-0-2.XT2.NYC4.ALTER.NET [152.63.0.153]
27 121 ms 109 ms 122 ms 0.xe-5-0-3.XL2.IAD8.ALTER.NET [152.63.37.214]
28 130 ms 112 ms 112 ms 0.xe-2-1-4.XT1.NYC4.ALTER.NET [152.63.5.17]
29 133 ms 129 ms 109 ms 0.xe-8-0-0.BR2.NYC4.ALTER.NET [152.63.21.213]
30 109 ms 112 ms 136 ms 0.xe-11-1-0.BR3.NYC4.ALTER.NET [152.63.24.105]
Trace complete.
Lag/high ping
Re: Lag/high ping
During tonight's lag ballz on Twin Rivers, what I saw from my end is that my traffic was being bounced around Chicago and New York rather than staying in Dallas / Fort Worth. After 30 hops it hadn't even stopped bouncing yet:
Re: Lag/high ping
Trench in November 2014 wrote:...for some reason today I have a 40ms slowdown leaving Verizon's network to alter.net, which wasn't happening last night:
Last night the issue has finally been corrected, with the new LAN trace showing the traffic no longer goes through "CHI" routers, which my bet was they were in Chicago.tracert in November 2014 wrote:Tracing route to 8.12.64.130 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [xx.xx.xx.xx]
2 3 ms 4 ms 4 ms L100.DLLSTX-VFTTP-75.verizon-gni.net [xx.xx.xx.xx]
3 7 ms 7 ms 6 ms G0-5-1-3.DLLSTX-LCR-21.verizon-gni.net [130.81.129.42]
4 * * * Request timed out.
5 32 ms 31 ms 32 ms 0.ae1.XL3.CHI13.ALTER.NET [140.222.225.179]
6 33 ms 34 ms 37 ms TenGigE0-6-4-0.GW2.CHI13.ALTER.NET [152.63.66.114]
7 32 ms 32 ms 36 ms tinet-gw.customer.alter.net [152.179.92.6]
8 92 ms 91 ms 92 ms xe-10-0-2.dal33.ip4.gtt.net [141.136.110.25]
9 51 ms 51 ms 52 ms gtt-gw.ip4.gtt.net [173.241.130.138]
10 51 ms 52 ms 54 ms as20473.xe-5-1-2.cr1.dfw1.us.as4436.gtt.net [69.31.63.238]
11 53 ms 51 ms 51 ms 8.12.64.130
Trace complete.
Regardless of whether it had been due to errors in Verizon's route choice, or simply bad route information coming from ALTER.NET, now when I attempt to reach the server I stay within "DFW.ALTER.NET" instead of being sent to "CHI.ALTER.NET". And correspondingly, the round trip is now lower-latency.tracert wrote:Tracing route to 8.12.64.130 over a maximum of 30 hops
1 1 ms 1 ms 2 ms Wireless_Broadband_Router.home [xx.xx.xx.xx]
2 4 ms 9 ms 6 ms L100.DLLSTX-VFTTP-75.verizon-gni.net [xx.xx.xx.xx]
3 9 ms 9 ms 7 ms G0-5-1-3.DLLSTX-LCR-21.verizon-gni.net [130.81.129.42]
4 * * * Request timed out.
5 14 ms 9 ms 9 ms 0.ae1.BR1.DFW13.ALTER.NET [140.222.227.169]
6 22 ms 12 ms 7 ms 204.255.168.66
7 7 ms 12 ms 7 ms xe-3-0-0.dal33.ip4.gtt.net [141.136.106.78]
8 7 ms 10 ms 9 ms gtt-gw.ip4.gtt.net [173.241.130.138]
9 9 ms 6 ms 7 ms as20473.xe-5-1-2.cr1.dfw1.us.as4436.gtt.net [69.31.63.238]
10 9 ms 7 ms 6 ms 8.12.64.130
Trace complete.
-Trench