US Cable Support → Comcast HSI > Awkward Routing To New York Servers?CT->Illinois

Awkward Routing To New York Servers?CT->Illinois

I'm in CT and I noticed today that my latency to NY is really high for the small distance(About 55-80ms). I did a couple tracerts and I assume that it's saying that I'm being routed all the way to Illinois first. Is it?

(Ignore the wild latency; my Linksys doesn't like tracerts)

(To CT.gov website)
over a maximum of 30 hops:

1 6 ms 9 ms 9 ms Linksys [192.168.1.1]
2 19 ms 9 ms 10 ms -----------
3 19 ms 19 ms 20 ms ----------
4 21 ms 19 ms 20 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
5 24 ms 19 ms 39 ms pos-0-1-0-0-ar01.berlin.ct.hartford.comcast.net [68.87.144.149]
6 18 ms 19 ms 24 ms pos-1-9-0-0-ar01.woburn.ma.boston.comcast.net [68.87.144.166]
7 53 ms 49 ms 59 ms he-4-12-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.41]
8 59 ms 59 ms 59 ms pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.162]
9 51 ms 59 ms 58 ms 173.167.58.138
10 57 ms 59 ms 59 ms 0.xe-3-1-3.XL3.CHI13.ALTER.NET [152.63.70.122]
11 72 ms 69 ms 79 ms 0.ge-1-3-0.XL1.NYC8.ALTER.NET [152.63.21.101]
12 78 ms 69 ms 69 ms 0.so-0-0-0.XR1.NYC9.ALTER.NET [152.63.9.57]
13 78 ms 79 ms 79 ms 183.ATM6-0.GW1.HAR2.ALTER.NET [152.63.23.1]
14 68 ms 79 ms 99 ms StateofCT-gw.customer.alter.net [157.130.26.2]
15 78 ms 89 ms 72 ms 159.247.3.212
16 75 ms 79 ms 79 ms www.ct.gov [159.247.0.240]

Trace complete.

To NY:

Tracing route to atlanticmetro.net [204.145.69.1]
over a maximum of 30 hops:

1 6 ms 6 ms 2 ms Linksys [192.168.1.1]
2 21 ms 19 ms 19 ms -------
3 16 ms 10 ms 19 ms --------
4 15 ms 19 ms 17 ms ---------
5 24 ms 22 ms 29 ms be-61-ar01.berlin.ct.hartford.comcast.net [68.85.69.37]
6 30 ms 29 ms 29 ms pos-1-8-0-0-ar01.woburn.ma.boston.comcast.net [68.87.144.162]
7 48 ms 59 ms 55 ms he-4-10-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.92.49]
8 54 ms 59 ms 59 ms pos-1-3-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.158]
9 75 ms 79 ms 79 ms 208.178.58.61
10 78 ms 80 ms 74 ms atlantic-metro-com.tengigabitethernet6-3.ar8.nyc1.gblx.net [159.63.51.6]
11 74 ms 76 ms 72 ms ve238.csr2.lga1.amcbb.net [108.60.132.125]
12 70 ms 70 ms 79 ms www.atlanticmetro.net [204.145.69.1]

Trace complete.

if you look a little closer everything is be routed to chicago atm, something must have broke...

Looks ok from the South of you in Delaware"

Target Name: www.ct.gov
IP: 159.247.0.240
Date/Time: 10/3/2013 5:22:44 PM

