dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
751
share rss forum feed


netloss

@comcast.net

Northeast routing latency

I've had comcast service for many years and i always used to ping from CT to NY/NJ servers below 15ms. i don't recall when things changed, but now my pings have more than tripped by the time they reach NY from boston, it's a pretty dramatic increase from MA to NY..

guess the good old days of decent latency are gone.. it isn't terrible, but when gaming every little makes a difference. i'm seriously considering switching to DSL even though speed wise it will be a huge downgrade, but seems comcast is the worst ISP for gaming.

normally i ping 50ms to central US servers, yet my ping is nearly the same for servers located just 1 state over.

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    1 ms    1 ms    1 ms  192.168.1.1
  2    7 ms     8 ms     7 ms  96.67.88.1
  3    6 ms     7 ms     8 ms  te-8-1-ur01.newhaven.ct.hartford.comcast.net [68.85.187.117]
  4    14 ms    12 ms    11 ms  be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
  5    23 ms    24 ms    16 ms  pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.69]
  6    62 ms    47 ms    48 ms  he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
  7    41 ms    49 ms    49 ms  173.167.58.26
  8    41 ms    44 ms    42 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
  9    43 ms    43 ms    44 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
 10    42 ms    41 ms    44 ms  www.dslreports.com [209.123.109.175]
 

Darknessfall
Premium
join:2012-08-17
kudos:3
Reviews:
·Comcast
·AT&T U-Verse

Yes, the dreaded NY server!

Tracing route to Dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 * * * Request timed out.
3 8 ms 7 ms 8 ms -------
4 13 ms 15 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
5 23 ms 14 ms 23 ms pos-1-5-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.73]
6 44 ms 47 ms 47 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
7 44 ms 42 ms 44 ms 173.167.58.26
8 55 ms 44 ms 47 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
9 45 ms 43 ms 43 ms vlan804.esd1.oct.nac.net [209.123.10.2]
10 43 ms 43 ms 43 ms www.dslreports.com [209.123.109.175]

Trace complete.

Tracing route to 96.67.88.1 over a maximum of 30 hops(Your CMTS)

1 1 ms 1 ms 1 ms 10.0.0.1
2 * * * Request timed out.
3 7 ms 9 ms 7 ms te-3-2-ur01.===.ct.hartford.comcast.net [68.87.159.49]
4 8 ms 9 ms 8 ms 96.67.88.1

Trace complete.


plat2on1

join:2002-08-21
Hopewell Junction, NY
reply to netloss

you may be able to "fix" it by pulling an ip address from a different block. change the mac address of your router and reset your modem a few times until you get a "good" one.

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  172.16.0.1
  2     9 ms     7 ms     8 ms  96.67.136.1
  3    13 ms     7 ms     8 ms  te-4-2-ur01.carmel.ny.hartford.comcast.net [68.87.180.161]
  4    13 ms    10 ms    12 ms  po-64-ur01.danbury.ct.hartford.comcast.net [68.86.230.253]
  5    14 ms    11 ms    16 ms  be-53-ar01.berlin.ct.hartford.comcast.net [68.85.162.185]
  6    20 ms    18 ms    19 ms  pos-1-8-0-0-ar01.woburn.ma.boston.comcast.net [68.87.144.162]
  7    19 ms    19 ms    23 ms  pos-1-12-0-0-ar01.needham.ma.boston.comcast.net [68.86.224.166]
  8    24 ms    23 ms    23 ms  he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.93.185]
  9    23 ms    23 ms    21 ms  173.167.58.26
 10    23 ms    23 ms    25 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
 11    29 ms    24 ms    29 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
 12    24 ms    23 ms    23 ms  www.dslreports.com [209.123.109.175]
 

Darknessfall
Premium
join:2012-08-17
kudos:3
Reviews:
·Comcast
·AT&T U-Verse

1 edit

NY



NJ


NY


MA(Comcast Server)


