Skip to main content
Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you bring your phone.
end of navigation menu
Slower than promised DSL connection
oltean
Enthusiast

Hello,

I would like to inform anyone from Verizon who is reading this board that I am not getting the promised speed of .5 to 1 Mbps at all times. Sometimes I have been getting speeds of
0.155 Mbps as tested by speedtest.net and http://my.verizon.com/micro/speedtest/broadband/#. The technical support will not help me as they said they ran a Line Test and that came out to be fine. They wanted to do a shared screen to delete my temporary internet files but I did that myself.  They repeatedly tell me to check my speed at www.speedtest.net which I did but they offer no other solution to the problem.  No other help was provided to me. What can I do to resolve this problem?

Thank you

0 Likes
Re: Slower than promised DSL connection
tns
Master

Regretably few from Verizon read these boards.  Those who do can sometimes direct you to someone that can help, but are not themselves part of the normal support structure.

0 Likes
Re: Slower than promised DSL connection
smith6612
Super User
Super User

Just need some information to start helping you resolve this issue. What modem do you have, and are these slow speeds taking place at random or are they consistent with the time of day (eg; slowdown at night)?

0 Likes
Re: Slower than promised DSL connection
oltean
Enthusiast

These slow speeds are taking place at random. For example I just checked a second ago and on the first try I got 0.24 Mbps download on the second try 0.74 Mbps download and on the third try 0.44 Mbps download. My modem is Actiontec model GT784WNV.

0 Likes
Re: Slower than promised DSL connection
smith6612
Super User
Super User

OK.

Run the test found here (just press the Submit button) and copy/paste the results: http://lg.dreamhost.com/

0 Likes
Re: Slower than promised DSL connection
oltean
Enthusiast

Ok, here it is:

traceroute to pool-74-111-47-229.syrcny.east.verizon.net (74.111.47.229), 30 hops max, 46 byte packets 1 ip-66-33-193-1 (66.33.193.1) 7.654 ms 1.971 ms 0.965 ms 2 rampart-0.hq.newdream.net (66.33.201.2) 0.848 ms 1.784 ms * 3 ip-66-33-201-222 (66.33.201.222) 0.891 ms 0.872 ms 1.386 ms 4 vl1109.mag01.lax04.atlas.cogentco.com (38.104.210.173) 27.246 ms 26.685 ms * 5 te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165) 11.035 ms * 1.595 ms 6 te0-2-0-7.mpd22.lax01.atlas.cogentco.com (154.54.2.237) 1.153 ms te0-3-0-7.ccr22.lax01.atlas.cogentco.com (154.54.43.249) 1.014 ms 0.960 ms 7 * te4-8.ccr02.lax05.atlas.cogentco.com (154.54.30.194) 1.968 ms te7-8.ccr02.lax05.atlas.cogentco.com (154.54.30.198) 1.045 ms 8 uunet.lax05.atlas.cogentco.com (154.54.13.86) 1.141 ms 1.545 ms 8.238 ms 9 0.ge-1-2-0.LAX01-BB-RTR2.verizon-gni.net (152.63.112.6) 2.239 ms 1.900 ms 1.654 ms 10 P12-0-0.SYRCNY-LCR-02.verizon-gni.net (130.81.28.187) 87.371 ms 87.318 ms 87.584 ms 11 G4-0-203.SYRCNY-SYRCNYSU-ERXG03.verizon-gni.net (130.81.195.169) 92.768 ms 92.163 ms 92.150 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Finshed!

Running...
PING 74.111.47.229 (74.111.47.229) from 208.97.141.21 : 56(84) bytes of data. 64 bytes from 74.111.47.229: icmp_seq=1 ttl=49 time=2325 ms 64 bytes from 74.111.47.229: icmp_seq=2 ttl=49 time=2276 ms 64 bytes from 74.111.47.229: icmp_seq=3 ttl=49 time=2301 ms 64 bytes from 74.111.47.229: icmp_seq=4 ttl=49 time=2403 ms 64 bytes from 74.111.47.229: icmp_seq=5 ttl=49 time=2367 ms 64 bytes from 74.111.47.229: icmp_seq=6 ttl=49 time=2338 ms 64 bytes from 74.111.47.229: icmp_seq=7 ttl=49 time=2343 ms 64 bytes from 74.111.47.229: icmp_seq=8 ttl=49 time=2364 ms 64 bytes from 74.111.47.229: icmp_seq=9 ttl=49 time=2551 ms 64 bytes from 74.111.47.229: icmp_seq=10 ttl=49 time=2483 ms --- 74.111.47.229 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9089ms rtt min/avg/max/mdev = 2276.684/2375.578/2551.877/79.831 ms, pipe 3 Finshed!

