Community Forum
Top

Internet outage at the same time.

GeorgeX1
Contributor
‎09-01-2020 04:06 PM

Internet outage at the same time.

Since I got a new Arris Surfboard T25 (few months ago), I have had periodic outages always at the same time -- 12:30am Eastern -- that last anywhere from 4 - 10 minutes. I have directly noticed and been impacted by them every 2-4 days, but it may be happening more often because I'm not always using the internet connection at that time.

 

During the outage, restarting the modem or my router (Netgear R7000) does nothing.  Once the system comes back again (or whatever corrects itself on the distant end), things go back to normal.  However, sometimes the connection stays offline until I manually restart the modem.

 

Repeated attempts to contact customer service result in a long proces of "may I have your name?", "May I have the service address?", "Let me check your system status?", and more often than not a lengthy explanation that "YES, I understand the differernce between 'Internet Conectivity' and 'My internal network's connectivity'."  By the time we slog through all that, the end result is "please contact us when you are actually experiencing this outage so we can diagnose the problem" which is frustrating to say the least.

 

I will add logs.

Reply
GeorgeX1
Contributor
‎09-01-2020 04:08 PM

Re: Internet outage at the same time.

Downstream QAM
 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 16459.00 MHz5.60 dBmV40.95 dB256QAM180592016600
Downstream 27465.00 MHz5.30 dBmV40.37 dB256QAM9711143900
Downstream 38471.00 MHz5.00 dBmV40.37 dB256QAM9327407400
Downstream 49477.00 MHz5.10 dBmV40.37 dB256QAM10594583900
Downstream 510483.00 MHz4.60 dBmV40.37 dB256QAM176848552700
Downstream 611489.00 MHz4.90 dBmV40.37 dB256QAM10666543600
Downstream 712495.00 MHz4.50 dBmV40.37 dB256QAM10663084790
Downstream 813519.00 MHz5.60 dBmV40.37 dB256QAM169256122500
Downstream 914525.00 MHz5.50 dBmV40.95 dB256QAM6807027200
Downstream 1015531.00 MHz5.60 dBmV40.37 dB256QAM5988131200
Downstream 1116537.00 MHz5.60 dBmV40.37 dB256QAM6022332700
Downstream 1217543.00 MHz4.90 dBmV40.37 dB256QAM6736004600
Downstream 1318549.00 MHz4.70 dBmV40.37 dB256QAM6641392410
Downstream 1419555.00 MHz4.20 dBmV38.98 dB256QAM6581815600
Downstream 1520561.00 MHz4.40 dBmV40.95 dB256QAM6756312700
Downstream 1621567.00 MHz4.30 dBmV40.37 dB256QAM6114237500
Downstream 1722573.00 MHz4.40 dBmV40.37 dB256QAM6057943520
Downstream 1823579.00 MHz4.90 dBmV40.37 dB256QAM6509859600
Downstream 1924585.00 MHz5.30 dBmV40.95 dB256QAM6600261000
Downstream 2025591.00 MHz5.40 dBmV40.37 dB256QAM6571098700
Downstream 2126597.00 MHz5.40 dBmV40.37 dB256QAM168135578300
Downstream 2227603.00 MHz4.80 dBmV38.98 dB256QAM6841945530
Downstream 2328609.00 MHz4.80 dBmV38.98 dB256QAM6834949810
Downstream 2429615.00 MHz4.70 dBmV40.37 dB256QAM71055671454590
Downstream 2530621.00 MHz4.40 dBmV38.61 dB256QAM72143558430960
Downstream 2631627.00 MHz4.30 dBmV40.37 dB256QAM7296771122283
Downstream 2733633.00 MHz4.90 dBmV40.37 dB256QAM932932022400
Downstream 2834639.00 MHz5.30 dBmV40.37 dB256QAM922381872460
Downstream 2935645.00 MHz5.90 dBmV40.37 dB256QAM9222633814988
Downstream 3036651.00 MHz5.70 dBmV40.95 dB256QAM87715247726
Downstream 3137657.00 MHz4.80 dBmV38.98 dB256QAM8617255311841
Reset FEC Counters
Downstream OFDM
 FFT TypeChannel Width(MHz)# of Active SubcarriersFirst Active Subcarrier(MHz)Last Active Subcarrier(MHz)Average RxMER(dB)
