Hello, I am having an issue over the last 2 weeks with packet loss and low upstream bandwidth.
My vitals: Arris SB6183 modem, Netgear R8000 router, 10/100 tier, signal levels below, 1 splitter installed by Cox tech to increase upstream power (tested with and without it), setup is direct line from ground block to modem, various speed tests performed indicating 3-5 up and 60+ down, ping, pathping, and pingtest.net used all indicating packet loss, no tweaks, wired only, bypassed router with no effect on lost packets bandwidth, only internet service.
Had a tech out last night and i met him at the ground block with a laptop (wired) and the modem so we could eliminate inside wiring right off the bat. i performed speed tests, ping tests and ping path from there and we saw packet loss and low bandwidth. he checked the drop and said he was receiving 10db from my 20db drop. He said he would put in a ticket to increase to a 28 drop but if you could explain to me how that will increase db up from 10 please let me know. I really want to make sure this is escalated so it is corrected.
With splitter:
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 97 801000000 Hz -2.4 dBmV 38.0 dB 0 0
2 Locked QAM256 98 807000000 Hz -2.8 dBmV 38.1 dB 0 0
3 Locked QAM256 99 813000000 Hz -2.1 dBmV 38.5 dB 0 0
4 Locked QAM256 100 819000000 Hz -3.1 dBmV 37.9 dB 0 0
5 Locked QAM256 101 825000000 Hz -3.2 dBmV 37.8 dB 0 0
6 Locked QAM256 102 831000000 Hz -2.0 dBmV 38.5 dB 0 0
7 Locked QAM256 103 837000000 Hz -3.1 dBmV 37.9 dB 0 0
8 Locked QAM256 104 843000000 Hz -3.4 dBmV 37.3 dB 0 0
9 Locked QAM256 105 849000000 Hz -2.0 dBmV 38.5 dB 0 0
10 Locked QAM256 106 855000000 Hz -3.3 dBmV 37.5 dB 0 0
11 Locked QAM256 107 861000000 Hz -3.5 dBmV 37.5 dB 0 0
12 Locked QAM256 108 867000000 Hz -2.6 dBmV 38.0 dB 0 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 23696000 Hz 39.0 dBmV
2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18896000 Hz 37.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 30704000 Hz 39.0 dBmV
4 Locked TDMA and ATDMA 4 2560 Ksym/sec 35600000 Hz 39.0 dBmV
Current System Time: Thu Aug 13 08:57:29 2015
With out splitter:
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 97 801000000 Hz 2.1 dBmV 38.2 dB 0 0
2 Locked QAM256 98 807000000 Hz 1.8 dBmV 38.4 dB 0 0
3 Locked QAM256 99 813000000 Hz 2.8 dBmV 38.8 dB 0 0
4 Locked QAM256 100 819000000 Hz 1.9 dBmV 38.2 dB 0 0
5 Locked QAM256 101 825000000 Hz 1.7 dBmV 38.2 dB 0 0
6 Locked QAM256 102 831000000 Hz 2.8 dBmV 38.7 dB 0 0
7 Locked QAM256 103 837000000 Hz 1.6 dBmV 38.1 dB 0 0
8 Locked QAM256 104 843000000 Hz 1.3 dBmV 37.6 dB 0 0
9 Locked QAM256 105 849000000 Hz 2.8 dBmV 38.7 dB 0 0
10 Locked QAM256 106 855000000 Hz 1.5 dBmV 37.8 dB 0 0
11 Locked QAM256 107 861000000 Hz 1.4 dBmV 37.8 dB 0 0
12 Locked QAM256 108 867000000 Hz 2.4 dBmV 38.2 dB 0 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 23696000 Hz 36.0 dBmV
2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18896000 Hz 34.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 30704000 Hz 36.0 dBmV
4 Locked TDMA and ATDMA 4 2560 Ksym/sec 35600000 Hz 36.0 dBmV
Current System Time: Thu Aug 13 09:00:59 2015
AUG 9 2015
Tracing route to cox.com [68.99.123.161]
over a maximum of 30 hops:
0 10.10.10.17
1 10.10.10.1
2 10.17.208.1
3 68.1.11.194
4 68.1.1.123
5 68.1.15.238
6 68.99.123.4
7 68.99.123.161
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 10.10.10.17 PC
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.10.10.1 ROUTER
0/ 100 = 0% |
2 13ms 1/ 100 = 1% 1/ 100 = 1% 10.17.208.1
0/ 100 = 0% |
3 18ms 5/ 100 = 5% 5/ 100 = 5% 68.1.11.194
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 68.1.1.123
0/ 100 = 0% |
5 50ms 1/ 100 = 1% 1/ 100 = 1% 68.1.15.238
0/ 100 = 0% |
6 49ms 1/ 100 = 1% 1/ 100 = 1% 68.99.123.4
0/ 100 = 0% |
7 39ms 0/ 100 = 0% 0/ 100 = 0% 68.99.123.161
Trace complete.
Tracing route to cox.net [68.99.123.161]
over a maximum of 30 hops:
0 PC [10.10.10.17]
1 DD-WRT [10.10.10.1]
2 10.17.208.1
3 ip68-1-11-194.at.at.cox.net [68.1.11.194]
4 dukedsrj02-ae4.0.rd.at.cox.net [68.1.1.123]
5 68.1.15.238
6 * 68.99.123.4
7 ww2.cox.com [68.99.123.161]
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC [10.10.10.17]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% DD-WRT [10.10.10.1]
2/ 100 = 2% |
2 13ms 2/ 100 = 2% 0/ 100 = 0% 10.17.208.1
0/ 100 = 0% |
3 14ms 2/ 100 = 2% 0/ 100 = 0% ip68-1-11-194.at.at.cox.net [68.1.11.194]
0/ 100 = 0% |
4 --- 100/ 100 =100% 98/ 100 = 98% dukedsrj02-ae4.0.rd.at.cox.net [68.1.1.123]
0/ 100 = 0% |
5 41ms 2/ 100 = 2% 0/ 100 = 0% 68.1.15.238
0/ 100 = 0% |
6 45ms 2/ 100 = 2% 0/ 100 = 0% 68.99.123.4
1/ 100 = 1% |
7 34ms 3/ 100 = 3% 0/ 100 = 0% ww2.cox.com [68.99.123.161]
AUG 10 2015
Tracing route to cox.com [68.99.123.161]
over a maximum of 30 hops:
0 10.10.10.17
1 10.10.10.1
2 10.17.208.1
3 68.1.11.194
4 68.1.1.123
5 68.1.15.238
6 68.99.123.4
7 68.99.123.161
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 10.10.10.17
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.10.10.1
0/ 100 = 0% |
2 8ms 3/ 100 = 3% 3/ 100 = 3% 10.17.208.1
0/ 100 = 0% |
3 9ms 1/ 100 = 1% 1/ 100 = 1% 68.1.11.194
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 68.1.1.123
0/ 100 = 0% |
5 37ms 3/ 100 = 3% 3/ 100 = 3% 68.1.15.238
0/ 100 = 0% |
6 39ms 3/ 100 = 3% 3/ 100 = 3% 68.99.123.4
0/ 100 = 0% |
7 29ms 0/ 100 = 0% 0/ 100 = 0% 68.99.123.161
Trace complete.
Tracing route to cox.com [68.99.123.161]
over a maximum of 30 hops:
0 10.10.10.17
1 10.10.10.1
2 10.17.208.1
3 68.1.11.194
4 68.1.1.123
5 68.1.15.238
6 68.99.123.4
7 68.99.123.161
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 10.10.10.17
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.10.10.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.17.208.1
1/ 100 = 1% |
3 7ms 1/ 100 = 1% 0/ 100 = 0% 68.1.11.194
1/ 100 = 1% |
4 --- 100/ 100 =100% 98/ 100 = 98% 68.1.1.123
0/ 100 = 0% |
5 37ms 3/ 100 = 3% 1/ 100 = 1% 68.1.15.238
0/ 100 = 0% |
6 40ms 2/ 100 = 2% 0/ 100 = 0% 68.99.123.4
0/ 100 = 0% |
7 28ms 2/ 100 = 2% 0/ 100 = 0% 68.99.123.161
Trace complete.
http://www.speedtest.net/result/4574986579.png - 5.6 up 95 down
http://www.pingtest.net/result/128698688.png - 2% packet loss
Ping statistics for 68.99.123.161:
Packets: Sent = 100, Received = 98, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 60ms, Average = 37ms
12 AUG
Ping statistics for 74.125.227.174:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 100ms, Average = 83ms
Ping statistics for 74.125.227.174:
Packets: Sent = 200, Received = 196, Lost = 4 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 101ms, Average = 84ms
Ping statistics for 192.223.30.161:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 80ms, Average = 51ms
13 AUG
http://www.dslreports.com/pingtest/nil/3336276
Any help is appreciated.
↧