So, if you are surrounded by thousands of your neighbors who all have had outages at the same time as you - it is not you - it is Comcast that is having a problem.
Start with the modem's signal stats. Perhaps they already are, or they are close to being out of spec and intermittently they go completely of spec. Try getting them here http://192.168.100.1 or here http://10.0.0.1
Please copy all of the text in its entirety of the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers and paste them into your next post.
What is the exact make and model number of the modem ?
Please create a new topic of your own here on this board detailing your issue and someone will attempt to assist you there. Please do not hijack someone else's help thread in progress. Multiple posters piling onto and being helped in a single thread becomes too complicated, confusing, and convoluted. And it's unfair to the original poster. Thank you
I am not a Comcast Employee. I am a Customer Expert volunteering my time to help other customers here in the Forums. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer!
My intent was to provide information to flagrant99 to help him solve his problem. He may have a modem that Comcast has blocked port 80 on and he would not be able to do as you suggested.
My information provided to flagrant99 might save him from hours of frustration - especially if he tries to follow your recommendations and there is no one available to explain why port 80 is blocked.
Also, as a best-practices trouble-shooting process - the very first thing that should be suggested is to see if there is a neighborhood wide outage in flagrant99's location. Why spend hours or months trouble-shooting his specific situation if the problem is with Comcast and not flagranr99. It takes 5 seconds to check:
For example, just this minute, the number of Comcast outages went from 1-50 to 51-500 in my zip-code. So, I know to quickly finish up a couple of things before a possible outage hits my home.
Thanks to everyone for any help. I was just frustrated with the Bots at Comcast. Yeah there have been many neighbor hood outages. Got an email about some upgrades coming like a week ago. So ask the bot to text my when it's up. It's up for 5 minutes then goes out again. Every day for last couple of days. Wanted to find out how long this work is going on but No one answers anything anymore at Comcast. Rinse Repeat.
I think they might be doing work in my area regardless so hopefully eventually the major pain will stop. The intermitent pain is here in my log. I do see T3 Time outs alot well before this started. Removed all splitters.
14/2/2022 17:12:07
3
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
14/2/2022 17:13:43
3
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"]CM-QOS=1.1;CM-VER=3.1;
14/2/2022 17:14:42
3
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
14/2/2022 17:14:49
3
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 08:10:46
3
Successful LAN WebGUI login from 24.91.130.167 on 22/02/15 at 8:10 AM.
15/2/2022 14:16:42
3
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:18:55
3
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:18:56
3
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:19:05
3
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:19:05
3
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:19:09
3
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:19:12
3
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:20:28
3
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:22:55
6
Honoring MDD; IP provisioning mode = IPv6
15/2/2022 14:23:10
5
REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 14:23:11
5
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
15/2/2022 18:35:51
3
Successful LAN WebGUI login from 24.91.130.167 on 22/02/15 at 6:35 PM.
O/k so the signal stats looked good / in spec at that snapshot in time, but the error log entries confirm that something is going on. Perhaps there is intermittent noise ingress into the line(s) / an upstream channel-return path impairment somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
I am not a Comcast Employee. I am a Customer Expert volunteering my time to help other customers here in the Forums. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer!
My service goes out daily again. Why are you working to make improvements every day and cutting out my internet. Every time it says it will be back in 45 minutes.
We’ve detected a network performance issue in your area and we’re working to make improvements as quickly as we can; you may experience a temporary service interruption during this time. We'll have you back up and running by approximately 04/12/2022 10:34 AM (Eastern). We apologize for any inconvenience and appreciate your patience. Would you like to receive updates via SMS about the progress of the outage?
truerock2
Contributor
•
227 Messages
4 years ago
My neighborhood has had frequent outages for 5 months.
Tens of thousands of Comcast customers have outages in my part of Houston every week.
Here are some examples from Comcast outage maps for my zip-code of 5,000 single family homes:
https://www.xfinity.com/support/status-map
Outage type: unplanned
11/18/2021: 2,500+ customers
12/02/2021: 2,500+ customers
01/11/2022: 51-500 customers
01/23/2022: 2,500+ customers
02/05/2022: 51-500 customers
02/07/2022: 2,500+ customers
02/14/2022: 51-500 customers
02/15/2022: 1-50 customers
So, if you are surrounded by thousands of your neighbors who all have had outages at the same time as you - it is not you - it is Comcast that is having a problem.
0
0
EG
Expert
•
118.7K Messages
4 years ago
@flagrant99
Start with the modem's signal stats. Perhaps they already are, or they are close to being out of spec and intermittently they go completely of spec. Try getting them here http://192.168.100.1 or here http://10.0.0.1
Please copy all of the text in its entirety of the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers and paste them into your next post.
What is the exact make and model number of the modem ?
Is this a WiFi connection ?
8
EG
Expert
•
118.7K Messages
4 years ago
O/k so the signal stats looked good / in spec at that snapshot in time, but the error log entries confirm that something is going on. Perhaps there is intermittent noise ingress into the line(s) / an upstream channel-return path impairment somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
(edited)
7