Quantcast
Channel: Comcast XFINITY forum - dslreports.com
Viewing all articles
Browse latest Browse all 15706

routing issue

$
0
0
I'm located in Seattle. Can someone explain how these routes make sense? First one to Chicago, second one to NY. Chicago: Tracing route to host.colocrossing.com [198.144.179.111] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms dlinkrouter.hsd1.wa.comcast.net [192.168.0.1] 2 24 ms 27 ms 17 ms 73.99.164.1 3 10 ms 11 ms 13 ms te-0-2-0-1-sur03.tacoma.wa.seattle.comcast.net [68.87.206.85] 4 24 ms 13 ms 13 ms ae-28-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.205] 5 16 ms 16 ms 14 ms he-1-3-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.93.165] 6 29 ms 31 ms 31 ms pos-2-14-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.85.202] 7 56 ms 37 ms 36 ms pos-0-5-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.87.162] 8 41 ms 40 ms 41 ms xe-9-3-0.sjc10.ip4.tinet.net [213.200.80.165] 9 81 ms 102 ms 80 ms xe-0-1-1.chi11.ip4.tinet.net [89.149.184.1] 10 81 ms 80 ms 92 ms as23353.chi11.ip4.tinet.net [199.229.229.210] 11 84 ms 82 ms 81 ms ae12.cr2.ord6.us.scnet.net [204.93.204.83] 12 82 ms 84 ms 89 ms 72.ae2.ar2.ord6.us.scnet.net [204.93.204.159] 13 88 ms 81 ms 82 ms as36352.xe-0-1-0.ar2.ord6.us.scnet.net [50.31.170.126] 14 86 ms 90 ms 83 ms 10ge-2.fz146.chi1.colocrossing.com [206.217.137.254] 15 82 ms 84 ms 84 ms host.colocrossing.com [205.234.152.250] 16 82 ms 84 ms 81 ms host.colocrossing.com [198.144.179.111] Trace complete. New York: Tracing route to host.colocrossing.com [206.217.128.165] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms dlinkrouter.hsd1.wa.comcast.net [192.168.0.1] 2 11 ms 11 ms 11 ms 73.99.164.1 3 11 ms 10 ms 11 ms te-0-2-0-1-sur03.tacoma.wa.seattle.comcast.net [68.87.206.85] 4 73 ms 13 ms 38 ms ae-28-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.205] 5 22 ms 15 ms 20 ms he-1-6-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.94.69] 6 42 ms 39 ms 39 ms he-0-14-0-0-cr01.denver.co.ibone.comcast.net [68.86.87.49] 7 64 ms 63 ms 63 ms he-5-9-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.89.41] 8 80 ms 83 ms 83 ms he-4-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.149] 9 81 ms 82 ms 80 ms he-1-10-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.86.250] 10 82 ms 85 ms 87 ms as4436-1-c.111eighthave.ny.ibone.comcast.net [173.167.57.162] 11 90 ms 84 ms 89 ms as20473.ae7.ar1.nyc3.us.nlayer.net [69.31.34.62] 12 82 ms 81 ms 84 ms vl20-br1.pnj1.choopa.net [108.61.65.41] 13 85 ms 83 ms 84 ms vl150-as3.pnj1.choopa.net [108.61.93.250] 14 82 ms 81 ms 83 ms 108.61.16.82.choopa.net [108.61.16.82] 15 82 ms 84 ms 82 ms 10ge-1.14-7.ny1.colocrossing.com [206.217.128.250] 16 89 ms 83 ms 82 ms host.colocrossing.com [206.217.128.165] Trace complete. First off, I ping the same to Chicago as I do to NY. That shouldn't be happening. Secondly, why does Chicago route through California? NY heads east immediately to Denver, which is what Chicago use to do. Both routes are on Comcast's network so I would think they'd be optimal, but apparently that isn't the case. What is wrong with the routing to Chicago? Any insight is appreciated.

Viewing all articles
Browse latest Browse all 15706

Trending Articles