Slower than Dialup! Please help

[Egz1]

My connection has gotten really terrible lately. Speedtests from a variety of sites show between 0.08 and 0.5 Mbps on a 1.5-3Mbps package. Modem and router is a Netgear DGN2200. Computer is a fresh Windows 7 install. Computer is hardwired to the Netgear, and wireless is turned off for testing. I even went out side, ran a line to the test port, disconnected all the house lines, and the speed didn't increase any.

This is the closest I can find to the transceiver stats (while plugged into the test port at the NID):

System Up Time 00:08:44
Port 	Status 	TxPkts 	RxPkts 	Collisions 	Tx B/s 	Rx B/s 	Up Time
WAN 	pppoe 	2027 	1925 	0 	7197 	10258 	00:02:00
LAN1 	10M/100M 	4503 	5777 	0 	4780 	2922 	00:08:44
LAN2 	Link Down 	--
LAN3 	Link Down 	--
LAN4 	Link Down 	--
WLAN 	145M 	0 	0 	0 	0 	0 	00:08:19

ADSL Link 	Downstream 	Upstream
Connection Speed 	3360 kbps 	832 kbps
Line Attenuation 	59.0 db 	27.0 db
Noise Margin 	13.3 db 	10.0 db

Verizon phone support said that the signal is clear and fast, so I'm banging my head here as to why this is so slow suddenly.

[smith6612]

I'm curious to know why exactly you're showing a good amount of packet collisions occurring during a 5-8 minute span. That may be related to the slow speeds you are having. For your line's length, your statistics look pretty good.

Run an NDT Test from here: http://measurementlab.net/run-ndt (Java is required!).

Post up the results fron the Summary, Details, and Advanced section of the page.

[Egz1]

Thanks, I'll give that a try when I get home from work.

What is odd is over the course of 6pm to 10pm, the speeds were all between 0.08 and 0.5 Mbps.  Woke up this morning, with no change in anything, and test results were showing 2Mbps.

Is it possible that their trunk is over-saturated somehow?

[smith6612]

That's always a possibility, and seems to have become rather common lately with the DSL service in some areas.

[Egz1]

Well last night seemed okay for the most part, and tonight, its gone back down again.

From Run NDT: 

Upload speed

0.56 mb/s

Download speed

0.57 mb/s

Your system: Windows 7 version 6.1
Java version: 1.6.0_23 (x86)

TCP receive window: 66792 current, 66792 maximum
0.011744966 packets lost during test
Round trip time: 82 msec (minimum), 310 msec (maximum), 133.61 msec (average)
Jitter: 228 msec
0 seconds spend waiting following a timeout
TCP time-out counter: 392
88 selective acknowledgement packets received

No duplex mismatch condition was detected.
The test did not detect a cable fault.
Network congestion may be limiting the connection.
No network addess translation appliance was detected.

0.9915% of the time was not spent in a receiver limited or sender limited state.
0.0% of the time the connection is limited by the client machine's receive buffer.
Optimal receive buffer: 68395008 bytes
Bottleneck link: Cable/DSL modem
0 duplicate ACKs set

WEB100 Kernel Variables: Client: localhost/127.0.0.1 CurMSS: 1452 X_Rcvbuf: 87380 X_Sndbuf: 89664 AckPktsIn: 326 AckPktsOut: 0 BytesRetrans: 47916 CongAvoid: 181 CongestionOverCount: 0 CongestionSignals: 7 CountRTT: 233 CurCwnd: 8712 CurRTO: 392 CurRwinRcvd: 66792 CurRwinSent: 5888 CurSsthresh: 5808 DSACKDups: 0 DataBytesIn: 0 DataBytesOut: 876684 DataPktsIn: 0 DataPktsOut: 596 DupAcksIn: 60 ECNEnabled: 0 FastRetran: 7 MaxCwnd: 40656 MaxMSS: 1452 MaxRTO: 425 MaxRTT: 310 MaxRwinRcvd: 66792 MaxRwinSent: 5888 MaxSsthresh: 20328 MinMSS: 1452 MinRTO: 288 MinRTT: 82 MinRwinRcvd: 66792 MinRwinSent: 5840 NagleEnabled: 1 OtherReductions: 0 PktsIn: 326 PktsOut: 596 PktsRetrans: 33 RcvWinScale: 7 SACKEnabled: 3 SACKsRcvd: 88 SendStall: 0 SlowStart: 50 SampleRTT: 162 SmoothedRTT: 171 SndWinScale: 2 SndLimTimeRwin: 0 SndLimTimeCwnd: 10386597 SndLimTimeSender: 88912 SndLimTransRwin: 0 SndLimTransCwnd: 6 SndLimTransSender: 6 SndLimBytesRwin: 0 SndLimBytesCwnd: 850816 SndLimBytesSender: 25868 SubsequentTimeouts: 0 SumRTT: 31132 Timeouts: 0 TimestampsEnabled: 0 WinScaleRcvd: 2 WinScaleSent: 7 DupAcksOut: 0 StartTimeUsec: 839804 Duration: 10479889 c2sData: 2 c2sAck: 2 s2cData: 8 s2cAck: 3 half_duplex: 0 link: 100 congestion: 1 bad_cable: 0 mismatch: 0 spd: 0.67 bw: 0.77 loss: 0.011744966 avgrtt: 133.61 waitsec: 0.00 timesec: 10.00 order: 0.1840 rwintime: 0.0000 sendtime: 0.0085 cwndtime: 0.9915 rwin: 0.5096 swin: 0.6841 cwin: 0.3102 rttsec: 0.133614 Sndbuf: 89664 aspd: 0.00000 CWND-Limited: 177.95 minCWNDpeak: 1452 maxCWNDpeak: 40656 CWNDpeaks: 7 The theoretical network limit is 0.77 Mbps The NDT server has a 43.0 KByte buffer which limits the throughput to 5.11 Mbps Your PC/Workstation has a 65.0 KByte buffer which limits the throughput to 3.81 Mbps The network based flow control limits the throughput to 2.32 Mbps Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is 'OC-48', Server Acks report link is 'Ethernet' 

I'm guessing its Verizon's pipe.

[smith6612 · Accepted solution]

That would be a correct guess. That jitter value is way too high, and even though the NDT test isn't showing any cable faults/packet collisions, nor is it seeing any packet loss really, it is a congestion issue on Verizon's end. This is espeically trus since, as you've pointed out, it only occurs during the night time hours. What you can do to get this problem solved, is to visit the Verizon Direct forum over at DSLReports.com and ask them to move you to a less congested circuit at the CO, if possible. Additionally, if a Verizon Employee posts in this thread with some contact information, they can also help you solve this problem.

[Egz1]

Well Verizon made some changes at the CO, and it seemed to help so far.

[smith6612]

Glad to hear. If you still need help or wish to ask us anything else, feel free 🙂