I signed up the $45 plan in September, got a cgn3u modem, internet connection was great.
A couple of weeks ago, used my wife's name, signed up the $37.5 plan, got a coda4582u. I put the modem in bridge mode, overall the internet connection is good, but I have this annoying problem, everyday I experience one internet disconnect, normally it lasts a couple of minutes, it may last around 5 minutes, then the connection comes back as normal, I do not need to reboot the modem, and I do not need to renew connection on my router. No events on the coda shows it reboots or anything else, and nothing shows in my router log.
To be more precise, during the short disconnect time, the connection is not completely gone, I may be able to load a page using a browser, then fails to load other pages.
Is this a common issue for coda3582u modem? The modem has firmware vesion 188.8.131.52.
Update: As of Feb-11 this early morning, Rogers/Fido users (including myself) have noticed that the OFDM/OFDMA has been disabled across the board. Good news as it should help with the random disconnect. Fingers crossed.
I'm new and Fido has issued me a CGN3U modem. Has anyone found that when running in bridge mode the connection drops more frequently due to some sort of DHCP error between the modem and your router? I have reverted to using my GNC3 modem in routed with my Asus router downstream and the DHCP errors have been eliminated. (This requires me to forward a few ports in the modem and use double NAT.) I find that the modem does drop its WAN connection about once or twice a day and it takes about a minute or so to restore itself. Is this normal?
I have the CODA modem. I had it on bridge mode before but had to switch back to gateway mode to connect with my home router. Despite now it's doing double-nat but with port forwarding setup, my Xbox is not complaining. Few reasons that I had to switch back from bridge mode: a) for some reason it's higher latency (ping time) while on bridge mode with Speedtest. b) Time on my CODA is no longer updated from network and time started to drift, off by a couple minutes. c) Fido/Rogers tech support pretty much didn't want to support me due to "lack of logs" on the modem while it's on bridge mode. Regarding drops of connections, it didn't seem to make any difference whether on gateway or bridge mode. In my case they both have 20-30 second random drops.
I have the same issue as described here. Unfortunately I don't have a resolution to this problem and neither does Fido tech support. I am thinking it's something to do with the Fido/Rogers network or equipment. I am very close to switching to another provider if they can't fix it.
As OP @mglen has mentioned, the issue has been widely discussed: https://communityforums.rogers.com/t5/Internet/Internet-Keeps-Dropping/td-p/454580/page/60
In my case, the disconnects usually lasted up to 20 seconds (always at bad time when I was in important conference calls and kicked me out). Randomly happened twice a day or once every other day. Some how it's been okay (no drops) for the last 3 days. I run one-second interval pings around the clock so I know when it dropped. Fido/Roger mysteriously dropped my WAN connection for exactly 5 minutes this early morning at 5:55am, so I counted that as a "maintenance". I am watching closely of my network if the random drops happen again.
Disappointed to report, a drop of 24 seconds has happened tonight (Jan 19). Glad I wasn't but if I were in any real-time sessions like voice/video calls, would have dropped my session.
drop : Tue Jan 19 18:34:00 2021
recover: Tue Jan 19 18:34:24 2021
In conclusion, the random disconnects/interruptions did not go away and therefore I cannot have my important voice/video calls run over this Fido cable internet line, since it is deemed unreliable.
Thanks for the update @mglen,
A modem swap is offered when the modem itself is faulty.
If our technical support team confirmed that the disconnect is not model related. Have you had the chance to try connecting your devices directly to our modem without having to use your router as a bridge?
Another suggestion would be to connect your computer with an Ethernet cable directly to our modem and test it for a few days. Hope this helps, and let us know how it goes.
When the modem was in bridge mode, I did add a comupter directly to another port on the modem while my router was still connected to one port on the modem.
I ran same network monitoring scripts on this computer and another computer that's behind the router. Both computers recorded network hiccups at same time. So the hiccups are definitely not related to my router, either the modem has a problem, or Fido network has a problem. A traceroute probably will tell if it's modem problem or network problem and where the network problem is.
Just got a hiccup around 930pm, this is the traceroute looks like:
traceroute to 184.108.40.206 (220.127.116.11), 30 hops max, 60 byte packets
1 unknown (192.168.64.1) 0.175 ms 0.104 ms 0.102 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * dns.google (18.104.22.168) 16.831 ms
A normal traceroute looks like this:
traceroute to 22.214.171.124 (126.96.36.199), 30 hops max, 60 byte packets
1 unknown (192.168.64.1) 0.217 ms 0.128 ms 0.182 ms
2 unallocated-static.rogers.com (188.8.131.52) 18.277 ms 20.746 ms 26.146 ms
3 184.108.40.206 (220.127.116.11) 26.145 ms 26.102 ms 26.114 ms
4 0-5-0-8-cgw01.bloor.rmgt.net.rogers.com (18.104.22.168) 27.676 ms 22.214.171.124 (126.96.36.199) 27.665 ms 0-15-0-8-cgw01.bloor.rmgt.net.rogers.com (188.8.131.52) 27.587 ms
5 184.108.40.206 (220.127.116.11) 26.038 ms 26.132 ms 26.089 ms
6 18.104.22.168 (22.214.171.124) 25.753 ms 126.96.36.199 (188.8.131.52) 25.145 ms 24.944 ms
7 184.108.40.206 (220.127.116.11) 25.166 ms 18.104.22.168 (22.214.171.124) 15.603 ms 126.96.36.199 (188.8.131.52) 21.109 ms
8 dns.google (184.108.40.206) 23.901 ms 220.127.116.11 (18.104.22.168) 21.835 ms dns.google (22.214.171.124) 23.652 ms
first hop is my router's internal ip, second hop in second traceroute 126.96.36.199 is the fido/rogers gateway, does the fact that it did not show up in the 1st traceroute suggest the hiccup is a modem, local node or gateway issue?
Based on info from https://communityforums.rogers.com/t5/Internet/Internet-Keeps-Dropping/td-p/454580, tech support could not help much.
I noticed my modem's OFDMA channel was disabled today. Based on the above link, the short disconnect is upstream issue, likely caused by Rogers/Fido enabling upstream OFDMA channel, if this is the case, now my modem's OFDMA channel is disabled, the issue should go away. I got one samll hiccup at 8:08 today in the morning, it lasted only about 2 minutes. I'll see how this goes in the next few days.
Is Rogers/Fido rolling back the OFDMA change temporarily to get around the disconnect issue? downdetector.ca reported much less issues tonight for Rogers comparing to previous nights and even this morning.
It's been 72 hours since last hiccup. It looks like disabling upstream OFDMA(dark blue upstream light) by Fido/Rogers fixed the random disconnect issue.
When will it be enabled again? Wish some transparency from Fido/Rogers regarding to network change.