very inconsistant and horrible cable speeds [Archive] - SpeedGuide.net Broadband Community

View Full Version : very inconsistant and horrible cable speeds


UltimateHigh1
03-26-07, 06:02 PM
ive been experiencing inconsisant cable speeds for about 1-2 weeks. The speeds tend to be really slow during the day although sometimes increasing. Later at night/early morning i tend to get a speed increase sometimes but its still inconsistant. my projected speeds are 4mb/1b.. I never get close to 4mb these days, rarely touching 3mbs.. My ISP told me its not realistic to expect 4mb speeds but its nonsense to only be getting like 2.5 on a good day which i havent had in awhile. I seem to be experience alot of packet loss and i dont see any electronic devices near my modem. My tracert test seems to really show me that something is wrong. My modem is connected to 2 computers as well

test results:

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 553.20Kb/s
running 10s inbound test (server to client) . . . . . . 504.79kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 150.24 msec; the Packet size = 1460 Bytes; and
There were 5 packets retransmitted, 38 duplicate acks received, and 18 SACK blocks received
The connection stalled 3 times due to packet loss
The connection was idle 1.11 seconds (11.10%) of the time
This connection is network limited 99.97% of the time.
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: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End


« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.26.2007 18:25
IP address: 64.89.xxx.xxx

TCP options string: 020405b40103030101010402
MSS: 1460
MTU: 1500
TCP Window: 128480 (multiple of MSS)
RWIN Scaling: 1
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 5139kbps (642KBytes/s)
BDP limit (500ms): 2056kbps (257KBytes/s)
MTU Discovery: ON
TTL: 41
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)


Power level:


Lock Status Operational
Modulation 64QAM
Channel ID 0
Provisioned Rate 4096 kbps
Symbol Rate 5056.941 Ksym/sec
Downstream Power 10.0 dBmV
SNR 41.5 dB


Upstream Channel


Lock Status Operational
Modulation QPSK
Channel ID 2
Provisioned Rate 1024 kbps
Symbol Rate 2560 Ksym/sec
Upstream Power 48.0 dBmV

trogers
03-26-07, 08:42 PM
test results:

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 553.20Kb/s
running 10s inbound test (server to client) . . . . . . 504.79kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 150.24 msec; the Packet size = 1460 Bytes; and
There were 5 packets retransmitted, 38 duplicate acks received, and 18 SACK blocks received
The connection stalled 3 times due to packet loss
The connection was idle 1.11 seconds (11.10%) of the time
This connection is network limited 99.97% of the time.
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: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End


« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.26.2007 18:25
IP address: 64.89.xxx.xxx

TCP options string: 020405b40103030101010402
MSS: 1460
MTU: 1500
TCP Window: 128480 (multiple of MSS)
RWIN Scaling: 1
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 5139kbps (642KBytes/s)
BDP limit (500ms): 2056kbps (257KBytes/s)
MTU Discovery: ON
TTL: 41
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)


Power level:


Lock Status Operational
Modulation 64QAM
Channel ID 0
Provisioned Rate 4096 kbps
Symbol Rate 5056.941 Ksym/sec
Downstream Power 10.0 dBmV
SNR 41.5 dB


Upstream Channel


Lock Status Operational
Modulation QPSK
Channel ID 2
Provisioned Rate 1024 kbps
Symbol Rate 2560 Ksym/sec
Upstream Power 48.0 dBmV

Have you scan your comp for possible spyware/malware?

The test reported excessive packet losses. Lowering your RWIN to 64240 may help your speed a little.

The downstream power level of your cable modem is a little high. Recommended values are -8 to +8 dBmV.

How long have you been using this modem?

Do a tracert to www.yahoo.com and post.

UltimateHigh1
03-26-07, 10:12 PM
Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 15 ms 8 ms 8 ms 10.0.99.1
2 45 ms 24 ms 11 ms 66.186.180.209
3 22 ms 11 ms 18 ms 66.186.173.37
4 16 ms 15 ms 78 ms pwn-pi-mont-core.pwless.net [66.186.173.43]
5 41 ms 19 ms 92 ms 64.89.247.242
6 43 ms * 69 ms 64.89.249.98
7 23 ms * 33 ms 198.164.27.13
8 42 ms 30 ms 41 ms stjhnbsu22w-ge-14-0.aliant.net [142.166.211.97

9 56 ms * 62 ms so-8-1.car2.boston1.level3.net [4.79.2.81]
10 76 ms * 63 ms ae-5-5.ebr1.newyork1.level3.net [4.69.132.250]
11 102 ms 61 ms 69 ms ae-3.ebr1.washington1.level3.net [4.69.132.89]
12 * 87 ms 93 ms ae-11-55.car1.washington1.level3.net [4.68.121
46]
13 59 ms 113 ms 138 ms 4.79.228.2
14 75 ms 78 ms 55 ms ge-2-1-0-p140.msr1.re1.yahoo.com [216.115.108.
]
15 * 58 ms 68 ms ge-1-41.bas-a1.re3.yahoo.com [66.196.112.193]
16 * 60 ms 60 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

Trace complete.


I think i've had this modem for probably a year.

trogers
03-26-07, 10:17 PM
Tracing route to www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 15 ms 8 ms 8 ms 10.0.99.1
2 45 ms 24 ms 11 ms 66.186.xxx.xxx
3 22 ms 11 ms 18 ms 66.186.173.37
4 16 ms 15 ms 78 ms pwn-pi-mont-core.pwless.net [66.186.173.43]
5 41 ms 19 ms 92 ms 64.89.247.242
6 43 ms * 69 ms 64.89.249.98
7 23 ms * 33 ms 198.164.27.13
8 42 ms 30 ms 41 ms stjhnbsu22w-ge-14-0.aliant.net [142.166.211.97

9 56 ms * 62 ms so-8-1.car2.boston1.level3.net [4.79.2.81]
10 76 ms * 63 ms ae-5-5.ebr1.newyork1.level3.net [4.69.132.250]
11 102 ms 61 ms 69 ms ae-3.ebr1.washington1.level3.net [4.69.132.89]
12 * 87 ms 93 ms ae-11-55.car1.washington1.level3.net [4.68.121
46]
13 59 ms 113 ms 138 ms 4.79.228.2
14 75 ms 78 ms 55 ms ge-2-1-0-p140.msr1.re1.yahoo.com [216.115.108.
]
15 * 58 ms 68 ms ge-1-41.bas-a1.re3.yahoo.com [66.196.112.193]
16 * 60 ms 60 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

Trace complete.


I think i've had this modem for probably a year.

Hop 1 (your modem) shows irregular ping times. Make sure your modem is placed a few feet from any other electrical devices to avoid electromagnetic interference. Power off your modem for a few minutes and then reboot it. Do another tracert to see if you can get all its 3 ping times to be equal.

You may want to consider getting a router to improve your security.