1 1 ms 2 ms 0 ms 1 ms [172.16.12.1]
2 25 ms 11 ms 26 ms 24 ms [68.57.24.1]
3 22 ms 12 ms 10 ms 11 ms te-1-4-ur01.rt202.de.panjde.comcast.net [68.85.79.1]
4 21 ms 10 ms 11 ms 11 ms te-9-1-ur02.newcastle.de.panjde.comcast.net [68.86.211.205]
5 10 ms 11 ms 10 ms 12 ms te-9-3-ur01.newcastle.de.panjde.comcast.net [68.86.153.254]
6 14 ms 14 ms 18 ms 15 ms xe-7-0-0-0-ar03.newcastle.de.panjde.comcast.net [68.86.211.197]
7 20 ms N/A N/A 18 ms pos-5-10-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.92.177]
8 17 ms 19 ms 17 ms 16 ms he-0-11-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.83.74]
9 17 ms 15 ms 14 ms 16 ms n-a.GW12.IAD8.ALTER.NET [152.179.50.205]
10 17 ms 14 ms 17 ms 19 ms 0.xe-4-2-0.XL1.IAD8.ALTER.NET [152.63.36.41]
11 19 ms 20 ms 19 ms 34 ms 0.so-7-2-0.XL1.NYC8.ALTER.NET [152.63.146.53]
12 25 ms 23 ms 30 ms 20 ms 0.so-3-0-0.XR1.NYC8.ALTER.NET [152.63.19.30]
13 23 ms 21 ms 23 ms 22 ms 183.ATM6-0.GW1.HAR2.ALTER.NET [152.63.23.1]
14 26 ms 24 ms 24 ms 25 ms StateofCT-gw.customer.alter.net [157.130.26.2]
15 23 ms 23 ms 25 ms 24 ms [159.247.3.212]
16 25 ms 23 ms 24 ms 26 ms www.ct.gov [159.247.0.240]

Ping statistics for www.ct.gov
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 23ms, Maximum = 26ms, Average = 24ms
--
"ONE team - ONE city - ONE dream!!"

Yeah, looks like whatever the next hop after Woburn would be is getting routed to Chicago on the iBone no matter where it's directed. More than likely it's a downed router. I'm sure it'll correct itself eventually...Here's another sample of your latest IP from DE.

Target Name: ottcommunications.com
IP: 216.220.230.111
Date/Time: 10/3/2013 5:57:27 PM

1 0 ms 1 ms [172.16.12.1]
2 90 ms 12 ms [68.57.24.1]
3 9 ms 9 ms te-1-4-ur01.rt202.de.panjde.comcast.net [68.85.79.1]
4 31 ms 9 ms [68.86.211.58]
5 13 ms 12 ms xe-5-0-2-0-ar03.coatesville.pa.panjde.comcast.net [68.85.192.241]
6 16 ms 11 ms ae-8-0-ar03.newcastle.de.panjde.comcast.net [69.139.193.213]
7 16 ms 17 ms pos-5-12-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.137]
8 19 ms 45 ms 23-30-207-94-static.hfc.comcastbusiness.net [23.30.207.94]
9 23 ms 23 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
10 24 ms 27 ms [4.69.201.69]
11 23 ms 25 ms ae-1-8.bar2.Boston1.Level3.net [4.69.140.97]
12 23 ms 25 ms ae-0-11.bar1.Boston1.Level3.net [4.69.140.89]
13 32 ms 29 ms CRC-COMMUNI.bar1.Boston1.Level3.net [4.31.154.22]
14 35 ms 34 ms bngr-r1.v3201.midmaine.com [216.220.246.15]
15 32 ms 30 ms knds-r3.v3200.midmaine.com [216.220.246.17]
16 32 ms 33 ms knds-r1.v3204.ottcommunications.com [216.220.246.104]
17 32 ms 31 ms ottcommunications.com [216.220.230.111]

Ping statistics for ottcommunications.com
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 31ms, Maximum = 32ms, Average = 31ms
--
"ONE team - ONE city - ONE dream!!"

Could also be a BGP routing table / advertisement issue.

You can Google for info. If it is, as an end user, there is nothing you can do about it anyway.

BGP "publishes" routes to others, If they know the front door is going to be busy, it says "deliveries to the rear, following path X
If you don't follow path X you may be ignored, or more likely charged more for using the front door. since virtually all residential rates are base on the cheapest route available, they follow the directions is published.
It's not a whole lot different then the airline hub and spoke system where if "your company's " airline doesn't have a direct flight from Seattle to Philly you may instead go Seattle to Dallas to Atlanta to Newark to Philly for $0.01 in savings.... not as direct, probably not as fast, but fine by the bean counters.

OT but there is another tool there that shows the routes and advertisments history/changing (on a polar-like chart?)
Sometime it changes for 30 seconds, sometime for days, and sometimes on a schedule.
if the end points are big with lots of possible paths it's not a problem, small provider depend on a chain of connection the users will suffer.