PilotPLCData
Downstream 24K941880661754474241
 
Upstream QAM
 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1517.30 MHz38.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2836.50 MHz39.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 3730.10 MHz39.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 4623.70 MHz38.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream OFDM
 FFT TypeChannel Width(MHz)# of Active SubcarriersFirst Active Subcarrier(MHz)Last Active Subcarrier(MHz)Tx Power(dBmV)

 Status
System Uptime:0 d: 15 h: 34 m
Computers Detected:staticCPE(1), dynamicCPE(1)
CM Status:Telephony-Reg Complete
Time and Date:Tue 2020-09-01 15:07:25

 Interface Parameters
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledUp1000 (Full)14:C0:3E:14:EA:32
LAN Port 2EnabledDown-----14:C0:3E:14:EA:32
CABLEEnabledUp-----14:C0:3E:14:EA:33
MTAPassUp-----14:C0:3E:14:EA:34

 Diplexer
 Upstream RangeDownstream RangeCurrent Band Setting
Band 05 MHz-85 MHz108 MHz-1002 MHz 
Band 15 MHz-42 MHz108 MHz-1002 MHzX

 

 
Reply
GeorgeX1
Contributor
‎09-01-2020 04:08 PM

Re: Internet outage at the same time.

Hardware Information
 
System:ARRIS DOCSIS 3.1 / PacketCable 2.0 Touchstone Telephony Modem / Retail
HW_REV: 2
VENDOR: ARRIS Group, Inc.
BOOTR: 2.2.16.573854
SW_REV: 11.01.142.PC20
MODEL: T25
Serial Number:A215J3566200599
  
Options: 

 Firmware Build and Revisions
Firmware Name:TS11.01.142_061719_701.PC20.03
Firmware Build Time:Mon Jun 17 15:46:15 EDT 2019
Open Source:View Open Source Attribution

 

 
Reply
GeorgeX1
Contributor
‎09-01-2020 04:08 PM

Re: Internet outage at the same time.


Date TimeEvent IDEvent LevelDescription
8/26/2020 21:14820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:15820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:21820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:21820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:22820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:35820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:35820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:35820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:42820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:42820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:42820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:55820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:55820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 21:56820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:02820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:02820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:03820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:16820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:16820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:16820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:23820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:23820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:23820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:36820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:36820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:37820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:43820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:43820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:44820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:57820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:57820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 22:57820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:04820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:04820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:04820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:17820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:17820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:18820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:24820003003Ranging Request Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:24820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:25820005003Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12/31/1969 19:01820002003No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12/31/1969 19:01820011005RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/26/2020 23:40900000005MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/27/2020 10:35820002003No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/31/2020 23:30840202005Lost MDD Timeout;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12/31/1969 19:01820002003No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12/31/1969 19:01820011005RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
8/31/2020 23:34900000005MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
9/1/2020 9:11820002003No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 PacketCable(MTA) Events