0 Likes
Re: Slower than promised DSL connection
oltean
Enthusiast

Another thing. I noticed that these low speeds as displayed by speedtest.net occur when I watch any streaming video. Will a streaming video cause the tested speed to be lower than when I am not streaming any video. Shouldn't the speed remain constant in the range of .5 to 1 Mbps download even though I am streaming a video?

0 Likes
Re: Slower than promised DSL connection
MrB681
Newbie

yes my problem exactly every darn week end  it s starting to really pee me off . I am thinking about deducting this none service from my bill.

0 Likes
Re: Slower than promised DSL connection
smith6612
Super User
Super User

Well, the speed tests don't account for traffic already on your network. They simply measure what they can obtain. If you have a 1Mbps connection, that is 1000kbps of usable capacity for the line. Say the video places the connection at 800kbps of capacity being used, and holds to it's utilization (rather than bursts traffic in). The speed test will report 200kbps as your speed since the stream is consuming the rest of the capacity. With normal file transfers (eg; YouTube when playing HD video as the lower qualities throttle after enough has buggered), the speed will ideally split in half. The file will download at 500kbps, and the speed test will report 500kbps. If it's just the speed test running, the speed test will report 1000kbps.

There is a decent enough jump in the latency between the Syracuse, NY Core backbone router and the Juniper ERX you're attached to, to say that perhaps the router is under some load. Those typically are 1-2ms in response time from the backbone when tracing from a looking glass server. When you're about 5-10ms between two points in a relatively small area, you're looking at either de-prioritization of the traceroute packets (in this case, UDP which are often not de-prioritized) or you are looking at a scenario where there is a decent load on the device or path to the device.

The pings you posted up show a rediculous amount of latency. A 2 second lag time is purely unacceptable. That's higher than most satellite connections (and satellite is really slow due to latency alone!). That is a sign of congestion or excessive load/lack of balancing on Verizon's end if your connection is not transferring data what so ever.

Just double check that you do not have anything transferring data, and your Wireless if you have it is not being leeched on by others nearby. Using the upload can shoot your latency into the 2 second range when saturated completely and buffered. If there is no traffic, someone from Verizon needs to investigate the network on their end for peek time performance issues.

Here's a trace to my connection from the same server. The last two reported hops (DSL-RTR1) would be one of the backbone-attached routers for my area as there are several, along with DSL-RTR2 which is the really old edge router I've yelled at Verizon to stay on due to the equipment I'm attached to. Notice, the latency is no more than 1ms between the core router and the edge router, and this is old gear and it is peak hour usage in my area.

traceroute to pool-<ip-removed>.bflony.east.verizon.net (), 30 hops max, 46 byte packets
 1  ip-66-33-193-1 (66.33.193.1)  100.548 ms  0.612 ms  0.308 ms
 2  rampart-0.hq.newdream.net (66.33.201.2)  12.062 ms  1.522 ms  1.211 ms
 3  ip-66-33-201-222 (66.33.201.222)  0.841 ms  0.836 ms  0.822 ms
 4  vl1109.mag01.lax04.atlas.cogentco.com (38.104.210.173)  57.733 ms  171.720 ms  204.989 ms
 5  te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165)  3.054 ms te8-3.ccr01.lax04.atlas.cogentco.com (154.54.83.161)  53.817 ms te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165)  1.022 ms
 6  te0-2-0-7.mpd22.lax01.atlas.cogentco.com (154.54.2.237)  0.980 ms te0-3-0-7.ccr22.lax01.atlas.cogentco.com (154.54.43.249)  1.310 ms  0.993 ms
 7  te3-4.ccr02.lax05.atlas.cogentco.com (154.54.3.10)  9.144 ms te8-3.ccr02.lax05.atlas.cogentco.com (154.54.29.202)  1.659 ms te9-1.ccr02.lax05.atlas.cogentco.com (154.54.44.130)  1.342 ms
 8  uunet.lax05.atlas.cogentco.com (154.54.13.86)  8.861 ms  1.067 ms  1.032 ms
 9  0.ge-1-2-0.LAX01-BB-RTR2.verizon-gni.net (152.63.112.6)  1.165 ms  1.358 ms  1.189 ms
