Slow DSL network speed but modem says 2.994 Mb connect speed
RonT2
Enthusiast - Level 2

I have a Westell 7500 modem and I subscribe at 3 Mb speed. Normally I get 3.36 Mb / 0.83 Mb down and up but in the last three weeks when I run a speed test to speedtest.net or speakeasy.net I get only 0.29 Mb / 0.5 Mb down and up. Yes up is faster than down. I have had 3 VZ internet techs and 2 VZ phone techs out and the last one showed my 192.168.1.1 page 2.9 Mb / .64 Mb speeds and this matched their test set measured speeds. I am on a 14K foot loop and normally to speedtest.net I got 2.7 Mb / 0.76 Mb. The tech and I have used both my wireless connected PC and the tech’s Ethernet connected laptop and both show 2.9 Mb / .64 Mb and to speakeasy.net we got around 0.3 Mb down and 0.5 Mb up. The Westell modem and the homerun filter have also been replaced. The onsite VZ tech refers this trouble back to the CO end but they now want to send a sixth VZ tech out and say the problem is with my loop but both my modem and the VZ internet tech’s test set say I am connected at 2.994 MB down and 0.64 Mb up. I have used the VZ Executive Customer Service escalation process but they have not been much help in getting the CO end on board to resolve this issue. They started talking about downgrading me 1.5 Mb service but  0.29 Mb / 0.5 Mb down and up speed test but the modem and test set read 2.9 Mb / .64 Mb how could that help. Any help would be appreciated. It is even difficult to log on to this forum.

Re: Slow DSL network speed but modem says 2.994 Mb connect speed
RonT2
Enthusiast - Level 2

Let me add my Westell 7500 Transceiver Statistics:

Transceiver Statistics

Transceiver Revision A2pB020b3.d20h

Vendor ID Code 4D54

Line Mode ADSL_G.dmt

Data Path INTERLEAVED

 Transceiver Information                           Down Stream Path                                             Up Stream Path

DSL Speed (Kbits/Sec)                                          2944                                                                     640

Margin (dB)                                                               24.8                                                                      18.0

Line Attenuation (dB)                                              51.0                                                                      30.0

Transmit Power (dBm)                                           19.4                                                                      11.9

Re: Slow DSL network speed but modem says 2.994 Mb connect speed
jmw1950
Specialist - Level 2

Your transceiver statistics are only a measure of the link between you and the Central Office. In effect the on and off ramp to the Internet. That  says little or nothing about congestion, or other issues that may be upstream  of the Central Office  , or downstream in your PC.

My suggestion is to run a speed test with analysis capability such as ndt.anl.gov . In particular look at the statistics and 'more details' to see if the issue is congestion, configuration (buffer configuration)or perhaps a combination of both.

0 Likes
Re: Slow DSL network speed but modem says 2.994 Mb connect speed
RonT2
Enthusiast - Level 2

Thanks Matheww. I ran the test to ndt.anl.gov in Illinois and the results are shown below. Also monitored my CPU and wireless activity and saw no issues. Would appreciate any suggestions. The VZ office end keeps wanting to downgrade me to 1.5 MB.  

** Starting test 1 of 1 **

Connected to: web100.rit.edu  --  Using IPv4 address

Another client is currently being served, your test will begin within 135 seconds

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

checking for firewalls . . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client-to-server [C2S]) . . . . . 244.0kb/s

running 10s inbound test (server-to-client [S2C]) . . . . . . 105.15kb/s

Your PC is connected to a Cable/DSL modem

 [S2C]: Packet queuing detected

THIS TEST WAS DONE WITH FIREWALL OFF

MONITORING WINDOWS TASK MANAGER/ NETWORKING SHOWED THE CPU ACTIVITY UNDER 5% AND THE WIRELESS NETWORK AT LESS THAT 1%

DETAILED STATS

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

checking for firewalls . . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client-to-server [C2S]) . . . . . 244.0kb/s

running 10s inbound test (server-to-client [S2C]) . . . . . . 105.15kb/s

            ------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_22

            ------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 85.3 msec; the Packet size = 1452 Bytes; and