Date TimeEvent IDDescription
8/25/2020 7:0765527SIP Registration Timeout
8/25/2020 7:0765527SIP Registration Timeout
8/25/2020 7:1265511SIP DNS Query Failure
8/25/2020 7:1265527SIP Registration Timeout
8/25/2020 7:1265527SIP Registration Timeout
8/25/2020 7:1365527SIP Registration Timeout
8/25/2020 7:1365527SIP Registration Timeout
8/25/2020 7:1365527SIP Registration Timeout
8/25/2020 7:1365527SIP Registration Timeout
8/25/2020 7:1865527SIP Registration Timeout
8/25/2020 7:1865527SIP Registration Timeout
8/25/2020 7:1965527SIP Registration Timeout
8/25/2020 7:1965527SIP Registration Timeout
8/25/2020 7:1965527SIP Registration Timeout
8/25/2020 7:1965527SIP Registration Timeout
8/25/2020 7:2465527SIP Registration Timeout
8/25/2020 7:2565527SIP Registration Timeout
8/25/2020 7:2565527SIP Registration Timeout
8/25/2020 7:2565527SIP Registration Timeout
8/25/2020 7:2565527SIP Registration Timeout
8/25/2020 7:2565527SIP Registration Timeout
8/25/2020 7:3065527SIP Registration Timeout
8/25/2020 7:3165527SIP Registration Timeout
8/25/2020 7:3165527SIP Registration Timeout
8/25/2020 7:3165527SIP Registration Timeout
8/25/2020 7:3165511SIP DNS Query Failure- Cleared
8/25/2020 7:3165527SIP Registration Timeout
8/25/2020 7:3165527SIP Registration Timeout
8/25/2020 7:3665511SIP DNS Query Failure
8/25/2020 7:3765527SIP Registration Timeout
8/25/2020 7:3765527SIP Registration Timeout
8/25/2020 7:3765527SIP Registration Timeout
8/25/2020 7:3765527SIP Registration Timeout
8/25/2020 7:3765527SIP Registration Timeout
8/25/2020 7:3765527SIP Registration Timeout
8/25/2020 7:4516MTA TFTP: Successful
8/25/2020 7:454000951500Provisioning Complete
8/25/2020 7:4526MTA PROV: Successful!
8/25/2020 7:453Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/25/2020 7:453Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS
8/26/2020 23:4016MTA TFTP: Successful
8/26/2020 23:404000951500Provisioning Complete
8/26/2020 23:4026MTA PROV: Successful!
8/26/2020 23:403Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/26/2020 23:403Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS
8/31/2020 23:3516MTA TFTP: Successful
8/31/2020 23:354000951500Provisioning Complete
8/31/2020 23:3526MTA PROV: Successful!
8/31/2020 23:353Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/31/2020 23:353Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS

 

 
Reply
GeorgeX1
Contributor
‎09-01-2020 04:10 PM

Re: Internet outage at the same time.

In case it matters to the modem performance, we have Triple Play but do not own a land line phone so the phone jack and line has never been used/accessed/plugged into anything.

Reply
GeorgeX1
Contributor
‎09-03-2020 12:36 AM

Re: Internet outage at the same time.

And again tonight. Same time.

Not sure why my modem is on Central time.

9/2/2020 23:27 84020200 5 Lost MDD Timeout;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12/31/1969 19:01 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12/31/1969 19:01 82001100 5 RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
9/2/2020 23:29 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
9/2/2020 23:29 82001100 5 RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:14:ea:33;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Reply
GeorgeX1
Contributor
‎09-09-2020 12:44 AM

Re: Internet outage at the same time.

And this continues. Every night this week at 12:30am Eastern.

Does anyone from customer service read these forums? Is this a “don’t know” or “don’t care”?

The fact that this happens each night on Comcast’s network yet nobody seems to be able to tell me what or why this is happening is an atrocious lack of either customer service or agent education. Further, the fact that every conversation with a rep steers towards some version of “we can come out and figure out what’s wrong with your internal network” indicates a prevailing attitude of “the customer is wrong until proven right”. Ironic given how many times I’ve had to explain the difference between LAN connectivity and WAN connectivity to said reps.
Reply
Tsugu
New Poster
‎10-01-2020 12:00 AM

Re: Internet outage at the same time.

I have the same T25 and experiance a similer outage exery 7 to 11 days. Have had Comcast to house, all levels are fine. See post: https://forums.xfinity.com/t5/Your-Home-Network/Every-11-days-lost-Internet-connection/td-p/3333854

 This is so fustrating COMCAST FIX YOUR PROVISIONING!!

