Visitor
•
2 Messages
Intermittent internet outages
Hi there,
Over the past month, I've been having intermittent connectivity issues impacting my home internet usually around once or twice a day (usually lasting around 5 minutes or so with no internet available).
The issue does not seem to be a hardware issue (hardwired connection still experiencing same issue). See stats below for more info.
Downstream Connectivity Stats
Channel | Lock Status | Modulation | Channel ID | Freq. (MHz) | Pwr (dBmV) | SNR (dB) | Corrected | Uncorrected |
1 | Locked | QAM256 | 29 | 597.0 | 2.1 | 38.4 | 393 | 0 |
2 | Locked | QAM256 | 30 | 603.0 | 1.8 | 38.2 | 402 | 0 |
3 | Locked | QAM256 | 31 | 609.0 | 1.7 | 38.1 | 338 | 0 |
4 | Locked | QAM256 | 32 | 615.0 | 1.5 | 38.0 | 331 | 0 |
5 | Locked | QAM256 | 33 | 621.0 | 1.5 | 37.9 | 334 | 0 |
6 | Locked | QAM256 | 34 | 627.0 | 1.6 | 37.8 | 335 | 0 |
7 | Locked | QAM256 | 35 | 633.0 | 1.7 | 37.8 | 340 | 0 |
8 | Locked | QAM256 | 36 | 639.0 | 1.8 | 37.8 | 368 | 0 |
9 | Locked | QAM256 | 37 | 645.0 | 1.8 | 37.7 | 325 | 0 |
10 | Locked | QAM256 | 38 | 651.0 | 1.4 | 37.6 | 325 | 0 |
11 | Locked | QAM256 | 39 | 657.0 | 1.4 | 37.6 | 300 | 0 |
12 | Locked | QAM256 | 40 | 663.0 | 1.5 | 37.6 | 333 | 0 |
13 | Locked | QAM256 | 41 | 669.0 | 1.6 | 37.6 | 250 | 0 |
14 | Locked | QAM256 | 42 | 675.0 | 1.9 | 37.4 | 240 | 0 |
15 | Locked | QAM256 | 43 | 681.0 | 2.0 | 37.8 | 228 | 0 |
16 | Locked | QAM256 | 44 | 687.0 | 2.2 | 37.9 | 208 | 0 |
Total | 5050 | 0 |
Upsteam Connectivity Stats
Channel | Lock Status | Channel Type | Channel ID | Symb. Rate (Ksym/sec) | Freq. (MHz) | Pwr (dBmV) |
1 | Locked | ATDMA | 12 | 5120 | 29.2 | 54.3 |
2 | Not Locked | Unknown | 0 | 0 | 0 | 0.0 |
3 | Not Locked | Unknown | 0 | 0 | 0 | 0.0 |
4 | Not Locked | Unknown | 0 | 0 | 0 | 0.0 |
Event Log
Time | Priority | Description |
Sun May 28 12:51:02 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:51:04 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:52:21 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:52:24 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:53:22 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:53:24 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:53:38 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:53:44 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:54:38 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:54:45 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:54:45 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:54:46 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:54:46 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:54:51 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:54:51 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:54:59 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:54:59 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:55:00 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:55:00 2023 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC; |
Sun May 28 12:55:02 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:55:08 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:55:08 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:55:11 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:55:11 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:55:12 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:55:12 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:55:14 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:55:14 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:55:20 2023 | Warning (5) | Dynamic Range Window violation |
Sun May 28 12:55:20 2023 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC; |
Sun May 28 12:55:37 2023 | Critical (3) | No Ranging Response received - T3 time-out; |
Sun May 28 12:55:44 2023 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Any thoughts or suggestions are appreciated.
Thank you!
BruceW
Gold Problem Solver
•
26.4K Messages
2 years ago
The downstream signals look OK, but the upstream has problems. At least 3 channels should be locked. Only 1 is, and the power level on that one is out of spec (too high).
Network connection problems like this are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.
If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you still need help, please post your Internet plan speed and the modem model number.
If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.
If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit ($70-$100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.
Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.
0
0
user_f95f4a
Visitor
•
2 Messages
2 years ago
Hi there,
Was able to restart the modem and upstream appears to have 4 locked now, although it still seems out of spec.
The Internet plan is 400 Mbps - speed test gets back range from 55 to 115 Mbps over wifi.
The device is a Motorola MG7550.
Appreciate the help, thanks!
0
0
BruceW
Gold Problem Solver
•
26.4K Messages
2 years ago
Although it's probably not the primary problem, be aware that the MG7550 is not approved for use with 400 Mbps service. https://www.xfinity.com/support/devices says it is approved for use with plan speeds "Up to 373 Mbps". Using an device not approved for the plan speed typically results in measured speeds well below the speed you're paying for.
As for the updated upstream signal values, the intermittent nature of the signals suggests, as stated, a coax cable connection problem. I'm not sure what to make of, once again, one channel being out-of-spec high. I would guess that it too is most likely due to a cable fault, but it might also be due to a defective transmit channel in the modem.
It would be best to either replace the modem with one rated for use with your plan speed, or lower your plan speed below the modem's approved limit. And, as above, if you can't find the cause of the out-of-spec/missing upstream channels you'll need to have a premise tech take a look at the problem.
Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.
0
0