Alter to level 3 route timeout
Airwalk
Newbie

The last year I been having lags problem.  Anyone else?

Tracing route to 192.64.170.62 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms L100.NWRKNJ-VFTTP-112.verizon-gni.net [98.109.67.1]
3 13 ms 11 ms 11 ms G1-2-2-7.NWRKNJ-LCR-21.verizon-gni.net [100.41.195.30]
4 6 ms 7 ms 8 ms ae1-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.146]
5 14 ms 11 ms 12 ms 0.xe-3-0-1.BR1.NYC1.ALTER.NET [152.63.5.149]
6 * * * Request timed out.
7 90 ms 92 ms 92 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 90 ms 87 ms 87 ms ae-47-47.ebr2.NewYork1.Level3.net [4.69.201.33]
9 93 ms 93 ms 91 ms ae-2-2.ebr1.SanJose1.Level3.net [4.69.135.185]
10 89 ms 87 ms 90 ms ae-61-61.csw1.SanJose1.Level3.net [4.69.153.2]
11 87 ms 84 ms 88 ms ae-62-62.ebr2.SanJose1.Level3.net [4.69.153.17]
12 89 ms 133 ms 86 ms ae-1-6.bar2.SanFrancisco1.Level3.net [4.69.140.153]
13 93 ms 92 ms 92 ms ae-0-11.bar1.SanFrancisco1.Level3.net [4.69.140.145]

0 Likes
Re: Alter to level 3 route timeout
ortiz34
Enthusiast - Level 3

yes it's been  terrible, I started at 35/35 then kicked down to 25/25 then kicked down to 15/15

I've all but started wireless tethering off my cell phone and will probably drop FIOS completely

0 Likes
Re: Alter to level 3 route timeout
eljefe2
Master - Level 1

@Airwalk wrote:

The last year I been having lags problem.  Anyone else?

Tracing route to 192.64.170.62 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms L100.NWRKNJ-VFTTP-112.verizon-gni.net [98.109.67.1]
3 13 ms 11 ms 11 ms G1-2-2-7.NWRKNJ-LCR-21.verizon-gni.net [100.41.195.30]
4 6 ms 7 ms 8 ms ae1-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.146]
5 14 ms 11 ms 12 ms 0.xe-3-0-1.BR1.NYC1.ALTER.NET [152.63.5.149]
6 * * * Request timed out.
7 90 ms 92 ms 92 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 90 ms 87 ms 87 ms ae-47-47.ebr2.NewYork1.Level3.net [4.69.201.33]
9 93 ms 93 ms 91 ms ae-2-2.ebr1.SanJose1.Level3.net [4.69.135.185]
10 89 ms 87 ms 90 ms ae-61-61.csw1.SanJose1.Level3.net [4.69.153.2]
11 87 ms 84 ms 88 ms ae-62-62.ebr2.SanJose1.Level3.net [4.69.153.17]
12 89 ms 133 ms 86 ms ae-1-6.bar2.SanFrancisco1.Level3.net [4.69.140.153]
13 93 ms 92 ms 92 ms ae-0-11.bar1.SanFrancisco1.Level3.net [4.69.140.145]


If I traceroute to that same IP address you did I see about the same results.  However, I deal with San Francisco Bay Area web sites all the time and haven't noticed any unusual lag.

0 Likes