| Northeast routing problems?Is anyone experiencing high latency issues today?
From my house (Comcast - Danbury, CT) to a customer site (Comcast - Kenilworth, NJ):
Tracing route to Customer [173.161.141.xxx]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms My house [173.166.91.xxx]
2 <1 ms <1 ms <1 ms 173-166-91-102-newengland.hfc.comcastbusiness.net [173.166.91.102]
3 6 ms 6 ms 7 ms 96.120.64.73
4 9 ms 7 ms 9 ms te-5-4-ur02.danbury.ct.hartford.comcast.net [68.87.157.97]
5 12 ms 11 ms 11 ms be-61-ar01.chartford.ct.hartford.comcast.net [68.85.69.17]
6 15 ms 13 ms 13 ms pos-1-5-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.73]
7 14 ms 15 ms 14 ms pos-0-0-0-0-ar01.woburn.ma.boston.comcast.net [68.85.162.142]
8 46 ms 49 ms 44 ms pos-2-1-0-0-cr01.chicago.il.ibone.comcast.net [68.86.95.25]
9 49 ms 47 ms 47 ms pos-1-7-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.88.46]
10 73 ms 67 ms 67 ms pos-4-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.141]
11 64 ms 64 ms 63 ms so-0-0-0-0-ar03.plainfield.nj.panjde.comcast.net [68.86.95.174]
12 98 ms 88 ms 72 ms xe-0-0-0-0-sur01.union.nj.panjde.comcast.net [68.85.62.2]
13 89 ms 69 ms 71 ms 68.86.192.182
14 74 ms 73 ms 72 ms 73.187.224.114
15 73 ms 73 ms 74 ms Customer [173.161.141.xxx]
Trace complete.
From my house (Comcast - Danbury, CT) to my office (Verizon FIOS - Port Chester, NY):
Tracing route to Office [108.6.21.xx]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms My house [173.166.91.xxx]
2 1 ms <1 ms 1 ms 173-166-91-102-newengland.hfc.comcastbusiness.net [173.166.91.102]
3 7 ms 5 ms 5 ms 96.120.64.73
4 6 ms 7 ms 5 ms te-5-3-ur01.danbury.ct.hartford.comcast.net [68.87.157.93]
5 19 ms 8 ms 9 ms be-53-ar01.berlin.ct.hartford.comcast.net [68.85.162.185]
6 15 ms 15 ms 13 ms pos-1-9-0-0-ar01.woburn.ma.boston.comcast.net [68.87.144.166]
7 45 ms 45 ms 44 ms pos-2-2-0-0-cr01.chicago.il.ibone.comcast.net [68.86.93.121]
8 66 ms 65 ms 65 ms pos-2-10-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.87.114]
9 82 ms 79 ms 79 ms pos-0-14-0-0-cr01.miami.fl.ibone.comcast.net [68.86.85.194]
10 106 ms 89 ms 80 ms pos-0-4-0-0-pe01.nota.fl.ibone.comcast.net [68.86.88.98]
11 196 ms 197 ms * 216.6.16.9
12 206 ms 187 ms 185 ms 0.xe-7-3-0.BR1.MIA19.ALTER.NET [204.255.168.9]
13 232 ms 187 ms 187 ms 0.xe-10-2-0.XL1.MIA19.ALTER.NET [152.63.85.81]
14 186 ms * * 0.ge-3-3-0.XL3.MIA4.ALTER.NET [152.63.85.73]
15 241 ms 200 ms * 0.ge-3-2-0.TPA01-BB-RTR1.verizon-gni.NET [152.63.4.10]
16 * * * Request timed out.
17 * 213 ms 212 ms Office [108.6.21.xx]
Trace complete.
From a customer site (Comcast - Kenilworth, NJ) to my office (Verizon FIOS - Port Chester, NY):
Tracing route to Office [108.6.21.xx]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Customer [173.161.141.xxx]
2 1 ms <1 ms <1 ms 173-161-141-238-Philadelphia.hfc.comcastbusiness.net [173.161.141.238]
3 29 ms 29 ms 30 ms 73.191.226.1
4 62 ms 8 ms 9 ms xe-9-2-0-0-sur01.union.nj.panjde.comcast.net [68.86.192.185]
5 11 ms 9 ms 9 ms xe-3-0-0-0-ar03.plainfield.nj.panjde.comcast.net [68.85.62.1]
6 12 ms 11 ms 17 ms pos-3-10-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.92.217]
7 20 ms 16 ms 23 ms pos-0-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.85.93]
8 30 ms 30 ms 30 ms pos-4-3-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.87.70]
9 48 ms 45 ms 47 ms pos-0-12-0-0-cr01.miami.fl.ibone.comcast.net [68.86.88.218]
10 45 ms 45 ms 45 ms pos-0-0-0-0-pe01.nota.fl.ibone.comcast.net [68.86.87.102]
11 152 ms 160 ms 160 ms 216.6.16.9
12 152 ms 182 ms 156 ms 0.xe-7-3-0.BR1.MIA19.ALTER.NET [204.255.168.9]
13 152 ms 150 ms 150 ms 0.xe-10-2-0.XL2.MIA19.ALTER.NET [152.63.85.85]
14 153 ms 153 ms 153 ms 0.ge-3-3-0.XL4.MIA4.ALTER.NET [152.63.85.77]
15 156 ms 159 ms 158 ms so-7-0-0-0.TPA01-BB-RTR1.verizon-gni.net [130.81.19.36]
16 * * * Request timed out.
17 185 ms 174 ms 169 ms Office [108.6.21.xx]
Is anyone else seeing issues? I'm also getting some significant (15-20%) packet loss.
Thanks,
- Sherman |
|
andyrossPremium,MVM
join:2003-05-04
Schaumburg, IL | Without knowing what the path used to be, it almost seems as if Boston and NY are not talking to each other on Comcast's ibone, so it's routing around it. |
|
hhahn
join:2011-06-25
Marlton, NJ
3 edits | reply to sherman06810
I came here to post the same thing. Starting at about 12:50 today (+/- 3 mins), the northeast routing kicked the bucket. Connecting from Comcast to the VPN which is hosted on a FiOS business connection, it's practically unusable.
Here's a chart of ping over time:
And a traceroute to Comcast:
(clipped)
3 4 ms 2 ms 4 ms l100.cmdnnj-vfttp-35.verizon-gni.net [98.110.91.1]
4 52 ms 27 ms 22 ms g0-3-4-3.cmdnnj-lcr-22.verizon-gni.net [130.81.182.74]
5 * * * Request timed out.
6 12 ms 12 ms 11 ms so-10-1-0-0.res-bb-rtr2.verizon-gni.net [130.81.17.3]
7 12 ms 11 ms 15 ms 0.ae2.br2.iad8.alter.net [152.63.34.73]
8 13 ms 11 ms 12 ms ix-20-0.tcore2.aeq-ashburn.as6453.net [216.6.87.33]
9 151 ms 152 ms 151 ms te-0-14-0-1-pe01.ashburn.va.ibone.comcast.net [66.208.233.49]
10 151 ms 152 ms 151 ms pos-3-11-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.86.145]
11 * * 154 ms so-1-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.86.95.158]
12 155 ms 156 ms * xe-0-0-0-0-sur01.mtlaurel.nj.panjde.comcast.net [68.85.62.114]
13 169 ms 169 ms 169 ms 68.86.192.214
(clipped)
Here it is from Comcast:
(clipped)
3 xe-2-0-0-0-sur01.mtlaurel.nj.panjde.comcast.net (68.86.192.213) 8.464 ms 9.050 ms 7.210 ms
4 xe-3-1-0-0-ar03.audubon.nj.panjde.comcast.net (68.85.62.113) 10.469 ms 10.465 ms 8.964 ms
5 pos-3-8-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.95.153) 13.219 ms 13.469 ms
pos-3-9-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.95.157) 14.457 ms
6 pos-4-3-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.87.70) 28.906 ms 69.537 ms 26.697 ms
7 pos-0-11-0-0-cr01.miami.fl.ibone.comcast.net (68.86.88.214) 42.573 ms 43.209 ms 43.831 ms
8 pos-0-0-0-0-pe01.nota.fl.ibone.comcast.net (68.86.87.102) 42.299 ms 39.955 ms 41.422 ms
9 * Vlan514.icore2.MLN-Miami.as6453.net (66.110.9.101) 160.271 ms 159.278 ms
10 0.xe-7-3-0.BR1.MIA19.ALTER.NET (204.255.168.9) 148.013 ms 145.845 ms 146.371 ms
11 * 0.xe-10-2-0.XL2.MIA19.ALTER.NET (152.63.85.85) 145.442 ms *
12 * 0.ge-3-3-0.XL4.MIA4.ALTER.NET (152.63.85.77) 147.670 ms 189.280 ms
13 * * 130.81.23.218 (130.81.23.218) 150.986 ms
14 * * P9-0-0.CMDNNJ-LCR-02.verizon-gni.net (130.81.29.35) 169.007 ms
15 * * P12-0-0.CMDNNJ-LCR-04.verizon-gni.net (130.81.27.197) 158.012 ms
16 * P0-12-2-0.CMDNNJ-LCR-22.verizon-gni.net (130.81.27.91) 160.232 ms 159.569 ms
(clipped)
|
|
| reply to andyross
said by andyross:Without knowing what the path used to be, it almost seems as if Boston and NY are not talking to each other on Comcast's ibone, so it's routing around it.
Here's what the routing was a year ago:
»[Connectivity] Routing question
I was pleasantly surprised that Comcast fixed the issue within a few hours of posting here...hopefully they're browsing today |
|
| reply to hhahn
Same her in California.
C:\Users\jeremy.ANDERSON>tracert 64.220.124.102
Tracing route to 64.220.124.102.ptr.us.xo.net [64.220.124.102]
over a maximum of 30 hops:
1 41 ms 29 ms 29 ms 50.131.56.1
2 9 ms 9 ms 9 ms te-4-1-ur01.sffolsom.ca.sfba.comcast.net [68.85.
100.121]
3 12 ms 10 ms 14 ms te-1-10-0-2-ar01.sfsutro.ca.sfba.comcast.net [68
.85.154.62]
4 13 ms 11 ms 11 ms pos-3-2-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.90.153]
5 21 ms 21 ms 21 ms pos-2-13-0-0-cr01.losangeles.ca.ibone.comcast.ne
t [68.86.86.206]
6 52 ms 52 ms 52 ms pos-0-13-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.146]
7 83 ms 83 ms 83 ms pos-1-12-0-0-cr01.miami.fl.ibone.comcast.net [68
.86.88.126]
8 84 ms 82 ms 83 ms pos-0-3-0-0-pe01.nota.fl.ibone.comcast.net [68.8
6.87.230]
9 188 ms * 189 ms Vlan514.icore2.MLN-Miami.as6453.net [66.110.9.10
1]
10 189 ms 189 ms 189 ms te10-2-0d0.cir1.miami2-fl.us.xo.net [206.111.1.2
05]
11 192 ms * 193 ms vb2001.rar3.dallas-tx.us.xo.net [207.88.13.174]
12 214 ms 211 ms 212 ms te-3-2-0.rar3.denver-co.us.xo.net [207.88.12.42]
13 219 ms 215 ms 215 ms te-3-0-0.rar3.seattle-wa.us.xo.net [207.88.12.81
]
14 209 ms 213 ms 210 ms ae0d0.mcr1.seattle-wa.us.xo.net [216.156.0.194]
15 212 ms 210 ms 214 ms ge0-0.clr1.seattle-wa.us.xo.net [207.88.83.146]
16 213 ms 215 ms 213 ms 64.220.124.102.ptr.us.xo.net [64.220.124.102]
Trace complete.
C:\Users\jeremy.ANDERSON> |
|
|
|
1 edit | reply to sherman06810
Same issue with me, I am in California;
|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 249 | 249 | 0 | 0 | 2 | 1 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
|te-9-2-ur01.placerville.ca.sacra.comcast.net - 0 | 249 | 249 | 7 | 10 | 64 | 11 |
|te-8-1-ar02.sacramento.ca.sacra.comcast.net - 0 | 249 | 249 | 8 | 16 | 115 | 9 |
|be-2-ar03.sacramento.ca.sacra.comcast.net - 0 | 249 | 249 | 8 | 11 | 18 | 11 |
|pos-0-2-0-0-cr01.sacramento.ca.ibone.comcast.net - 0 | 249 | 249 | 9 | 13 | 21 | 14 |
|pos-1-7-0-0-cr01.losangeles.ca.ibone.comcast.net - 0 | 249 | 249 | 19 | 22 | 55 | 24 |
|pos-0-9-0-0-cr01.dallas.tx.ibone.comcast.net - 0 | 249 | 249 | 50 | 53 | 60 | 54 |
|pos-1-13-0-0-cr01.miami.fl.ibone.comcast.net - 0 | 249 | 249 | 80 | 85 | 94 | 86 |
|pos-0-0-0-0-pe01.nota.fl.ibone.comcast.net - 0 | 249 | 249 | 81 | 85 | 93 | 83 |
| 216.6.16.9 - 51 | 81 | 40 | 0 | 192 | 204 | 190 |
| 0.xe-7-3-0.BR1.MIA19.ALTER.NET - 45 | 89 | 49 | 185 | 191 | 247 | 186 |
| 0.xe-10-2-0.XL1.MIA19.ALTER.NET - 45 | 89 | 49 | 0 | 189 | 211 | 188 |
| 0.so-6-1-0.XL3.SEA1.ALTER.NET - 46 | 88 | 48 | 210 | 213 | 222 | 216 |
| POS6-0.GW7.SEA1.ALTER.NET - 40 | 97 | 59 | 209 | 213 | 216 | 210 |
| internap-gw.customer.alter.net - 52 | 81 | 39 | 207 | 221 | 410 | 211 |
| border8.t7-1-bbnet1.sef.pnap.net - 49 | 85 | 44 | 207 | 211 | 223 | 211 |
| t - 40 | 97 | 59 | 207 | 215 | 227 | 211 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
|
 danielk
