05-31-2024 04:18 PM - last edited on 05-31-2024 05:28 PM by RogersMoin
Hi,
Would it be possible for someone here to look into the problem I'm having with intermittent disconnections? I'm getting disconnected multiple times a day and I've been dealing with Rogers but they have not been able to help even though they claim they have fixed the issue.
I can provide more details and ticket #'s if there's someone here that is able to look into this.
Thanks.
*Added Labels*
06-02-2024 08:25 PM
@-G-Thanks for letting me know. I had no idea what an acceptable amount of uncorrectable codeword errors would be. I'll ask them.
@DatalinkI had problems with the legacy digital TV package a few years ago and a Rogers technician gave me a 1 to 1 connection. I think it's called a coupler but when I looked up f-81 connector, the one I have looks like that. I don't have any splitters.
06-03-2024 04:28 PM
I received a response regarding what you suggested I ask the moderators. My OFDM MIBs are all within specification and there doesn't seem to be any issues with disconnections in my area.
I'll post updated modem stats. I've noticed some packet loss today but I did not see any disconnections. If there was an intermittent disconnection, would the modem uptime stat pick up on it even if it was minor?
System Uptime: 2 days 22h: 50m: 28s
IndexLock StatusFrequencySNRPower LevelModulation
Downstream | Channel Bonding Value | |||||||||||||||||||||||||||||||
16 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
651 MHz | 279 MHz | 849 MHz | 855 MHz | 861 MHz | 579 MHz | 585 MHz | 591 MHz | 597 MHz | 603 MHz | 609 MHz | 615 MHz | 621 MHz | 633 MHz | 639 MHz | 645 MHz | 657 MHz | 663 MHz | 669 MHz | 675 MHz | 681 MHz | 687 MHz | 693 MHz | 699 MHz | 705 MHz | 711 MHz | 717 MHz | 723 MHz | 825 MHz | 831 MHz | 837 MHz | 843 MHz | 350000000 |
40.0 dB | 38.8 dB | 41.0 dB | 41.0 dB | 41.2 dB | 40.0 dB | 40.0 dB | 40.2 dB | 40.3 dB | 40.5 dB | 40.6 dB | 40.2 dB | 40.4 dB | 40.1 dB | 40.1 dB | 40.0 dB | 40.0 dB | 40.1 dB | 40.2 dB | 39.4 dB | 40.4 dB | 40.4 dB | 40.3 dB | 40.5 dB | 40.5 dB | 40.6 dB | 40.9 dB | 40.8 dB | 41.4 dB | 41.4 dB | 41.0 dB | 41.0 dB | 38.4 dB |
4.2 dBmV | 1.6 dBmV | 5.8 dBmV | 5.6 dBmV | 5.7 dBmV | 4.6 dBmV | 4.6 dBmV | 4.6 dBmV | 4.8 dBmV | 5.0 dBmV | 5.0 dBmV | 4.9 dBmV | 4.9 dBmV | 4.6 dBmV | 4.5 dBmV | 4.4 dBmV | 4.1 dBmV | 4.1 dBmV | 4.2 dBmV | 4.3 dBmV | 4.2 dBmV | 4.2 dBmV | 4.2 dBmV | 4.5 dBmV | 4.6 dBmV | 4.7 dBmV | 5.4 dBmV | 5.5 dBmV | 6.4 dBmV | 6.3 dBmV | 5.9 dBmV | 5.8 dBmV | 1.9 dBmV |
256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | OFDM |
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream | Channel Bonding Value | ||
1 | 2 | 3 | 4 |
Locked | Locked | Locked | Locked |
21 MHz | 25 MHz | 32 MHz | 38 MHz |
2560 | 5120 | 5120 | 5120 |
39.8 dBmV | 41.8 dBmV | 41.3 dBmV | 43.0 dBmV |
QAM | QAM | QAM | QAM |
TDMA_AND_ATDMA | ATDMA | ATDMA | ATDMA |
IndexUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
CM Error Codewords | ||||||||||||||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
2051520743 | 2941413229 | 2941442595 | 2941464555 | 2941485415 | 2941511608 | 2941532720 | 2941550167 | 2941569542 | 2941592283 | 2941609666 | 2941630101 | 2941652115 | 2941669019 | 2941686348 | 2941702274 | 2941719536 | 2941742542 | 2941763025 | 2941784262 | 2941803184 | 2941821352 | 2941841281 | 2941858106 | 2941881720 | 2941898291 | 2941921238 | 2941943746 | 2941964600 | 2941988687 | 2941998636 | 2942001155 | 2051520743 |
1873013665 | 5771 | 102 | 69 | 40 | 528 | 280 | 293 | 287 | 231 | 277 | 255 | 172 | 190 | 204 | 183 | 124 | 149 | 87 | 136 | 161 | 215 | 200 | 160 | 205 | 1185 | 208 | 211 | 88 | 104 | 127 | 136 | 1873013665 |
105428 | 2296 | 144 | 131 | 125 | 374 | 316 | 319 | 430 | 451 | 443 | 490 | 341 | 276 | 163 | 148 | 153 | 94 | 123 | 134 | 122 | 125 | 171 | 170 | 160 | 1485 | 191 | 199 | 143 | 145 | 180 | 200 | 105428 |
System Uptime: 2 days 22h: 50m: 28s
06-03-2024 04:32 PM
@-G-I forgot to mention that I was told the node in my neighbourhood was updated a few weeks ago. The upload upgrade was not done but improvements were made.
06-04-2024 06:52 PM
My internet just disconnected 5 minutes ago and the modem was flashing green. I'm now back online but I'm wondering why my modem stats still show this: System Uptime: 4 days 1h: 19m: 29s
Why doesn't it register the disconnection?
06-04-2024 08:44 PM
@DigTV99 wrote:
My internet just disconnected 5 minutes ago and the modem was flashing green. I'm now back online but I'm wondering why my modem stats still show this: System Uptime: 4 days 1h: 19m: 29s
Why doesn't it register the disconnection?
Think of the Ignite Gateway as a small computer. The System Uptime indicates how long it has been since the Gateway got power-cycled or rebooted... and also represents how long the error counts in the stats have been accumulating.
What you just saw was the Ignite Gateway losing its connection to the Rogers network. The modem will immediately try to reconnect, and the flashing green and amber status is the modem going through its registration process.
06-04-2024 10:37 PM
@DigTV99 wrote:
@-G-I forgot to mention that I was told the node in my neighbourhood was updated a few weeks ago. The upload upgrade was not done but improvements were made.
Okay... but that just begs to ask more questions, such as:
Why are you provisioned with only 4 upstream (DOCSIS 3.0) QAM channels and no OFDMA channel? (Is there some really old legacy gear installed in your neighbourhood that would make this channel configuration unstable or problematic? Is more maintenance work required to enable your area to be upgraded to support mid-split?)
Why are you getting so many uncorrectable errors? Is this problem isolated to your line? Are your neighbours affected as well? With a DAA / R-PHY node, the RF signal path to/from your modem is terminated at your node, not in the headend. If the errors are caused by noise ingress or other RF impairments, it should be localized and easily remediated.
Why is your modem losing registration so frequently? Is it due to serious issues with the cable plant in your area? Is it due to hardware/software stability issues with your new fibre node?
Did your current stability issues coincide with your node getting upgraded?
06-05-2024 02:04 AM - edited 06-05-2024 02:06 AM
Yup, everything that @-G- said .......
I'm not as concerned about the uncorrectable codewords as their a small component of the overall codewords.
Looking at your signal stats, there's nothing to indicate an issue, and apparently the moderators have indicated that the OFDM channel stats are within acceptable parameters. As @-G- is asking, what the heck is going on, and that's being polite about this.
Ok, so, this is where it would be an idea to run a long term ping test to the CMTS. If you're going to do this, run it on your main pc, even it its connected via wifi. You might see occasional missed packets over wifi, which we won't be too concerned about, but, in the case of a complete disconnect, you'll see a series of timeouts until the modem reconnects. Using the Powershell approach, you will have timestamps to go along with the time outs. You can copy that timeout data, with timestamps and sent that to the moderators via message to @CommunityHelps. What the moderators will do with that data is a good question, but, looking at the CMTS logs for the disconnected times, should show if you're the only one with this problem or if there are other customers on your neighbourhood node who also have this problem.
You indicated that you have a Windows 7 pc that you could use. Don't do that. Windows 7 on the internet is a security hazard looking for someone to hack into it. If you're not using it at all, and there's nothing on the hard drive that you want to keep, consider loading Ubuntu onto it, which is kept up to date. Only caveat is that you have to ensure that you enable the firewall after the load. If you're curious about linux and its offshoots, loading Ubuntu is an easy first step for learning purposes.
06-05-2024 11:40 AM
I wish Rogers technical support was as thorough as you are. They provided me with the limited information that I relayed to you. Either they don't know the answers to those questions or they prefer not to share it with customers.
How many upstream channels am I supposed to have?
I asked about the uptime stat in the modem partly because I'm wondering if this is the stat that Rogers uses to determine if other modems in my area are disconnecting. If they see that modems have been connected for several days, maybe they don't realize that they are actually disconnecting for a short while.
The intermittent disconnections started on May 23, or around there. There was a fiber cut in my area in early May and updates made to the node at around the same time.
06-05-2024 11:52 AM
Ok, I have followed your instructions and I'm running a ping test to the CMTS from my main PC which is running Windows 10 & connected via wifi.
When I share the time stamps with the moderators, when they look at CMTS logs for the disconnected times, would they have the tools to check if there are other customers in my neighbourhood node also have this problem or do they have access only to the modem uptime stats?
06-05-2024 01:09 PM
@DatalinkSorry for not replying to your comment about my Windows 7 laptop. Thanks for the tip. I plan to install a lightweight linux distro such as Linux Lite, on it when I get a chance. I forgot about the vulnerabilities that Windows 7 now has. I keep this laptop around mostly because it has an ethernet port but I guess I can buy a USB to Ethernet adapter.
06-06-2024 10:51 AM
Quick update on the ping test to the CMTS; my connection has been great in the last 23 hours and the test has not shown any timeouts.
06-06-2024 04:33 PM
The great connection didn't last long. I will forward this to the mods to see if they can look into it further.
2024-06-06 4:28:02 PM - Request timed out.
2024-06-06 4:28:07 PM - Request timed out.
2024-06-06 4:28:12 PM - Request timed out.
2024-06-06 4:28:17 PM - Request timed out.
2024-06-06 4:28:22 PM - Request timed out.
2024-06-06 4:28:27 PM - Request timed out.
2024-06-06 4:28:32 PM - Request timed out.
2024-06-06 4:28:37 PM - Request timed out.
2024-06-06 4:28:42 PM - Request timed out.
2024-06-06 4:28:47 PM - Request timed out.
2024-06-06 4:28:52 PM - Request timed out.
2024-06-06 4:28:57 PM - Request timed out.
2024-06-06 4:29:02 PM - Request timed out.
2024-06-06 4:29:07 PM - Request timed out.
2024-06-06 4:29:08 PM - Reply from 10.0.0.1: Destination net unreachable.
2024-06-06 4:29:09 PM - Reply from 10.0.0.1: Destination net unreachable.
2024-06-06 4:29:14 PM - Request timed out.
2024-06-06 4:29:15 PM - Reply from 10.0.0.1: Destination net unreachable.
2024-06-06 4:29:20 PM - Request timed out.
2024-06-06 4:29:21 PM - Reply from 10.0.0.1: Destination net unreachable.
2024-06-06 4:29:26 PM - Request timed out.
2024-06-06 4:29:27 PM - PING: transmit failed. General failure.
2024-06-06 4:29:28 PM - PING: transmit failed. General failure.
2024-06-06 4:29:29 PM - PING: transmit failed. General failure.
2024-06-06 4:29:30 PM - PING: transmit failed. General failure.
2024-06-06 4:29:31 PM - PING: transmit failed. General failure.
2024-06-06 4:29:32 PM - PING: transmit failed. General failure.
2024-06-06 4:29:33 PM - PING: transmit failed. General failure.
2024-06-06 4:29:34 PM - PING: transmit failed. General failure.
2024-06-06 4:29:39 PM - Request timed out.
2024-06-06 4:29:44 PM - Request timed out.
2024-06-06 4:29:49 PM - Request timed out.
2024-06-06 4:29:54 PM - Request timed out.
2024-06-06 4:29:59 PM - Request timed out.
2024-06-06 4:30:04 PM - Request timed out.
2024-06-06 4:30:05 PM - No resources.
2024-06-06 4:30:06 PM - PING: transmit failed. General failure.
2024-06-06 4:30:07 PM - PING: transmit failed. General failure.
2024-06-06 4:30:08 PM - PING: transmit failed. General failure.
2024-06-06 4:30:09 PM - PING: transmit failed. General failure.
2024-06-06 4:30:10 PM - PING: transmit failed. General failure.
2024-06-06 4:30:11 PM - Reply from 10.0.0.1: Destination net unreachable.
2024-06-06 4:30:16 PM - Request timed out.
2024-06-06 4:30:21 PM - Request timed out.
2024-06-06 4:30:26 PM - Request timed out.
2024-06-06 4:30:31 PM - Request timed out.
2024-06-06 4:30:36 PM - Request timed out.
2024-06-06 4:30:41 PM - Request timed out.
2024-06-06 4:30:46 PM - Request timed out.
2024-06-06 4:30:47 PM - Reply from 99.252.52.1: bytes=32 time=18ms TTL=63
2024-06-06 4:30:48 PM - Reply from 99.252.52.1: bytes=32 time=15ms TTL=63
2024-06-06 4:30:49 PM - Reply from 99.252.52.1: bytes=32 time=12ms TTL=63
06-06-2024 04:42 PM - edited 06-06-2024 06:08 PM
Yup, thats what we're looking for. Now, its on the moderators or network engineering staff to look at the CMTS and neighbourhood node records to see what was going on at that time.
I've never seen a "PING: transmit failed. General failure". Interesting .....
Did the connection just drop, or were there any high time pings that occurred just before the drop? Just wondering if there's anything evident leading up to the drop?
06-06-2024 06:07 PM
The connection dropped and the pings were very good right before that. So far this week, I'm getting less disconnections than the previous week but it seems that there is still a problem. I'm not sure if Rogers will deem 1-2 disconnections a day as a problem though.
06-06-2024 06:10 PM - edited 06-06-2024 06:10 PM
It shouldn't drop at all. The question is, are you the only one seeing this or is it restricted to you and your neighbourbours or is it a wider problem? Someone will have to dig into the records to see just how many customers are affected, which includes Rogers and other TPIA customers.
I would keep that test running. Let it run for days if you're willing to do that. Every once in a while you can copy the text file using File Manager and paste it into the same directory, it will paste in as a "Copy of ....." or paste it into a different folder. You don't have to stop the test to copy the file. When that's parked somewhere, you can use Word (??) or Notepadd++ to peruse the file. It would be work searching thru the file, looking for overnight disconnects.
06-06-2024 06:14 PM
I can let it run for a few more days. I generally like to shut my PC down at night but I will leave this running.
I'm using Notepad ++ as you recommended and I'm using Ctrl F to find instances of Request timed out. I spotted one early this morning but ever since I switched to Rogers, I've noticed disconnections at around 3am every day in my router's logs. I removed my router from the equation for now while I try to resolve this problem but it looks like the daily disconnections at that time are still happening. Apparently, these are normal as many people have reported this.
2024-06-06 3:37:43 AM - Request timed out.
2024-06-06 3:37:48 AM - Request timed out.
2024-06-06 3:37:49 AM - PING: transmit failed. General failure.
2024-06-06 3:37:50 AM - PING: transmit failed. General failure.
2024-06-06 3:37:51 AM - PING: transmit failed. General failure.
2024-06-06 3:37:52 AM - PING: transmit failed. General failure.
2024-06-06 3:37:53 AM - PING: transmit failed. General failure.
2024-06-06 3:37:54 AM - PING: transmit failed. General failure.
06-07-2024 03:26 PM
Today I'm seeing something different. There haven't been any disconnections but there has been a lot of packet loss. In the ping test, there are a lot of single line Request timed out entries that go back to normal after 6 seconds. One online multiplayer game that I play was unplayable due to latency.
I'm reposting my stats. Uncorrectable codewords went from around 190,000 as of last night to around 300,000. What is an acceptable amount? Is it a percentage of the Unerrored Codewords? When Correctable Codewords are very high, is that a sign of a problem?
IndexLock StatusFrequencySNRPower LevelModulation
23 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
693 MHz | 279 MHz | 849 MHz | 855 MHz | 861 MHz | 579 MHz | 585 MHz | 591 MHz | 597 MHz | 603 MHz | 609 MHz | 615 MHz | 621 MHz | 633 MHz | 639 MHz | 645 MHz | 651 MHz | 657 MHz | 663 MHz | 669 MHz | 675 MHz | 681 MHz | 687 MHz | 699 MHz | 705 MHz | 711 MHz | 717 MHz | 723 MHz | 825 MHz | 831 MHz | 837 MHz | 843 MHz | 350000000 |
40.2 dB | 39.0 dB | 40.9 dB | 40.9 dB | 41.1 dB | 40.0 dB | 40.0 dB | 40.1 dB | 40.2 dB | 40.3 dB | 40.3 dB | 40.0 dB | 40.3 dB | 40.0 dB | 40.0 dB | 39.9 dB | 39.8 dB | 39.8 dB | 40.1 dB | 40.1 dB | 39.7 dB | 40.3 dB | 40.3 dB | 40.4 dB | 40.6 dB | 40.5 dB | 40.8 dB | 40.7 dB | 41.3 dB | 41.2 dB | 40.9 dB | 40.8 dB | 38.5 dB |
4.6 dBmV | 2.6 dBmV | 5.9 dBmV | 5.8 dBmV | 5.9 dBmV | 5.0 dBmV | 5.0 dBmV | 5.0 dBmV | 5.1 dBmV | 5.2 dBmV | 5.2 dBmV | 5.1 dBmV | 5.0 dBmV | 4.6 dBmV | 4.5 dBmV | 4.5 dBmV | 4.3 dBmV | 4.2 dBmV | 4.3 dBmV | 4.4 dBmV | 4.6 dBmV | 4.5 dBmV | 4.5 dBmV | 4.8 dBmV | 4.9 dBmV | 5.0 dBmV | 5.5 dBmV | 5.6 dBmV | 6.6 dBmV | 6.5 dBmV | 6.1 dBmV | 5.9 dBmV | 2.6 dBmV |
256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | OFDM |
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream | Channel Bonding Value | ||
1 | 2 | 3 | 4 |
Locked | Locked | Locked | Locked |
21 MHz | 25 MHz | 32 MHz | 38 MHz |
2560 | 5120 | 5120 | 5120 |
37.3 dBmV | 39.3 dBmV | 39.5 dBmV | 39.3 dBmV |
QAM | QAM | QAM | QAM |
TDMA_AND_ATDMA | ATDMA | ATDMA | ATDMA |
IndexUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
CM Error Codewords | ||||||||||||||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
2928461064 | 1246521718 | 1246563741 | 1246599475 | 1246628067 | 1246666124 | 1246694314 | 1246720522 | 1246740478 | 1246774823 | 1246846061 | 1246875845 | 1246900362 | 1246889507 | 1246939275 | 1246960148 | 1246984330 | 1247011845 | 1247038999 | 1247065995 | 1247132008 | 1247159650 | 1247184753 | 1247208417 | 1247242834 | 1247267836 | 1247295039 | 1247327509 | 1247349570 | 1247385056 | 1247408845 | 1247410290 | 2928461064 |
2558589138 | 6309 | 287 | 277 | 192 | 853 | 675 | 593 | 576 | 626 | 666 | 519 | 489 | 438 | 444 | 467 | 393 | 459 | 397 | 476 | 419 | 543 | 570 | 428 | 556 | 1516 | 450 | 643 | 344 | 359 | 417 | 401 | 2558589138 |
306591 | 3751 | 542 | 407 | 381 | 920 | 901 | 951 | 1065 | 1071 | 1073 | 1139 | 962 | 905 | 680 | 594 | 504 | 321 | 382 | 430 | 510 | 474 | 512 | 653 | 655 | 2011 | 705 | 730 | 519 | 463 | 544 | 602 | 306591 |
06-07-2024 08:03 PM
I'm getting a lot of packet loss & jitter when pinging CMTS but not when pinging 10.0.0.1. What does this indicate?
CMTS
10.0.01
06-11-2024 04:35 PM - edited 06-11-2024 06:31 PM
@Datalink @-G- My connection has been pretty good but I was disconnected again about 15 minutes ago.
2024-06-11 4:12:35 PM - Reply from 99.252.52.1: bytes=32 time=17ms TTL=63
2024-06-11 4:12:36 PM - Reply from 99.252.52.1: bytes=32 time=12ms TTL=63
2024-06-11 4:12:37 PM - Reply from 99.252.52.1: bytes=32 time=15ms TTL=63
2024-06-11 4:12:42 PM - Request timed out.
2024-06-11 4:12:47 PM - Request timed out.
2024-06-11 4:12:52 PM - Request timed out.
2024-06-11 4:12:57 PM - Request timed out.
2024-06-11 4:13:02 PM - Request timed out.
2024-06-11 4:13:07 PM - Request timed out.
2024-06-11 4:13:12 PM - Request timed out.
2024-06-11 4:13:17 PM - Request timed out.
2024-06-11 4:13:22 PM - Request timed out.
2024-06-11 4:13:27 PM - Request timed out.
2024-06-11 4:13:32 PM - Request timed out.
2024-06-11 4:13:37 PM - Request timed out.
2024-06-11 4:13:42 PM - Request timed out.
2024-06-11 4:13:47 PM - Request timed out.
2024-06-11 4:13:48 PM - PING: transmit failed. General failure.
2024-06-11 4:13:49 PM - PING: transmit failed. General failure.
2024-06-11 4:13:50 PM - PING: transmit failed. General failure.
2024-06-11 4:13:51 PM - PING: transmit failed. General failure.
2024-06-11 4:13:56 PM - Request timed out.
2024-06-11 4:14:01 PM - Request timed out.
2024-06-11 4:14:06 PM - Request timed out.
2024-06-11 4:14:11 PM - Request timed out.
2024-06-11 4:14:16 PM - Request timed out.
2024-06-11 4:14:21 PM - Request timed out.
2024-06-11 4:14:26 PM - Request timed out.
2024-06-11 4:14:31 PM - Request timed out.
2024-06-11 4:14:36 PM - Request timed out.
2024-06-11 4:14:41 PM - Request timed out.
2024-06-11 4:14:46 PM - Request timed out.
2024-06-11 4:14:51 PM - Request timed out.
2024-06-11 4:14:52 PM - Reply from 99.252.52.1: bytes=32 time=388ms TTL=63
2024-06-11 4:14:53 PM - Reply from 99.252.52.1: bytes=32 time=25ms TTL=63
2024-06-11 4:14:54 PM - Reply from 99.252.52.1: bytes=32 time=17ms TTL=63
2024-06-11 5:20:11 PM - Reply from 99.252.52.1: bytes=32 time=13ms TTL=63
2024-06-11 5:20:12 PM - Reply from 99.252.52.1: bytes=32 time=13ms TTL=63
2024-06-11 5:20:17 PM - Request timed out.
2024-06-11 5:20:22 PM - Request timed out.
2024-06-11 5:20:27 PM - Request timed out.
2024-06-11 5:20:32 PM - Request timed out.
2024-06-11 5:20:37 PM - Request timed out.
2024-06-11 5:20:38 PM - Reply from 99.252.52.1: bytes=32 time=14ms TTL=63
2024-06-11 5:20:39 PM - Reply from 99.252.52.1: bytes=32 time=13ms TTL=63
2024-06-11 5:20:44 PM - Request timed out.
2024-06-11 5:20:45 PM - Reply from 99.252.52.1: bytes=32 time=15ms TTL=63
2024-06-11 5:20:46 PM - Reply from 99.252.52.1: bytes=32 time=13ms TTL=63
2024-06-11 5:38:57 PM - Reply from 99.252.52.1: bytes=32 time=11ms TTL=63
2024-06-11 5:38:58 PM - Reply from 99.252.52.1: bytes=32 time=12ms TTL=63
2024-06-11 5:39:03 PM - Request timed out.
2024-06-11 5:39:08 PM - Request timed out.
2024-06-11 5:39:13 PM - Request timed out.
2024-06-11 5:39:18 PM - Request timed out.
2024-06-11 5:39:23 PM - Request timed out.
2024-06-11 5:39:28 PM - Request timed out.
2024-06-11 5:39:33 PM - Request timed out.
2024-06-11 5:39:38 PM - Request timed out.
2024-06-11 5:39:43 PM - Request timed out.
2024-06-11 5:39:48 PM - Request timed out.
2024-06-11 5:39:53 PM - Request timed out.
2024-06-11 5:39:54 PM - Reply from 10.0.0.1: Destination net unreachable.
2024-06-11 5:39:55 PM - Reply from 10.0.0.1: Destination net unreachable.
2024-06-11 5:40:00 PM - Request timed out.
2024-06-11 5:40:05 PM - Request timed out.
2024-06-11 5:40:10 PM - Request timed out.
2024-06-11 5:40:15 PM - Request timed out.
2024-06-11 5:40:20 PM - Request timed out.
2024-06-11 5:40:25 PM - Request timed out.
2024-06-11 5:40:30 PM - Request timed out.
2024-06-11 5:40:35 PM - Request timed out.
2024-06-11 5:40:40 PM - Request timed out.
2024-06-11 5:40:45 PM - Request timed out.
2024-06-11 5:40:50 PM - Request timed out.
2024-06-11 5:40:55 PM - Request timed out.
2024-06-11 5:41:00 PM - Request timed out.
2024-06-11 5:41:01 PM - No resources.
2024-06-11 5:41:02 PM - PING: transmit failed. General failure.
2024-06-11 5:41:03 PM - PING: transmit failed. General failure.
2024-06-11 5:41:04 PM - PING: transmit failed. General failure.
2024-06-11 5:41:05 PM - PING: transmit failed. General failure.
2024-06-11 5:41:06 PM - PING: transmit failed. General failure.
2024-06-11 5:41:11 PM - Request timed out.
2024-06-11 5:41:16 PM - Request timed out.
2024-06-11 5:41:17 PM - Reply from 99.252.52.1: bytes=32 time=11ms TTL=63
2024-06-11 5:41:18 PM - Reply from 99.252.52.1: bytes=32 time=12ms TTL=63
2024-06-11 5:41:19 PM - Reply from 99.252.52.1: bytes=32 time=16ms TTL=63
I haven't had an update from the moderators yet so I sent them another message with this log. When I was disconnected, I checked the modem and it was flashing green. My previous disconnection happened at around the same time. I wonder if Rogers is doing work in the area at this time.
edit: added 2 more logs of disconnections.
06-11-2024 06:34 PM
I'm posting my latest modem stats as I might reboot my modem to see if anything improves.
System Uptime: 11 days 1h: 1m: 23s
IndexLock StatusFrequencySNRPower LevelModulation
Downstream | Channel Bonding Value | |||||||||||||||||||||||||||||||
23 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
693 MHz | 279 MHz | 849 MHz | 855 MHz | 861 MHz | 579 MHz | 585 MHz | 591 MHz | 597 MHz | 603 MHz | 609 MHz | 615 MHz | 621 MHz | 633 MHz | 639 MHz | 645 MHz | 651 MHz | 657 MHz | 663 MHz | 669 MHz | 675 MHz | 681 MHz | 687 MHz | 699 MHz | 705 MHz | 711 MHz | 717 MHz | 723 MHz | 825 MHz | 831 MHz | 837 MHz | 843 MHz | 350000000 |
40.1 dB | 38.6 dB | 41.0 dB | 40.9 dB | 41.3 dB | 39.9 dB | 40.0 dB | 40.1 dB | 40.2 dB | 40.3 dB | 40.3 dB | 40.0 dB | 40.3 dB | 40.1 dB | 39.9 dB | 40.0 dB | 39.9 dB | 39.8 dB | 40.0 dB | 40.1 dB | 39.4 dB | 40.1 dB | 40.2 dB | 40.4 dB | 40.4 dB | 40.4 dB | 40.7 dB | 40.7 dB | 41.3 dB | 41.3 dB | 40.9 dB | 40.9 dB | 38.3 dB |
4.4 dBmV | 1.7 dBmV | 6.3 dBmV | 6.1 dBmV | 6.2 dBmV | 4.9 dBmV | 4.9 dBmV | 4.8 dBmV | 5.0 dBmV | 5.1 dBmV | 5.2 dBmV | 5.2 dBmV | 5.2 dBmV | 4.9 dBmV | 4.8 dBmV | 4.7 dBmV | 4.5 dBmV | 4.4 dBmV | 4.3 dBmV | 4.4 dBmV | 4.5 dBmV | 4.4 dBmV | 4.4 dBmV | 4.6 dBmV | 4.8 dBmV | 4.9 dBmV | 5.5 dBmV | 5.7 dBmV | 6.6 dBmV | 6.5 dBmV | 6.2 dBmV | 6.2 dBmV | 1.8 dBmV |
256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | OFDM |
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream | Channel Bonding Value | ||
1 | 2 | 3 | 4 |
Locked | Locked | Locked | Locked |
21 MHz | 25 MHz | 32 MHz | 38 MHz |
2560 | 5120 | 5120 | 5120 |
41.8 dBmV | 42.5 dBmV | 43.5 dBmV | 43.8 dBmV |
QAM | QAM | QAM | QAM |
TDMA_AND_ATDMA | ATDMA | ATDMA | ATDMA |
IndexUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
CM Error Codewords | ||||||||||||||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
1019401519 | 214352729 | 214393545 | 214454560 | 214505732 | 214549780 | 214599401 | 214636197 | 214671260 | 214723370 | 214810412 | 214848301 | 214884515 | 214883552 | 214936375 | 214963496 | 214998035 | 215034340 | 215069968 | 215109494 | 215183559 | 215219988 | 215261929 | 215291296 | 215339223 | 215380773 | 215417533 | 215459248 | 215492168 | 215540019 | 215590050 | 215574582 | 1019401519 |
518412851 | 7322 | 533 | 511 | 324 | 1281 | 1068 | 1010 | 1022 | 1041 | 1125 | 910 | 924 | 907 | 835 | 801 | 735 | 758 | 575 | 788 | 704 | 902 | 920 | 765 | 964 | 2044 | 926 | 1192 | 664 | 679 | 714 | 705 | 518412851 |
955282 | 6004 | 929 | 681 | 624 | 1454 | 1513 | 1562 | 1727 | 1891 | 1819 | 1795 | 1712 | 1456 | 1099 | 827 | 686 | 468 | 652 | 650 | 732 | 714 | 782 | 1079 | 1073 | 2477 | 1163 | 1255 | 937 | 825 | 1044 | 1059 | 955282 |
07-03-2024 09:40 PM - edited 07-03-2024 09:42 PM
Quick update in case anyone else is having similar problems. A Rogers technician tested my inside and outside cables last week and found that the inside cable seemed fine but the outside cable did not carry a steady signal. He replaced the outside cable from the pole to the side of my home. He showed me how the old cable was damaged.
A couple of hours later, my internet disconnected. I rebooted my modem and after that, I noticed that I was getting a lot less uncorrectable codewords. For almost 4 days there were no disconnections but on the 4th day, there were 2 more disconnections.
That was 2 days ago and I haven't been disconnected since. I don't think the problem has been resolved entirely but for the last week, the connection seems more stable and does not disconnect as often. I'm guessing that there is a problem in my area or maybe something is not right at the node. The cable that was replaced was the problem but it seems there are other factors as well.