In Boston, going to a Comcast Business IP. Here's a part of the traceroute.
Verizon FIOS handing to ALterNet who then hands to Level 3 and sends it to San Jose, giving us an RTT 6 times greater than it should be. Started potentially about 7-10 days ago.
Anybody know who and how to contact somebody at Verizon to get them to have the routing optimized again. Frontline support can't escalate.
1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 1 ms 2 ms 192.168.1.1
3 8 ms 9 ms 8 ms L100.BSTNMA-VFTTP-72.verizon-gni.net [96.237.177
.1]
4 9 ms 8 ms 6 ms G11-0-1-772.BSTNMA-LCR-07.verizon-gni.net [130.8
1.96.114]
5 9 ms 7 ms 9 ms so-0-3-0-0.BOS-BB-RTR1.verizon-gni.net [130.81.2
9.252]
6 19 ms 19 ms 19 ms so-9-1-0-0.NY325-BB-RTR1.verizon-gni.net [130.81
.19.70]
7 16 ms 16 ms 19 ms 0.so-0-0-0.XL3.NYC4.ALTER.NET [152.63.1.41]
8 19 ms 15 ms 19 ms 0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
9 17 ms 19 ms 19 ms te-7-1-0.edge2.NewYork2.level3.net [4.68.127.21]
10 15 ms 16 ms 19 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
11 18 ms 19 ms 19 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
12 93 ms 89 ms 88 ms ae-2-2.ebr4.SanJose1.Level3.net [4.69.135.185]
13 88 ms 88 ms 91 ms ae-84-84.csw3.SanJose1.Level3.net [4.69.134.250]
14 85 ms 86 ms 86 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
15 90 ms 91 ms 91 ms COMCAST-IP.edge1.SanJose1.Level3.net [4.79.43.13
8]
16 109 ms 109 ms 108 ms pos-0-13-0-0-cr01.denver.co.ibone.comcast.net [6
8.86.85.133]
17 99 ms 102 ms 100 ms pos-0-14-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.117]
18 106 ms 109 ms 106 ms pos-2-15-0-0-ar01.woburn.ma.boston.comcast.net [
68.86.95.26]
19 107 ms 107 ms 109 ms po-63-ur02.lowell.ma.boston.comcast.net [68.85.6
9.78]
20 109 ms 109 ms 108 ms 68.85.184.70