IL(Comcast Server)


MA


Darknessfall
Premium
join:2012-08-17
kudos:3
Reviews:
·Comcast
·AT&T U-Verse

Just got a new modem and a new IP .

Tracing route to Dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 * * * Request timed out.
2 6 ms 7 ms 19 ms ----------
3 13 ms 10 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
4 13 ms 15 ms 15 ms pos-1-5-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.73]
5 21 ms 23 ms 23 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
6 20 ms 20 ms 24 ms 173.167.58.26
7 21 ms 21 ms 21 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
8 20 ms 21 ms 22 ms vlan804.esd1.oct.nac.net [209.123.10.2]
9 21 ms 20 ms 21 ms www.dslreports.com [209.123.109.175]

Trace complete.



ropeguru
Premium
join:2001-01-25
Mechanicsville, VA

Wow, I didn't realize there was anyone out there who was fast enough to have a 20ms difference effect their browsing to DSLR.


johnnn

join:2007-01-25
Ypsilanti, MI
reply to Darknessfall

I frequently encounter congestion when accessing servers through New York routes all the way out here in the Midwest. There are a number of congested routes in Chicago too. Started a thread about it a couple days ago, but was shot down quickly for lack of "conclusive" data =/


Darknessfall
Premium
join:2012-08-17
kudos:3

The weird thing I noticed was that I went through the same route in NY. The 68.86.95.29 was the same in both the before and current routes. Maybe they have a priority system? I guess they like to not give certain IP ranges good latency :/.



EG
The wings of love
Premium
join:2006-11-18
Union, NJ
kudos:9
reply to Darknessfall

said by Darknessfall:

Just got a new modem and a new IP .

Tracing route to Dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 * * * Request timed out.
2 6 ms 7 ms 19 ms ----------
3 13 ms 10 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
4 13 ms 15 ms 15 ms pos-1-5-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.73]
5 21 ms 23 ms 23 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
6 20 ms 20 ms 24 ms 173.167.58.26
7 21 ms 21 ms 21 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
8 20 ms 21 ms 22 ms vlan804.esd1.oct.nac.net [209.123.10.2]
9 21 ms 20 ms 21 ms www.dslreports.com [209.123.109.175]

Trace complete.

You still are traversing the same NY ibone router in the forward path that you were in your earlier trace..

6 44 ms 47 ms 47 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]

However, with your new WAN / public IP, perhaps the return path routing is now different. With the way that BGP works, a new IP will more likely force a change in the return path rather than the forward.

Darknessfall
Premium
join:2012-08-17
kudos:3
Reviews:
·Comcast
·AT&T U-Verse

said by EG:

said by Darknessfall:

Just got a new modem and a new IP .

Tracing route to Dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 * * * Request timed out.
2 6 ms 7 ms 19 ms ----------
3 13 ms 10 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
4 13 ms 15 ms 15 ms pos-1-5-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.73]
5 21 ms 23 ms 23 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
6 20 ms 20 ms 24 ms 173.167.58.26
7 21 ms 21 ms 21 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
8 20 ms 21 ms 22 ms vlan804.esd1.oct.nac.net [209.123.10.2]
9 21 ms 20 ms 21 ms www.dslreports.com [209.123.109.175]

Trace complete.

You still are traversing the same NY ibone router in the forward path that you were in your earlier trace..

6 44 ms 47 ms 47 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]

However, with your new WAN / public IP, perhaps the return path routing is now different. With the way that BGP works, a new IP will more likely force a change in the return path rather than the forward.

I noticed that too, weird.


EG
The wings of love
Premium
join:2006-11-18
Union, NJ
kudos:9

It's not "weird". It is what it is. A tracert doesn't reveal the return path routing. One does not know what path is being taken for the return. A trace would need to be performed from the other end to see what route is being used. The latency numbers you see on any particular hop are RTT's (Round Trip Times) so the excessive latency could actually be being introduced / caused by the return routing.