I live in Pennsylvania and I've been using Verizon wireless DSL for many years now with very few hiccups in between. However, since Thursday I've been experiencing severe lag spikes that last around a minute or two. While it makes browsing online annoying, it makes online gaming next to impossible. My latency will go from 31 ms to 6000+ in a matter of seconds, and I lag out completely and am forced to make the game crash so I can re-log.
I did a trace route and showed one of the techs that work for the game I play, and they told me it was a problem on my ISPs end, so here I am. I spoke with a Verizon service rep about this issue for a few hours last night and they insisted everything was ok on their end. He wouldn't even look at my trace route. I hoped to include it here so that maybe someone else could give me a hand/tell me whats going on. Thank you in advance!
Tracing route to USEast.battle.net [63.240.202.126]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms LIBERTO-HOME [192.168.0.1]
2 1 ms 1 ms 1 ms dslrouter [192.168.1.1]
3 10 ms 10 ms 10 ms 10.7.16.1
4 10 ms 10 ms 16 ms at-1-2-1-1721.PHIL-CORE-RTR2.verizon-gni.net [130.81.11.225]
5 11 ms 11 ms 12 ms so-7-2-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.20.138]
6 63 ms 74 ms 49 ms so-10-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.17.3]
7 17 ms 17 ms 16 ms 0.ae2.BR1.IAD8.ALTER.NET [152.63.32.158]
8 18 ms 18 ms 18 ms 192.205.36.141
9 24 ms 20 ms 22 ms cr2.wswdc.ip.att.net [12.122.81.250]
10 18 ms 18 ms 18 ms 12.122.135.9
11 20 ms 22 ms 19 ms 12.122.251.78
12 20 ms 20 ms 20 ms mdf001c7613r0004-gig-12-1.wdc1.attens.net [63.240.193.14]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
#1 What is the brand and model of your modem?
#2 What is the brand and model of your router?
My modem is a Westell 6100F. The router is a Cisco Linksys E4200.
Is the Westell 6100F bridged to allow the Linksys router to maintain the PPPoE connection? If yes, is the Linksys using an MTU of 1492 rather than Automatic or 1500? These are key things to make sure of when you're working with DSL.
The best thing to do while the lag spike is occurring is to perform a traceroute during the time when the problem is happening. Also, take note of the tine of when it happens, and also see if your speeds are severely degraded at the time on both the upload and the download.
The problem could be with a PPPoE session becoming stale and not being re-established completely, it could be with faulty equipment, for example a Fiber card or a switch that drops packets periodically, or it could be an odd problem involving what people call "Dark Buffers" which might not be the case and even I am not the most familiar with since it's difficult to spot. I doubt it's congestion as I've not heard of congestion causing a problem for only a minute with sudden jumps.
@Smith6612 wrote:Is the Westell 6100F bridged to allow the Linksys router to maintain the PPPoE connection?
While I am not the OP, by looking at the route it seems that the modem combo is not bridged.
Points OP to http://www.dslreports.com/faq/13600
I live in the kutztown area, and I have been having the same issue. I got a text from my neighbor tonight, and she is having dsl issues as well. My problems started after the heavy wind and rain last friday morning around 4:30 am. It also seems to get worse in the evenings(maybe when the wind picks up?) Seeing that multiple people in the same area are having issues, it would appear the problem is on verizon.
I don't mean to be hijacking this thread, but it looks like the OP and I are having the same issue, so I thought I would try to help out. The problem just started again, and I got a traceroute while it was happening. As you can see my modem is bridged, and I am having the issue. This seems to be the normal pattern. Internet appears slow and laggy. I start a constant ping, they go up to 2000 ms or so then they eventually start dropping. After a minute or so, it comes back and works for a little while.
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms LUCKYPINE [192.168.0.1]
2 * 2000 ms 2098 ms 10.7.16.1
3 1990 ms * 1903 ms at-1-2-1-1720.PHIL-CORE-RTR1.verizon-gni.net [130.81.11.221]
4 * 2079 ms * so-7-2-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.20.136]
5 2179 ms 2113 ms * so-8-0-1-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.19.76]
6 2060 ms 2022 ms 1763 ms 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
7 * 2185 ms 2047 ms ae16.edge1.washingtondc12.level3.net [4.68.62.133]
8 2284 ms * 2043 ms vl-3603-ve-227.ebr2.Washington12.Level3.net [4.69.158.42]
9 1826 ms 2024 ms 2058 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
10 1919 ms * 1889 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
11 2099 ms 2079 ms 2011 ms ge-5-0-60.hsa1.Washington2.Level3.net [4.69.149.51]
12 2040 ms 2115 ms * vnsc-bak.sys.gtei.net [4.2.2.2]
13 LUCKYPINE [192.168.0.1] reports: Destination net unreachable.
Did you ever figure out what the problem was? I also live in Montgomery County Pennsylvania and since last week also have been having the intermittent service. Several times in an hour we will lose connection for about 1-2minutes. If something worked for you please pass it on. I know it is an verizon issue as several tenants in the same building as me are also having the same problem. thanks..
I am also in Montgomery County and have the same problem. Below are some ping/packloss statistics from right now. This has been happening since last thursday. Notice the 30-50% packetloss and ping times reaching up to 5 seconds. Yesterday when monitoring, pings reached 8 seconds for about a minute or two.
PING google.com (74.125.115.103) 56(84) bytes of data.
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=2 ttl=53 time=27.5 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=4 ttl=53 time=27.4 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=5 ttl=53 time=28.8 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=6 ttl=53 time=26.2 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=7 ttl=53 time=27.5 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=9 ttl=53 time=28.3 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=10 ttl=53 time=26.8 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=11 ttl=53 time=26.4 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=13 ttl=53 time=27.7 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=16 ttl=53 time=27.2 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=17 ttl=53 time=27.5 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=19 ttl=53 time=26.6 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=20 ttl=53 time=27.5 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=21 ttl=53 time=27.3 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=22 ttl=53 time=29.4 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=25 ttl=53 time=864 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=26 ttl=53 time=1228 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=30 ttl=53 time=3052 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=31 ttl=53 time=3520 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=34 ttl=53 time=3756 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=36 ttl=53 time=1869 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=38 ttl=53 time=27.4 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=39 ttl=53 time=26.6 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=41 ttl=53 time=28.1 ms
64 bytes from vx-in-f103.1e100.net (74.125.115.103): icmp_req=42 ttl=53 time=27.0 ms
^C
--- google.com ping statistics ---
43 packets transmitted, 25 received, 41% packet loss, time 42101ms
rtt min/avg/max/mdev = 26.237/592.544/3756.284/1145.594 ms, pipe 4
PING google.com (74.125.115.99) 56(84) bytes of data.
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=2 ttl=53 time=27.7 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=3 ttl=53 time=26.7 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=5 ttl=53 time=26.3 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=8 ttl=53 time=26.6 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=9 ttl=53 time=28.8 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=10 ttl=53 time=29.7 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=11 ttl=53 time=26.7 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=13 ttl=53 time=26.4 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=14 ttl=53 time=29.0 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=15 ttl=53 time=27.4 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=16 ttl=53 time=27.2 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=17 ttl=53 time=28.2 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=18 ttl=53 time=28.2 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=19 ttl=53 time=26.7 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=20 ttl=53 time=28.8 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=21 ttl=53 time=29.4 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=24 ttl=53 time=548 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=25 ttl=53 time=1017 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=27 ttl=53 time=1876 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=28 ttl=53 time=1713 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=30 ttl=53 time=26.0 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=32 ttl=53 time=26.0 ms
64 bytes from vx-in-f99.1e100.net (74.125.115.99): icmp_req=33 ttl=53 time=28.9 ms
^C
--- google.com ping statistics ---
33 packets transmitted, 23 received, 30% packet loss, time 32078ms
rtt min/avg/max/mdev = 26.009/247.031/1876.236/527.674 ms, pipe 2
PING google.com (74.125.115.147) 56(84) bytes of data.
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=1 ttl=53 time=26.7 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=2 ttl=53 time=28.6 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=3 ttl=53 time=323 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=6 ttl=53 time=1687 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=8 ttl=53 time=2616 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=13 ttl=53 time=4717 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=14 ttl=53 time=4958 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=20 ttl=53 time=1936 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=21 ttl=53 time=952 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=22 ttl=53 time=27.3 ms
64 bytes from vx-in-f147.1e100.net (74.125.115.147): icmp_req=23 ttl=53 time=27.5 ms
^C
--- google.com ping statistics ---
25 packets transmitted, 11 received, 56% packet loss, time 24026ms
rtt min/avg/max/mdev = 26.726/1572.817/4958.027/1760.104 ms, pipe 5
Have other users that were experiencing this lag issue notice an improvement? I have not had the lag since sunday evening, but was just wondering if the cause was actually found and fixed.
Start a new topic or ask questions in the open forum.
