3-4 connection drops per hour, lots of t3 errors, but I think signal levels are ok - Time Warner Internet

#1
This question is about "3-4 connection drops per hour, lots of t3 errors, but I think signal levels are ok", with Time Warner Cable internet and apps. We've seen frequent drops of our connection in the past month. I'll see it on all my devices and the cable light on the modem will start flashing. This can easily happen 3+ times an hour causing movies to buffer, music to stop, and low pitched grumbles from the wife.



The modem log shows numerous T3 errors but I believe my signal levels look ok. Called support who said the modem has only gone down 4 times over the past month and that it's not an issue on their end so call Linksys. This is my own modem because I'd rather not continue paying for a modem long after it's paid it off.



What should I troubleshoot next? Should I buy another modem? rent one from Spectrum if it will get them to look into the issue?



  • 3-4 drops an hour for the past month
  • Many T3 errors
  • Signal levels and log attached
  • Haven't changed anything in the house
  • CSR said their's nothing they can do
  • Linksys CM3008 modem
  • North east Charlotte, NC
  • Only buying internet and no other devices are hooked up to the coax
  • 50-70mbps down 5-7mbps up speed tests



Status
DOCSIS WAN
DOCSIS Overview
[TABLE]

Network Access

Permitted


IP Address

2606:a000:c00:74:155d:1c42:2f99:e21d


Subnet Mask


Gateway IP


DHCP Lease Time

D: -- H: -- M: -- S: --

[/TABLE]
Downstream Overview
[TABLE]

Port ID

Frequency (Hz)

Modulation

Signal strength (dBmV)

Signal noise ratio (dB)

Octets

Correcteds

Uncorrectables

Channel ID


1

645000000

256QAM

-4.325

36.844

48269

0

0

32


2

633000000

256QAM

-3.256

37.093

51921

0

0

30


3

639000000

256QAM

-3.664

37.356

56437

0

0

31


4

627000000

256QAM

-2.281

37.356

60083

0

0

29


5

507000000

256QAM

2.469

37.636

63777

0

0

9


6

513000000

256QAM

1.793

37.936

66943

0

0

10


7

519000000

256QAM

1.491

37.093

71208

0

0

11


8

525000000

256QAM

2.009

38.258

74946

0

0

12


[/TABLE]
Upstream Overview
[TABLE]

Port ID

Frequency (Hz)

BandWidth (Hz)

Modulation Type

DOCSIS Mode

Signal Strength (dBmV)

Channel ID


1

17600000

6400000

64QAM

ATDMA

37.000

1


2

36800000

6400000

64QAM

ATDMA

38.500

4


3

30400000

6400000

64QAM

ATDMA

37.000

3


4

24000000

6400000

64QAM

ATDMA

37.000

2

[/TABLE]



DOCSIS Logs
The docsis event logs is shown here

[TABLE]

No

Time

type

Priority

Event


1

04/01/19 23:20:16

90000000

warning

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


2

04/01/19 22:37:36

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


3

04/01/19 22:37:22

82000600

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


4

04/01/19 22:37:22

82000300

critical

Ranging Request Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


5

04/01/19 22:37:22

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


6

04/01/19 22:37:21

82000600

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


7

04/01/19 22:37:21

82000300

critical

Ranging Request Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


8

04/01/19 22:37:21

82000600

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


9

04/01/19 22:37:21

82000300

critical

Ranging Request Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


10

04/01/19 22:37:21

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


11

04/01/19 22:37:20

82000600

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


12

04/01/19 22:37:20

82000300

critical

Ranging Request Retries exhausted;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


13

04/01/19 22:37:19

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


14

04/01/19 22:36:28

82000500

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


15

04/01/19 22:36:27

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


16

04/01/19 22:36:27

82000500

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


17

04/01/19 22:36:26

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


18

04/01/19 22:36:26

82000500

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


19

04/01/19 22:36:25

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;


20

04/01/19 22:36:25

82000500

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:91:82:5e:ad:84;CMTS-MAC=00:17:10:88:d9:e0;CM-QOS=1.1;CM-VER=3.0;

[/TABLE]

3-4 connection drops per hour, lots of t3 errors, but I think signal levels are ok?
 
Top