join:2009-02-01
Greenwood, MO
 ·Comcast
| reply to sherman06810
I've noticed the same thing too today while playing SWTOR, where latency is all over the place, and from tracerts to just the home page for it, www.swtor.com, everything is find until it hits FL then that's where it starts getting dicey.
Tracing route to a1158.g.akamai.net [128.242.186.248]
over a maximum of 30 hops:
1 23 ms 14 ms 24 ms 69.242.128.1
2 8 ms 8 ms 9 ms te-9-2-ur02.independence.mo.indepen.comcast.net
[68.87.234.229]
3 10 ms 9 ms 9 ms te-2-1-ar02.independence.mo.indepen.comcast.net
[68.87.234.22]
4 11 ms 9 ms 9 ms te-4-1-ar01.independence.mo.indepen.comcast.net
[68.87.234.1]
5 20 ms 56 ms 22 ms te-0-2-0-4-cr01.chicago.il.ibone.comcast.net [68
.86.91.145]
6 50 ms 42 ms 40 ms pos-2-11-0-0-cr01.atlanta.ga.ibone.comcast.net [
68.86.86.246]
7 57 ms 64 ms 59 ms pos-0-15-0-0-cr01.miami.fl.ibone.comcast.net [68
.86.86.198]
8 57 ms 54 ms 56 ms pos-0-5-0-0-pe01.nota.fl.ibone.comcast.net [68.8
6.88.102]
9 * * * Request timed out.
10 160 ms * 160 ms ae-6.r04.miamfl02.us.bb.gin.ntt.net [129.250.9.3
3]
11 160 ms 169 ms * ae-3.r21.miamfl02.us.bb.gin.ntt.net [129.250.4.2
50]
12 * * * Request timed out.
13 190 ms 167 ms * ae-0.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.5
9]
14 171 ms * 171 ms ae-4.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.2
01]
15 * 171 ms 172 ms ae-2.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.2
02]
16 * 172 ms 174 ms 128.242.186.248 |
|
 ccnetengComcast EmployeePremium,VIP