There were 27 packets retransmitted, 44 duplicate acks received, and 50 SACK blocks received

The connection stalled 6 times due to packet loss

The connection was idle 1.7 seconds (-0.07%) of the time

S2C throughput test: Packet queuing detected: 99.41%

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

Web100 reports TCP negotiated the optional Performance Settings to:

RFC 2018 Selective Acknowledgment: ON

RFC 896 Nagle Algorithm: ON

RFC 3168 Explicit Congestion Notification: OFF

RFC 1323 Time Stamping: OFF

RFC 1323 Window Scaling: OFF

Server 'web100.rit.edu' is not behind a firewall. [Connection to the ephemeral port was successful]

Client is probably behind a firewall. [Connection to the ephemeral port failed]

Information: Network Middlebox is modifying MSS variable

Server IP addresses are preserved End-to-End

Information: Network Address Translation (NAT) box is modifying the Client's IP address

            Server says [70.21.159.136] but Client says [192.168.1.36]

TEST STATS

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

checking for firewalls . . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client-to-server [C2S]) . . . . . 244.0kb/s

running 10s inbound test (server-to-client [S2C]) . . . . . . 105.15kb/s

            ------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_22

            ------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 85.3 msec; the Packet size = 1452 Bytes; and

There were 27 packets retransmitted, 44 duplicate acks received, and 50 SACK blocks received

The connection stalled 6 times due to packet loss

The connection was idle 1.7 seconds (-0.07%) of the time

S2C throughput test: Packet queuing detected: 99.41%

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

Web100 reports TCP negotiated the optional Performance Settings to:

RFC 2018 Selective Acknowledgment: ON

RFC 896 Nagle Algorithm: ON

RFC 3168 Explicit Congestion Notification: OFF

RFC 1323 Time Stamping: OFF

RFC 1323 Window Scaling: OFF

Server 'web100.rit.edu' is not behind a firewall. [Connection to the ephemeral port was successful]

Client is probably behind a firewall. [Connection to the ephemeral port failed]

Information: Network Middlebox is modifying MSS variable

Server IP addresses are preserved End-to-End

Information: Network Address Translation (NAT) box is modifying the Client's IP address

            Server says [70.21.xxx.xxx] but Client says [192.168.1.36]

Re: Slow DSL network speed but modem says 2.994 Mb connect speed
smith6612
Community Leader
Community Leader

For a 14,000 foot line your statistics are pretty good. The margin suggests the downstream can hold a bit more than the 3Mbps rates. Upstream isn't looking as good, but it is stable. For now, I would stop giving Verizon a call about the slow speeds before they actually do turn your speeds down. Going from a line that should sync at 3360kbps/640kbps to one locked at 1792kbps/448kbps isn't very nice at all. Once Verizon turns down the speed, it becomes difficult to get it back since 1.5Mbps would still fall under the same package. What is interesting to note though is your line isn't synced at 3360 despite the good margins. It's possible that Verizon's Optimization system set that sync speed. If so, that should improve the next time the system runs again.

The issue you're having isn't that uncommon at all. Are these slow speeds you're having occurring during the evening/night hours or are they consistently slow like that even in the early morning?

Re: Slow DSL network speed but modem says 2.994 Mb connect speed
RonT2
Enthusiast - Level 2

 Smith Thanks for the comments. I was getting 3.36 Mb / 0.830 Mb and about 2 weeks ago I started randomly losing the Internet LED. It would drop for 15 seconds to minutes and the internet LED would flash rapidly and then go solid and sync. I also would randomly hear the hash noise from the modem and if it lost sync I could actually hear tones on the phone. The VZ phone tech found some “light” short and replaced the pair between the NID and the pedestal. The phone did not have any noise for 5 days and then the same problem started again. The next VZ internet tech found 30 VDC bridged on the line and swapped in a new pair back to the switch. It was during this process that I noticed speedtest speeds were dropping from 0.2 to 0.5 Mb downstream and many times even fasted upstream; from >0.1 to 0.5 Mb. The tech test set now consistently reads 29.994 / 0.640 Mb and matches my 192.168.1.1Main page. They initially blamed the problem on my slow PC or wireless network. The fifth tech visit used an Ethernet connected with his laptop he saw the same speed. The tech tried to blame the speedtest sites but even he had trouble justifying that. The NSC (office end) keeps saying if the test set and my gateway page show 29.994 / 0.640 Mb the problem is on my end and can’t be their end of the network. A VZ internet tech is coming tomorrow and the VZ escalations and NSC groups want to do a “Co-Op’ test between the onsite tech and the NSC. In the past the techs did not know what this test was?     

