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

[lgusti]

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+)

[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.

[smith6612]

OK.

Did the traceroute above come from a Website? It looks like you ran it from the looking glass server to the forum. Try tracing to your IP address (it will not appear in the trace as routers do not reply back to UDP pings). Visiting the link I provided for traceroutes automatically fills in your IP address upon loading. Just press Trace.

Your line statistics aren't looking the greatest. The line is probably dropping out but this is a separate issue. If you don't mind, I would like to try to get that issue resolved as well. I'd like to do that before we get anyone in Verizon involved with checking the network for night time issues, as they'll try to do that first typically.

Would you happen to know the location of your NID? If not, look for your NID near your Electrical Service. It can be a modernized Grey box, it could be an older carbon block protector, or it could be a box located within reach on an extension pole located on your property if your home is a distance away from the street. I'd like you to take your modem to the NID when you are able to and connect the modem up and obtain the Line Statistics from the NID. Checking to see if there is a way to improve the physical signal level while we're at it to at least get 10Mbps/1Mbps.

Take a look at this FAQ for info: http://www.dslreports.com/faq/1317

[lgusti]

Smith,

Yeah sorry i guess i run the tracert wrong.

I just run a speedtest, and as usual, the speed is okay outside primte time at night.

I got Ping 26ms, Download 8.1Mbps, Upload 0.85 Mbps

(it's only during 7pm - 10pm PST that my speed crawl to 1.5)

I know the location of my NID, but i dont have access to it, since i live in the townhome. The NID is quite big and it looks new though since my complex was built on 2008. 

Below is the updated tracert

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

1 ip-66-33-193-1 (66.33.193.1) 0.562 ms 0.583 ms 1.280 ms

2 rampart-0.hq.newdream.net (66.33.201.2) 0.851 ms 1.047 ms 1.552 ms

3 ip-66-33-201-222 (66.33.201.222) 0.912 ms 0.934 ms 0.851 ms

4 vl1109.mag01.lax04.atlas.cogentco.com (38.104.210.173) 1.374 ms 1.331 ms 1.303 ms

5 te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165) 0.934 ms te8-3.ccr01.lax04.atlas.cogentco.com (154.54.83.161) 0.914 ms te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165) 0.982 ms

6 te0-2-0-7.mpd22.lax01.atlas.cogentco.com (154.54.2.237) 0.977 ms te0-3-0-7.ccr22.lax01.atlas.cogentco.com (154.54.43.249) 1.141 ms 1.537 ms

7 te9-1.ccr02.lax05.atlas.cogentco.com (154.54.44.130) 1.221 ms te4-8.ccr02.lax05.atlas.cogentco.com (154.54.30.194) 2.314 ms te7-8.ccr02.lax05.atlas.cogentco.com (154.54.30.198) 1.013 ms

8 uunet.lax05.atlas.cogentco.com (154.54.13.86) 1.074 ms 1.421 ms 1.020 ms

9 0.ge-1-2-0.LAX01-BB-RTR2.verizon-gni.net (152.63.112.6) 107.752 ms 4.477 ms 1.193 ms

10 P1-0-0-0.LSANCA-LCR-22.verizon-gni.net (130.81.199.41) 3.354 ms 3.064 ms 3.003 ms

11 G2-0.LSANCA-DSL-72.verizon-gni.net (130.81.195.79) 5.355 ms 5.049 ms 6.069 ms

12 * * *

And so on until 30

[smith6612]

That looks better. I'm not seeing anything wrong in the trace at least up to the Verizon edge router. If you could run the same trace again (if not already done) the same way to your connection during a horrible time that would be appreciated. This allows is to see if the problem is at the router or if it's in the network past that point.

[lgusti]

Smith, sorry for the delay, 
I just run the tracert again just now, 10:14pm PST.

Speedtest show ping 26ms, 1.61Mbps down, and 0.85Mbps Up 

traceroute to pool-XXX My IP ADDRESS.lsanca.dsl-w.verizon.net (XXXXX MY IP ADDRESS), 30 hops max, 46 byte packets

1 ip-66-33-193-1 (66.33.193.1) 51.656 ms 9.655 ms 4.468 ms

2 rampart-0.hq.newdream.net (66.33.201.2) 0.816 ms 1.698 ms 1.192 ms

3 ip-66-33-201-222 (66.33.201.222) 0.968 ms 1.183 ms 1.050 ms

4 vl1109.mag01.lax04.atlas.cogentco.com (38.104.210.173) 1.576 ms 1.627 ms 1.316 ms

5 te8-3.ccr02.lax04.atlas.cogentco.com (154.54.83.165) 1.453 ms * 0.891 ms

6 te0-2-0-7.mpd22.lax01.atlas.cogentco.com (154.54.2.237) 1.035 ms te0-3-0-7.ccr22.lax01.atlas.cogentco.com (154.54.43.249) 1.109 ms 1.376 ms

7 te9-1.ccr02.lax05.atlas.cogentco.com (154.54.44.130) 136.824 ms te4-8.ccr02.lax05.atlas.cogentco.com (154.54.30.194) 321.294 ms te7-8.ccr02.lax05.atlas.cogentco.com (154.54.30.198) 197.510 ms

8 uunet.lax05.atlas.cogentco.com (154.54.13.86) 1.110 ms 1.217 ms 1.731 ms

9 0.ge-1-2-0.LAX01-BB-RTR2.verizon-gni.net (152.63.112.6) 1.215 ms 1.137 ms 1.143 ms

10 P0-8-0-0.LSANCA-LCR-22.verizon-gni.net (130.81.29.127) 3.823 ms 3.477 ms 3.329 ms

11 G2-0.LSANCA-DSL-72.verizon-gni.net (130.81.195.79) 9.012 ms 5.115 ms 5.735 ms

12 * * *

13 * * *

14 * * *

[smith6612]

Well, not seeing anything still that stands out in that trace besides a jump in the latency to the edge router at first. That may be from just internet noise as we call it or a sudden spike in load on the hop. Either way this problem does sound more local. Let me get someone in Verizon to take a look at the line for you. Hold up.