dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
17

Darknessfall
Premium Member
join:2012-08-17
Motorola MG8725
Asus RT-N66

Darknessfall

Premium Member

Re: Northeast routing latency

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 Member
join:2001-01-25
Mechanicsville, VA

ropeguru

Premium Member

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

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

EG to Darknessfall

Premium Member

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 Member
join:2012-08-17
Motorola MG8725
Asus RT-N66

Darknessfall

Premium Member

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 Member
join:2006-11-18
Union, NJ

EG

Premium Member

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.