New Poster
•
1 Message
Asus RT-AX88U Router will not maintain gigabit speed
Hello everyone.
I have an Asus RT-AX88U router updated with the latest manufacturer firmware and an Arris SB8200 modem.
I have the gibabit internet package and I know both devices are compatible.
I would like to know if there are some settings I am missing or if I need to do a factory reset as my gigabit speeds only last for a short period of time then are reduced to a fraction of their original speed. Upon power cycling the router the speeds recover but, again only for a short period of time
Power cycling the router alone restores the speeds as well making me think it is not a modem issue.
On a fresh power cycling of both devices I show 6-700 Mbps downloads and 42 ish Mbps uploads.
However after several hours the download speed upon re testing is around 5 Mbps and 13 ish Mbps uploads.
These speeds were determined at the router via the internal speed testing app powered by Ookla.
QoS is off , Guest network is off, using a CAT6 cable
@EG I have seen some of your comments and was hoping you could possibly help me troubleshoot this.
tgwjrx06
Regular Visitor
•
4 Messages
4 years ago
@EG Plugging directly into the router with an ethernet cable to my laptop I get around 5 Mbps speeds. I need to wait until later to try directly into the modem as there are people using it to work from home.
The Arris SB8200 modem has 2 output ports on the back but if I directly plug into the second port I can't get any connection at all, it simply says "self identified IP address" in my network preferences (Mac) and as others are using the wifi I can't unplug the #1 connection which is plugged into the router this time.
Xfinity's speed test gives the same results when plugged in and when using the Asus app over Wifi . While previously running speed tests w/in Asus' app I assumed it was reading the hard wired speed directly from the router. I was doing that thinking it would read that speed directly from the hard wired router. Confirmed same speeds wired vs wireless both.
Either way on wireless or plugged directly into the router I am still getting 5 Mbps. Will test the direct modem connection as soon as I can.
I am thinking it may be a router issue only because rebooting (power cycling) fixes the problem but only temporarily...
I am not sure if there is an Asus router setting prohibiting it from maintaining gigabit speeds.
0
0
EG
Expert
•
106.5K Messages
4 years ago
FWIW, only port number 1 is active on the 8200. Port number 2 is disabled. You would need them to assign a second public / WAN IP address (for a fee) to it in order for it to be able to have internet access.
0
0
EG
Expert
•
106.5K Messages
4 years ago
Does the same thing happen with a direct connection to the 8200 cable modem (no router in the mix) ?
Is this with a WiFi connection or an ethernet connection to the router ?
Try this speed test: https://speedtest.xfinity.com/
0
0
tgwjrx06
Regular Visitor
•
4 Messages
4 years ago
@EG thank you for that information.
I will get back to you ASAP regarding the speed test on the modem itself.
I checked my speed test logs (asus/ookla) and it seems the longest "maintained" speeds of 6-700 Mbps is over a 8-9 hour period. I test at 2255 one night then 0700 the next morning and they were similar speed. Later in the day it was back to 4-5 Mbps again until I power cycled the equipment again.
I am really stumped.
0
0
tgwjrx06
Regular Visitor
•
4 Messages
4 years ago
I will also discuss with the technician. This house was wired for Direct TV prior to me moving in so when Comcast set it up it was on the lowest level of course.
0
0
tgwjrx06
Regular Visitor
•
4 Messages
4 years ago
@EG I plugged directly in and was only getting 30-40 mbps directly from the modem. I called comcast after they resent signal / refreshed modem (which did not help). They are sending a tech to see if it is an issue coming from outside the home.
I plugged everything back in and now from within the router's speed test (in the asus GUI being run through my phone) I am getting 715.41 MBPS download speeds from what I assume is the router which is directly connected to the modem. I have no doubt this will go down again tomorrow. I am baffled
Here are the modem logs followed by event logs while plugged directly in.
Connection
The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.
Startup Procedure
Procedure
Status
Comment
Acquire Downstream Channel
651000000 Hz
Locked
Connectivity State
OK
Operational
Boot State
OK
Operational
Configuration File
OK
Security
Enabled
BPI+
DOCSIS Network Access Enabled
Allowed
Downstream Bonded Channels
Channel ID
Lock Status
Modulation
Frequency
Power
SNR/MER
Corrected
Uncorrectables
33
Locked
QAM256
651000000 Hz
7.4 dBmV
41.6 dB
2
0
1
Locked
QAM256
465000000 Hz
6.4 dBmV
41.9 dB
10
0
2
Locked
QAM256
471000000 Hz
6.8 dBmV
38.5 dB
7
0
3
Locked
QAM256
477000000 Hz
6.7 dBmV
39.1 dB
8
0
4
Locked
QAM256
483000000 Hz
6.7 dBmV
41.0 dB
8
0
5
Locked
QAM256
489000000 Hz
7.0 dBmV
42.1 dB
10
0
6
Locked
QAM256
495000000 Hz
6.8 dBmV
42.1 dB
10
0
7
Locked
QAM256
501000000 Hz
7.0 dBmV
39.7 dB
11
0
8
Locked
QAM256
507000000 Hz
7.2 dBmV
42.3 dB
13
0
9
Locked
QAM256
513000000 Hz
7.4 dBmV
42.1 dB
9
0
10
Locked
QAM256
519000000 Hz
7.1 dBmV
37.6 dB
7
0
11
Locked
QAM256
525000000 Hz
6.7 dBmV
41.7 dB
8
0
12
Locked
QAM256
531000000 Hz
6.9 dBmV
41.7 dB
2
0
13
Locked
QAM256
537000000 Hz
6.9 dBmV
38.5 dB
2
0
14
Locked
QAM256
543000000 Hz
6.9 dBmV
41.8 dB
5
0
15
Locked
QAM256
549000000 Hz
6.8 dBmV
41.2 dB
6
0
16
Locked
QAM256
555000000 Hz
7.3 dBmV
41.6 dB
2
0
17
Locked
QAM256
561000000 Hz
7.2 dBmV
41.6 dB
1
0
18
Locked
QAM256
567000000 Hz
7.1 dBmV
41.9 dB
1
0
19
Locked
QAM256
573000000 Hz
7.1 dBmV
41.8 dB
0
0
20
Locked
QAM256
579000000 Hz
7.2 dBmV
41.3 dB
3
0
21
Locked
QAM256
585000000 Hz
7.1 dBmV
41.5 dB
6
0
22
Locked
QAM256
591000000 Hz
7.4 dBmV
41.4 dB
2
0
23
Locked
QAM256
597000000 Hz
7.3 dBmV
41.4 dB
5
0
24
Locked
QAM256
603000000 Hz
7.3 dBmV
41.5 dB
7
0
25
Locked
Other
672000000 Hz
7.7 dBmV
21.2 dB
24222637
63484
26
Not Locked
QAM256
0 Hz
0.0 dBmV
41.7 dB
6
0
27
Locked
QAM256
609000000 Hz
7.5 dBmV
41.7 dB
6
0
28
Locked
QAM256
615000000 Hz
7.3 dBmV
32.3 dB
2404362
2340635
29
Locked
QAM256
621000000 Hz
7.1 dBmV
27.6 dB
974629
1162350
30
Locked
QAM256
627000000 Hz
7.2 dBmV
41.4 dB
435569
969423
32
Locked
QAM256
633000000 Hz
7.6 dBmV
41.9 dB
1
0
Upstream Bonded Channels
Channel
Channel ID
Lock Status
US Channel Type
Frequency
Width
Power
1
5
Locked
SC-QAM Upstream
17300000 Hz
6400000 Hz
59.0 dBmV
2
7
Locked
SC-QAM Upstream
30100000 Hz
6400000 Hz
59.0 dBmV
3
6
Locked
SC-QAM Upstream
23700000 Hz
6400000 Hz
59.0 dBmV
4
8
Locked
SC-QAM Upstream
36500000 Hz
6400000 Hz
56.0 dBmV
Current System Time: Mon Dec 21 17:09:40 2020
Event Log
Status > Event Log
The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.
Top of Form
Date Time
Event ID
Event Level
Description
12/21/2020 17:30
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:30
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:30
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:30
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 1; Chan ID: 28 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:29
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:28
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:27
74010100
6
"CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:26
84020300
5
"MDD message timeout;CM-MAC=18:9c:27:ee:db:19;CMTS-MAC=00:01:5c:88:38:46;CM-QOS=1.1;CM-VER=3.1;"
12/21/2020 17:26
74010100
6
"CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 29
Bottom of Form
0
0
EG
Expert
•
106.5K Messages
4 years ago
The upstream power is WAY out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
0
0
EG
Expert
•
106.5K Messages
4 years ago
You could try it and see.
For the tech visit, bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home.
Good luck with it ! Please post back with how things turn out.
0
0
md981
Visitor
•
1 Message
4 years ago
How did this issue get resolved? I am having a similar experience.
0
0
EG
Expert
•
106.5K Messages
4 years ago
@md981
Please create a new topic of your own here on this board detailing your issue. Thanks. The original poster has not returned. 3 month old dead now being closed.
0
0