UPDATE: Slow DSL network speed but modem says 2.994 Mb connect speed
RonT2
Enthusiast - Level 2

UPDATE: An internet tech was at my home today and basically did a Co-Op test with the MCO. The result confirmed that the tech’s test set, his internet laptop, several modems and the MCO all see 2.994 Mb down and 0.64 Mb up. When testing to speakeasy.net and speedtest.net the onsite tech and MCO tech both saw my throughput as less than 0.5 Mb down on all three modems. The MCO tech even upgraded me temporarily to 5.886 Mb down and 0.83 Mb up all modems synced successfully and again both saw my speed as less than 0.5 Mb up and 0.7 Mb down. The tech using his laptop HSI test saw an error code on my new Westell 7500 modem but keep in mind none of the three modems saw more than 0.5 Mb to the speed test sites. I am supposed to receive a new Westell modem. In the end the MCO tech said he had to go but my problem remains.    

Re: UPDATE: Slow DSL network speed but modem says 2.994 Mb connect speed
jmw1950
Specialist - Level 2

Don't mean to be the profit of doom, but the information from the run of ndt.anl.gov suggests that your problems are NOT in the local DSL loop. They are in fact all upstream from the DSL loop. Consequently you can  re-provision, change modems and do anything you want to the local loop, and it won't make much difference because the local DSL loop  isn't the problem.

Read what the test is telling you:

The connection stalled 6 times due to packet loss

The connection was idle 1.7 seconds (-0.07%) of the time

S2C throughput test: Packet queuing detected: 99.41%

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch.

This says there is serious network congestiong upstream from your DSL connection. You don't get packet queuing on the local loop, and it is unlikely that you get packet loss on the local loop either.

This isn't an issue for a Verizon Tech to deal with at your home, it is an issue for Verizon Network guy to find and fix upstream from the DSL loop in Central Office or elsewhere upstream in the Verizon network.

Re: UPDATE: Slow DSL network speed but modem says 2.994 Mb connect speed
RonT2
Enthusiast - Level 2

Mathew Thank you for your quick response. Even the onsite tech said everything is fine on my loop to the DSLAM. I am dealing through the VZ Escalation Hotline, bypasses India, but wish I had a way to contact the MSO directly. When the onsite called in they said they were out of time and had to go. This is very frustrating. Thanks again!  

Re: UPDATE: Slow DSL network speed but modem says 2.994 Mb connect speed
smith6612
Community Leader
Community Leader

That's interesting to hear. MCO does have the ability to search for congestion between the DSLAM into the Core network, and they also have the ability to detect failing equipment. Whatever the issue is, it could be either QoS related (as in, network-related throttles to keep lines provisioned to set speeds, which is done by Verizon at the edge router) or it could in fact be the case of congestion or failing equipment. I would place bets on Failing/Failed equipment considering the amount of packet loss being detected by the NDT test and also considering the issues you were having with PPPoE connectivity just before this slow speed issue began.

I do have a contact to someone who works in Verizon MCO, or at least has direct contact with them, though I'm not sure that they actually want that info being posted. If you can't get any progress into this issue in another week or two by working with Verizon either on the phone or via these forums, send me a PM and I'll tell you how to reach him. He can get down to the bottom of what the problem is. As to getting it fixed onced he pinpoints the problem is another thing, as he can issue repair requests but there's no guarantee that it would be completed. Lots of chain of command to go through.

Oh, and while you're waiting to get the problem solved, see if you can find others near you that are seeing the same issues. The more people seeing issues, the faster the problem will be resolved.