Reply
Tsugu
New Poster
‎10-01-2020 12:01 AM

Re: Internet outage at the same time.

Also see: https://forums.xfinity.com/t5/Your-Home-Network/Internet-Connection-Lost-Arris-T25-Modem-frozen/td-p...

 

Reply
AGB2
Regular Visitor
‎10-01-2020 08:02 AM

Re: Internet outage at the same time.

Joining the fray here, I replied to this post here:  https://forums.xfinity.com/t5/Your-Home-Network/Re-SIP-DNS-Query-Failure-Periodic-loss-of-Internet-M...

 

Having a very very similar issue, only mine is every 4/5 days.  This last time connection lasted a day and 1/2 before I needed a manual reboot.  Mine usually fails around 6AM Central time - not sure why mine is Central either?  I'm in the Eastern time zone.

 

So many calls to tech support, swapped my CM1150V for this T25, and for 5 days it seemed like that was the fix.  Now I'm having to power cycle my devices AGAIN.  


Would be great if a tech who didn't ask "what's the service address"  "could you confirm the last 4 digitrs of the account holder's SSN" would come here and offer some help.

 

Here's my most recent batch of the exact same errors: 

 

10/1/2020 3:3665527SIP Registration Timeout
10/1/2020 3:3765527SIP Registration Timeout
10/1/2020 3:3865527SIP Registration Timeout
10/1/2020 3:3865524SIP Network Failure
10/1/2020 3:3965511SIP DNS Query Failure- Cleared
10/1/2020 3:3965527SIP Registration Timeout- Cleared
10/1/2020 3:3965524SIP Network Failure- Cleared
10/1/2020 3:3965510SIP pCSCF Discovery Failure- Cleared
10/1/2020 4:3065511SIP DNS Query Failure
10/1/2020 4:3265527SIP Registration Timeout
10/1/2020 4:3265524SIP Network Failure
10/1/2020 4:3265510SIP pCSCF Discovery Failure
10/1/2020 4:3565527SIP Registration Timeout
10/1/2020 4:3665524SIP Network Failure
10/1/2020 4:3965527SIP Registration Timeout
10/1/2020 4:4065524SIP Network Failure
10/1/2020 4:4565527SIP Registration Timeout
10/1/2020 4:4565524SIP Network Failure
10/1/2020 4:5265527SIP Registration Timeout
10/1/2020 4:5265524SIP Network Failure
10/1/2020 4:5265509SIP pCSCF Discovery Timeout
10/1/2020 4:5965511SIP DNS Query Failure- Cleared
10/1/2020 4:5965527SIP Registration Timeout- Cleared
10/1/2020 4:5965524SIP Network Failure- Cleared
10/1/2020 4:5965510SIP pCSCF Discovery Failure- Cleared
10/1/2020 4:5965509SIP pCSCF Discovery Timeout- Cleared
10/1/2020 5:4965511SIP DNS Query Failure
10/1/2020 5:5065527SIP Registration Timeout
10/1/2020 5:5165527SIP Registration Timeout
10/1/2020 5:5165524SIP Network Failure
10/1/2020 5:5165510SIP pCSCF Discovery Failure
10/1/2020 5:5265527SIP Registration Timeout
10/1/2020 5:5365527SIP Registration Timeout
10/1/2020 5:5465527SIP Registration Timeout
10/1/2020 5:5465524SIP Network Failure
10/1/2020 5:5665527SIP Registration Timeout
10/1/2020 5:5765527SIP Registration Timeout
10/1/2020 5:5765527SIP Registration Timeout
10/1/2020 5:5865524SIP Network Failure
10/1/2020 6:0065527SIP Registration Timeout
10/1/2020 6:0065511SIP DNS Query Failure- Cleared
10/1/2020 6:0065527SIP Registration Timeout- Cleared
10/1/2020 6:0065524SIP Network Failure- Cleared
10/1/2020 6:0065510SIP pCSCF Discovery Failure- Cleared
10/1/2020 6:0165511SIP DNS Query Failure
0 Likes
Reply
GeorgeX1
Contributor
‎10-15-2020 12:31 PM

