I can't speak for anyone else, but I'm not in bridge mode and have my PC directly connected to the modem. It's incredibly annoying and isn't what I'm paying for.
At this point in time I really, really don't believe that its a case of intentional throttling. All of the evidence that I've seen so far points to a protocol issue with the Puma series modems. Another poster noted that he was on Start, using a non-Puma modem and didn't have any issues, and that was with a service that used the Rogers network. So, this can work, on Rogers network, with a non-Puma modem. Its really unfortunate that Rogers doesn't offer such a modem as that could instantly indicate whether or not the problem is with the Puma series modems or not.
So, I'm not saying that the issue of a possible violation of net neutrality is inappropriate. I just don't believe that its the case here. But, I am absolutely willing to look at any evidence that indicates otherwise.
As I've indicted elsewhere, testing consumer modems is sorely lacking, personal opinion. That includes testing all of the various protocols that are legal for use, as indicated by their respective RFCs. That should be done by Intel before the modem is ever released for manufacturing. That would avoid situations such as this, or, personal opinion, it should avoid situations such as this. Should and would are two completely different concepts here.
Just to note, the days of a simple modem are long passed. These days, DOCSIS modems do a lot more than one would think.
Just thought I'd chime in - when I last posted some time ago, the issue had completely vanished. It's back again, and very annoying. Not going to bother with any other details as the symptoms and hardware are identical to so many other cases in this thread.
Not sure why it worked fine for the couple months or so or why it just came back sometime last week. If there were two firmware updates in that time frame it might make sense. Otherwise I'm not sure what's going on. I haven't changed anything on my end.
Just wanna put it out there.
CODA modem - Bitrate drops to 0
CODA + Router - Bitrate stopped dropping
Checked this multiple times and this was my issue.
But now I have another issue where I just get low speeds but not to 0.
Tech support always says its a node problem in the area and it's been months and haven't fixed it, they've closed the ticket multiple times without fixing it, every time I call them, they just open a ticket and tell me it's gonna be fixed in 24-48 hours.
Rogers is honestly a joke.
Can some twitch streamers using any of the CGN3xxx modems, CGNM-3552, and CODA-4582 modem in Gateway mode give this a go please. Same goes for anyone running any of those modems in Bridge mode with a router behind it. The following instructions apply to Gateway mode, but can also be used as a guide for any router that is in use.
1. Disable IPV6 in the modem. Log into the modem, navigate to the BASIC .... GATEWAY FUNCTION tab and change the Router Mode from Dual (Stack) setting to IPV4 only. Save the change. The modem will usually take a couple of minutes to switch to IPV4 only mode. Reboot the modem anyway please: ADMIN .... DEVICE RESET ..... Reboot.
2. While the modem is rebooting, reboot the pc as well.
3. When the modem reboot is complete, log back into the modem and assign a static address to the pc or laptop that you are using. Navigate to BASIC .... LAN Setup .... DHCP Reservation. When the LAN IP reservation is complete, reboot the modem, ADMIN .... DEVICE RESET .... Reboot.
4. After the reboot, set the port forwarding required for Twitch. Navigate to BASIC .... PORT FORWARDING and set up port forwarding to the previously mentioned pc or laptop with ports:
443: TCP & UDP
5. Reboot the modem: ADMIN ..... DEVICE RESET .... Reboot.
I'd like to know if there is any difference with IPV6 disabled and the ports set for forwarding.
If this doesn't work, go back and undo the port forwarding and DHCP reservation. Reboot the modem: ADMIN ..... DEVICE RESET .... Reboot. I don't want users to leave the port forwarding setting enabled unless you can see that this instruction sequence actually works. Even then, after any streaming is complete, you should disable the port forwarding to protect the pc when its in use for other purposes.
So it appears that since I have the modem set in bridge mode with gateway disabled, I actually can't go back to modem menu without doing a factory reset, which doesn't seem like a prudent thing to do.
Ok, to log into the modem, use 192.168.100.1 as the login address. That will normally work for both Gateway and Bridge modes. Resetting the modem back to Gateway by using the UI will return the modem to Gateway mode with its previous settings intact. Using the Factory reset will completely reset the modem back to default settings. 192.168.100.1 will normally work thru the router, but there have been a few cases where a routing rule is required to access the modem thru the router.
If you're running the modem in Bridge mode, don't worry about setting the modem back to Gateway mode, unless you really want to try it. At this point, disable IPV6 in the router if you have it running and add the two ports for port forwarding. Reboot the router and pc to see what effect if any there is on streaming to Twitch.
Edit; What router are you using?