10  as1-0.BUFF-CORE-RTR1.verizon-gni.net (130.81.20.105)  81.337 ms  81.226 ms  81.248 ms
11  P3-0-0.BUFF-DSL-RTR2.verizon-gni.net (130.81.13.74)  81.245 ms  81.200 ms  81.464 ms

Re: Slower than promised DSL connection
oltean
Enthusiast

Ok, I ran the tests again while making sure I am not streaming any video or not doing anything that would cause the test to be inaccurate. The wireless is protected by password and it doesn't look like someone is getting a free ride. Here are the results once again. What do you suggest I do to inprove this connection? Do I have a valid argument that Verizon is not offering me the best service? How would I go about telling them what the situation is so that they can fix it at their end?

traceroute to pool-{edited for privacy}.syrcny.east.verizon.net ({edited for privacy}), 30 hops max, 46 byte packets

1 ip-66-33-193-1 (66.33.193.1) 69.237 ms 1.089 ms 0.502 ms

2 rampart-0.hq.newdream.net (66.33.201.2) 1.064 ms 1.086 ms 0.841 ms

3 ip-66-33-201-222 (66.33.201.222) 0.837 ms 1.195 ms 0.824 ms

4 vl1109.mag01.lax04.atlas.cogentco.com (38.104.210.173) 1.389 ms 1.268 ms 1.313 ms

5 te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165) 1.009 ms te8-3.ccr01.lax04.atlas.cogentco.com (154.54.83.161) 0.929 ms te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165) 0.988 ms

6 te0-2-0-7.mpd22.lax01.atlas.cogentco.com (154.54.2.237) 1.325 ms te0-3-0-7.ccr22.lax01.atlas.cogentco.com (154.54.43.249) 0.992 ms 1.030 ms

7 te4-4.ccr02.lax05.atlas.cogentco.com (154.54.82.162) 1.183 ms te9-8.ccr02.lax05.atlas.cogentco.com (154.54.44.134) 1.217 ms te3-4.ccr02.lax05.atlas.cogentco.com (154.54.3.10) 1.162 ms

8 uunet.lax05.atlas.cogentco.com (154.54.13.86) 1.089 ms 1.284 ms 1.540 ms

9 0.ge-1-2-0.LAX01-BB-RTR2.verizon-gni.net (152.63.112.6) 1.655 ms 2.272 ms 1.602 ms

10 P12-0-0.SYRCNY-LCR-02.verizon-gni.net (130.81.28.187) 86.441 ms 86.259 ms 86.337 ms

11 G4-0-203.SYRCNY-SYRCNYSU-ERXG03.verizon-gni.net (130.81.195.169) 91.157 ms 98.468 ms 91.201 ms

PING {edited for privacy} ({edited for privacy}) from 208.97.141.21 : 56(84) bytes of data.

64 bytes from {edited for privacy}: icmp_seq=1 ttl=49 time=140 ms

64 bytes from {edited for privacy}: icmp_seq=2 ttl=49 time=137 ms

64 bytes from {edited for privacy}: icmp_seq=3 ttl=49 time=137 ms

64 bytes from {edited for privacy}: icmp_seq=4 ttl=49 time=139 ms

 64 bytes from {edited for privacy}icmp_seq=5 ttl=49 time=139 ms

64 bytes from {edited for privacy} icmp_seq=6 ttl=49 time=138 ms

64 bytes from {edited for privacy}: icmp_seq=7 ttl=49 time=138 ms

64 bytes from {edited for privacy}: icmp_seq=8 ttl=49 time=138 ms

64 bytes from {edited for privacy}: icmp_seq=9 ttl=49 time=140 ms

64 bytes from {edited for privacy}: icmp_seq=10 ttl=49 time=222 ms

--- {edited for privacy} ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9087ms rtt min/avg/max/mdev = 137.773/147.354/222.182/24.962 ms


0 Likes