Child Item

Site Totals

61223 Questions Answered 267 Categories

Dry Loop DSL slow-down during prime time, Long Beach, CA

Hi, about 2 months ago, I switched my Verizon DSL (7Mbps) + Residential Phone to just Verizon Dry Loop DSL (15Mbps) and canceled my residential phone.

And thats when the nightmare begin.

WIth my old DSL, for over 2 years i almost never had any issue, at any time i decided to run speedtest, i always got 7Mbps or close to it.

With this dryloop DSL (15Mbps) I never get speed higher than 9Mbps and during primetime 7pm - 10pm PST, the speed will drop to about 1.5 - 2.5 Mpbs. After 10PM usually the speed will climb back again to 7Mpbs to 9Mpbs.

I tried to call the Verizon tech support and they tried to blame my equipment, even though i said that the speed is fine outside primetime.

I just create an email to Verizon support and hope maybe they can help better.

Any suggestion on what i should do next?

Do you need some statistic from my DSL modem?

(My DSL modem is TP-Link TD-8616, that support ADSL2+)

Comments

lgusti

I talked to Verizon Tech Support yesterday,

They said that my line was not qualified for 15Mpbs and that's why I'm seeing network slowdown during primetime.

They told me to downgrade the line to 7Mbps and I should not see those slowdown during primetime anymore.

Outside primetime, I can get consistent speed of 7-9Mbps. (Never over 10Mbps).

My main concern is after the downgrade, I will still see the network congestion during primetime and end up worse than before.

Suggestion guys?

Thanks

smith6612

Who knows to be honest. Slower speeds might still wind you up with congested equipment. That's not really a fix at all. So, leave the line at 15Mbps for now and let's see if we can get 15Mbps out of it day and night.

Just to be sure to see if the support call was truthful in what speed your line can do, get some Transceiver Statistics for us. If you don't know how to get this information, tell us which modem you have and we'll give you some instructions for getting the numbers. In addition, go to http://lg.dreamhost.com/ and copy/paste a traceroute from that website to this forum. Just need that information to get an idea of where your connection is going through. No need for last hop information so you do not need to check the "ICMP" box as if everything is fine up to the edge router, the problem lays not at the backbone but within the Internal network in the CO.

A speed test during the morning/afternoon and during the evening hours would be appreciated as well.

lgusti

Thanks for trying to help me Smith,

This is the transceiver info that i got from my DSL modem TP-Link TD-8616 at 6:45pm.

Speedtest show ping of 25ms, 7.94Mbps download, and 0.85Mbps upload.

Traceroute info as follow

traceroute to vrzn.lithium.com (208.74.204.208), 30 hops max, 46 byte packets

1 ip-66-33-193-1 (66.33.193.1) 182.894 ms 3.631 ms 1.384 ms

2 ip-66-33-201-113 (66.33.201.113) 0.614 ms 0.643 ms 0.267 ms

3 vl204.mag01.lax01.atlas.cogentco.com (38.122.20.217) 0.534 ms 0.394 ms 0.505 ms

4 te0-0-0-6.ccr22.lax01.atlas.cogentco.com (154.54.28.145) 0.517 ms te0-0-0-6.ccr21.lax01.atlas.cogentco.com (154.54.28.141) 0.472 ms te0-0-0-6.ccr22.lax01.atlas.cogentco.com (154.54.28.145) 0.970 ms

5 te3-1.mpd01.sjc01.atlas.cogentco.com (154.54.5.185) 12.794 ms te4-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.69) 13.124 ms te3-1.mpd01.sjc01.atlas.cogentco.com (154.54.5.185) 13.128 ms

6 te3-1.mpd01.sjc06.atlas.cogentco.com (154.54.7.106) 60.504 ms te4-2.mpd01.sjc06.atlas.cogentco.com (154.54.6.150) 14.189 ms 14.103 ms

7 lithium-tech.demarc.cogentco.com (38.104.134.2) 15.510 ms 16.907 ms 17.754 ms 8 vrzn.lithium.com (208.74.204.208) 13.521 ms 13.535 ms 13.537 ms

I'll try to post another test around 9pm PST when usually i see the slowdown.

Thanks for your help.

lgusti

Just as expected, the internet just slowed down at 7:45pm

Speedtest show 26Ms ping, 1.47Mbps download, and 0.85Mbps upload

Here is the transceiver stat

Here is the traceroute info

traceroute to vrzn.lithium.com (208.74.204.208), 30 hops max, 46 byte packets

1 ip-66-33-193-1 (66.33.193.1) 0.718 ms 98.540 ms 92.724 ms

2 ip-66-33-201-113 (66.33.201.113) 0.882 ms 1.355 ms 0.649 ms

3 vl204.mag01.lax01.atlas.cogentco.com (38.122.20.217) 0.823 ms 0.338 ms 0.317 ms

4 te0-0-0-6.ccr21.lax01.atlas.cogentco.com (154.54.28.141) 0.429 ms te0-0-0-6.ccr22.lax01.atlas.cogentco.com (154.54.28.145) 0.558 ms te0-0-0-6.ccr21.lax01.atlas.cogentco.com (154.54.28.141) 0.802 ms

5 te4-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.69) 12.792 ms te3-1.mpd01.sjc01.atlas.cogentco.com (154.54.5.185) 12.765 ms te4-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.69) 12.754 ms

6 te4-2.mpd01.sjc06.atlas.cogentco.com (154.54.6.150) 13.223 ms te3-1.mpd01.sjc06.atlas.cogentco.com (154.54.7.106) 13.334 ms 13.288 ms

7 lithium-tech.demarc.cogentco.com (38.104.134.2) 16.447 ms 16.149 ms 16.106 ms 8 vrzn.lithium.com (208.74.204.208) 14.167 ms 13.734 ms 18.148 ms

I do notice that I got a different IP address that the one i got earlier.

Child Item