no, it's just interesting to see the shift between one route and another. and these are shifts in the outside routes, pretty sure Comcast won't be publicizing their internal network

How do I view that?

I'm seeing the same thing in northeastern Mass.

traceroute to boston.com (66.151.183.34), 30 hops max, 60 byte packets
 1  router (192.168.1.1)  20.282 ms  20.273 ms  20.266 ms
 2  96.128.48.1 (96.128.48.1)  43.653 ms  43.661 ms  43.653 ms
 3  68.85.161.217 (68.85.161.217)  43.617 ms  43.625 ms  43.619 ms
 4  68.85.106.41 (68.85.106.41)  43.618 ms  43.615 ms  43.608 ms
 5  he-4-10-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.92.49)  69.727 ms  69.729 ms  69.720 ms
 6  he-0-10-0-1-pe04.350ecermak.il.ibone.comcast.net (68.86.83.54)  69.727 ms  54.361 ms  54.352 ms
 7  173.167.58.138 (173.167.58.138)  54.365 ms  60.185 ms  65.756 ms
 8  0.xe-3-0-1.XL3.CHI13.ALTER.NET (152.63.66.189)  65.697 ms  61.593 ms  65.661 ms
 9  0.ge-7-2-0.XL3.BOS4.ALTER.NET (152.63.5.182)  86.687 ms  86.678 ms  86.656 ms
10  0.xe-10-2-0.GW15.BOS4.ALTER.NET (152.63.21.138)  86.611 ms  69.185 ms  85.634 ms
11  internap-gw.customer.alter.net (152.179.134.214)  85.646 ms  85.642 ms  85.627 ms
12  border12.te8-1-bbnet2.bsn.pnap.net (63.251.128.105)  85.624 ms  85.619 ms  108.834 ms
13  * * *
 

It's an experimental widget, similar to BGPlay »stat.ripe.net/widget/bgplay#w.resource=7922
but allows you more control, not finding it right now, they keep adding and removing them to work on them

Looks like mine just started behaving:

traceroute to boston.com (66.151.183.34), 64 hops max, 52 byte packets
 1  router (192.168.1.1)  1.696 ms  3.602 ms  0.786 ms
 2  96.128.48.1 (96.128.48.1)  11.467 ms  9.791 ms  13.459 ms
 3  68.85.161.217 (68.85.161.217)  14.424 ms  21.361 ms  12.905 ms
 4  68.86.226.125 (68.86.226.125)  16.020 ms  9.838 ms  12.580 ms
 5  be-21-ar01.needham.ma.boston.comcast.net (68.85.106.45)  17.463 ms  18.783 ms  18.166 ms
 6  he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.93.185)  20.817 ms  30.983 ms  31.351 ms
 7  he-0-10-0-0-pe03.111eighthave.ny.ibone.comcast.net (68.86.83.90)  19.225 ms  24.505 ms  22.095 ms
 8  n-a.gw13.nyc1.alter.net (152.179.220.125)  17.841 ms  17.395 ms  19.724 ms
 9  0.xe-3-1-0.xl3.nyc1.alter.net (152.63.19.46)  21.913 ms
    0.xe-1-0-0.xl4.nyc1.alter.net (152.63.5.6)  19.562 ms
    0.xe-8-2-0.xl4.nyc1.alter.net (152.63.20.174)  19.124 ms
10  0.ge-4-0-0.xl3.bos4.alter.net (152.63.17.30)  34.450 ms  25.876 ms  26.091 ms
11  0.ge-9-0-0.gw15.bos4.alter.net (152.63.24.42)  26.815 ms
    0.xe-8-1-0.gw15.bos4.alter.net (152.63.24.30)  89.227 ms  29.287 ms
12  internap-gw.customer.alter.net (152.179.134.214)  38.434 ms  27.805 ms  33.511 ms
13  border12.te7-1-bbnet1.bsn.pnap.net (63.251.128.42)  26.246 ms  26.440 ms  26.250 ms
14  * * *
15  * *^C
 

BGPlay itself should work on any STABLE browser, but like a lot of RIPE stuff server is SLOW and is SLOW to resolve. but a pretty cool tool once you learn it's tricks.