Problems in cardiff?

Question

Hi, after 3 years of nearly perfect service it's really went down the pan today.

Getting a lot of disconnects, weirdly seems to be when i try to upload files .

Lots of messages in the log:

Time	Priority	Description
15-09-2025 18:04:26	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 18:02:35	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 18:01:17	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 18:00:05	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:59:52	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:26	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:22	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:20	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:17	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:15	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:06	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:01	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:58:01	notice	CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 27; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:54	notice	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:53	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:51	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:51	warning	MDD message timeout;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:49	notice	CM-STATUS message sent. Event Type Code: 1; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:46	notice	CM-STATUS message sent. Event Type Code: 2; Chan ID: 4 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:45	warning	MDD message timeout;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:44	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:42	notice	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:42	notice	CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 7 27; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:38	notice	CM-STATUS message sent. Event Type Code: 2; Chan ID: 5 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:37	notice	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:37	warning	MDD message timeout;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:35	warning	MDD message timeout;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:34	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 5 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:22	notice	CM-STATUS message sent. Event Type Code: 1; Chan ID: 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:20	notice	CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 27; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:16	notice	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;
15-09-2025 17:57:15	warning	MDD message timeout;CM-MAC=64:fd:96:73:a8:43;CMTS-MAC=00:01:5c:6a:fc:68;CM-QOS=1.1;CM-VER=3.1;

says there are signal issues in your area.

Cardiffman282 · Answer

I'm in Cardiff and I am fine. All the same check for local faults on 0800 561 0061.&nbsp;

Forum Discussion

Problems in cardiff?

1 Reply

Related Content

Problems with online account

Another contract renewal problem!

Problem accessing SECONDARY email accounts

routing problems to Google DNS?

Network Routing problem