join:2008-02-06
Philadelphia, PA
1 edit | reply to sherman06810
There appears to be a problem between Comcast (AS7922) and TATA Communications (AS6453). Both engineering teams are aware and working the issue. It should be resolved shortly. Very sorry about the inconvenience. |
|
 whfsdudePremium
join:2003-04-05
Washington, DC
 ·T-Mobile US
| reply to sherman06810
Seeing major issues with v6 as well.
will@whfsdude:~$ traceroute6 2001:470:8:60e:adb0:e52f:445:8543
traceroute to 2001:470:8:60e:adb0:e52f:445:8543 (2001:470:8:60e:adb0:e52f:445:8543), 30 hops max, 80 byte packets
1 2001:49f0:4006::1 (2001:49f0:4006::1) 0.722 ms 0.982 ms 1.234 ms
2 2001:559::311 (2001:559::311) 1.678 ms 1.616 ms 1.549 ms
3 pos-2-7-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5fe::1) 2.887 ms 2.824 ms 2.756 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
will@whfsdude:~$ traceroute6 tunnelbroker.net
traceroute to tunnelbroker.net (2001:470:0:63::2), 30 hops max, 80 byte packets
1 2001:49f0:4006::1 (2001:49f0:4006::1) 0.597 ms 0.830 ms 1.246 ms
2 2001:559::311 (2001:559::311) 2.070 ms 2.054 ms 2.033 ms
3 pos-2-7-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5fe::1) 1.154 ms 1.134 ms 4.900 ms
4 pos-1-9-0-0-cr01.chicago.il.ibone.comcast.net (2001:558:0:f60d::1) 1.945 ms 1.802 ms 1.782 ms
5 pos-2-12-0-0-cr01.atlanta.ga.ibone.comcast.net (2001:558:0:f54f::2) 23.369 ms 23.358 ms 23.218 ms
6 pos-0-13-0-0-cr01.miami.fl.ibone.comcast.net (2001:558:0:f590::1) 39.836 ms 46.827 ms 40.111 ms
7 pos-0-5-0-0-pe01.nota.fl.ibone.comcast.net (2001:558:0:f619::2) 37.347 ms 37.339 ms 37.319 ms
8 2001:5a0:1800:300::4d (2001:5a0:1800:300::4d) 143.244 ms 143.255 ms 143.226 ms
9 if-ae8.1775.tcore1.AEQ-Ashburn.ipv6.as6453.net (2001:5a0:600:400::21) 151.504 ms 151.492 ms 151.313 ms
10 v317.core1.ash1.he.net (2001:470:0:191::1) 150.028 ms 149.987 ms *
11 10gigabitethernet7-4.core1.pao1.he.net (2001:470:0:1e4::1) 205.371 ms 205.359 ms 205.302 ms
12 10gigabitethernet1-2.core1.fmt1.he.net (2001:470:0:2e::1) 204.437 ms 204.398 ms 214.413 ms
13 * * *
14 * * *
15 * * *
|
|
danielk
join:2009-02-01
Greenwood, MO | reply to sherman06810
looks like they're making some headway, my latency in SWTOR dropped back down to 40-50 like normal. |
|
| reply to sherman06810
Routing for me has gotten a lot better but still seeing some ping spikes which I would expect. |
|
| reply to sherman06810
Much better. I am now routing from San Jose directly to Seattle. |
|