Re: Internet outage at the same time.

An update and "thus far":

 

  • Multiple (and by that I mean at least a dozen) chat and phone interactions with customer service personnel.
  • 2 tech visits in 2 days.  One tech found nothing wrong.  The other actually tested the signal strength inside and discussed the issue at length with me.
    • Prevailing suggestion: try a different modem.
    • Tech #2 also removed the filter at the back of my modem and installed a new one outside that he said was "the right one".
  • Tech #2 was prompted by a second call to customer service which resulted in the promising diagnosis of "you didn't get fiber run to the house when you got new service?".  However it turned out upon tech arrival that fiber isn't in my area so that obviously wasn't the problem.
  • Since Tech #2, the problem still occurs with the modem stopping functionality, not every night, but always between 12 midnight and 12:30.  With a restart of the modem being the only thing that brings things back.
  • Since Tech #2, while it seems like the problem occurs less, my download speed has been no higher than ~550Mbps -- per Xfinity's speed test and Ookla, tested at 9AM, 1PM, and 12 midnight Eastern -- which is just over 1/2 the advertised speed of the plan.

 

My next move: obtain another modem and see if this problem persists.  Since Xfinity's modem auto-restarts at 2-4AM, that hardly fixes the problem of an interruption overnight other than automating the restart.  So, that leaves the Netgear CM1150V as the candidate.  Promisingly, it does NOT use an Intel Puma 7 chipset like the T25 which seems to have some indication around the net that it may suffer the issues with Puma 6, if not as glaringly.  We shall see.

 

Note to those who would like to try this: look for extended holiday return times for products.  That gives you an extra couple months (often into mid-January) to return things if there's no improvement.

 

I will update with any info.

0 Likes
Reply
Alanlpa
Regular Visitor
‎10-15-2020 06:23 PM

Re: Internet outage at the same time.

my internet does that also around 4PM EST I think Xfinity can't handle too many people connecting at the same time, but they will not admit it

0 Likes
Reply
GeorgeX1
Contributor
‎10-20-2020 10:03 PM

Re: Internet outage at the same time.

Update: Installed the Netgear CM1150V tonight.

 

Speeds are slightly up (mid-500s to low 700s on Ookala) but about the same or maybe slightly lower on Xfinity's speed test.

 

Very interestingly, the CM1150V reports the same signal strengths that the Xfinity tech showed me on his hand-held reader (connected to the same cable that goes to my modem) whereas the T25 was always reporting low.  The signals reported are what the Arris techs claim that Comcast needs to be supplying.

Reply
PCurrao
Frequent Visitor
‎10-23-2020 06:41 AM

Re: Internet outage at the same time.

Just an update from me.

 

I had the Arris T25 as well.. Same problem as y'all.. Just about nightly reset at 1am. Had to power cycle my modem every 3-4 days. Error logs were always active, and uncorrectable errors piled up.

 

Installed the Netgear modem about 4 days ago, and it has been solid. No errors, not even any uncorrectable errors reported. Eveything just stays up as it should.

0 Likes
Reply
GeorgeX1
Contributor
‎10-27-2020 12:13 PM

Re: Internet outage at the same time.

1 Week update:

Zero down time.

2 Correctables, zero Uncorrectables.

Event log is still empty.

It could be my imagination, but compared to the T25, things are more responsive/smooth.

 

I am incredibly annoyed at Comcast for having even listed the T25 as an option. Unless they sureptitiously changed something in my service (doubt it), the T25, while techincally "working" on their network, is arguably slower, definitely more error prone, and routinely locks up.  However given that Comcast would undoubtedly prefer me to pay them $15/month, I can't say I'm surprised they didn't bother vetting the T25 properly.

 

Now what to do with a T25?

Reply
Visit Our Help Communities