It is been 1 month of Rogers 500u internet and it has been a very frustrating experience. Had 3 modem changes and 4 tech visits. First 2 times the modem probably was a refurbished modem and finally after demanding a new one they gave a brand new modem.
The less the said about the technicians the better. All they did was check signal strenght and add Spliterrs and atenuators. None of them were capable of resolving the issue.
Finally after some analysis of what the techs we're trying I moved the modem from basement close to fibre point to upper level in the house and internet has been steady for last 24 hrs. I am wondering does having the modem too close to fibre outlet could be the cause of instability?
Welcome to the Rogers Community Forums!
Thank you for sharing your Internet experience with the Community. Unstable Internet can surely be bothersome. Were you experiencing unstable Internet over a WiFi connection?
The modem being in the basement may result in poor WiFi experience due to various reasons in the top floors of the house.
Please provide us with more details about the issue so that the Community can chime in.
The WIFI coverage was good, however, the modem would lose internet connection ever so often from the basement location. So far after moving the modem upstairs , the internet has not disconnected.
Does the distance from fibre outlet have something to do with the unstable connection. Thats the only meaningful change i have done since the last tech visit and replace of modem.
Although I'm disappointed to hear that your experience with us started off poorly, I am glad to hear that moving the modem to a higher floor seems to have stabilized it for the time being. Hopefully, we don't see any further issues going forward!
Typically, having your modem in close proximity to a fibre outlet should not cause any disruption to your internet signal. It could be as RogersMoin suggested, something environmental that is interfering with the signal from the basement to the other areas of your home. For example, electronic devices emitting their own signals or even certain building materials or furniture can sometimes be a factor in signal loss or disruption.
If you can please keep an eye on things for now and let the Community know if anything changes, that would be great!
The internet was stable for 2 days and since the weekend the problems have restarted.
Every few hours or so i lose internet connection. All lights on the modem are they way they are supposed to be when the connection is good.
When i restart of the modem it takes a long while for WAN DHCP initialization process. This sometimes takes 15 to 20 min before internet is back
@Rogers Please provide guidance on how my issue can be resolved. I am pretty close to moving to another provider unless my internet is more stable.
Oh no! We were hoping the modem re-location to a more central area in the home would help to resolve this issue. Since that is not the case we'll really need to investigate further to see what is going on and review the notes on your file to see what has been done by the technicians on site.
Please send us a Private Message to @CommunityHelps so we can gather your information and get started on this for you. If you are not familiar with our Private Messaging system please check out our Blog.
We look forward to your message!
Terrible first hop connectivity ruining all online experiences
We have the 500u package. We moved into our place in June, and since then we've been seeing lag and rubberbanding in online games. Usually it's just a small hiccup and doesn't last, so we shrug it off, but for the last month or so now, we've been seeing absolutely terrible connectivity to basically every service we use.
Games, including Final Fantasy XIV, Path of Exile, Destiny 2, RIFT, Overcooked 2.
Streaming services such as YouTube and Netflix.
Teleconferencing services such as WebEx, Microsoft Teams, and Skype for Business.
All of these have become pretty much unusable in the last month or so, which has led to some serious difficulties as I'm a consultant who works from home. Not being able to take conference calls isn't exactly great for my career.
Anyway, moving on. The first hop out of my house has the IP 18.104.22.168. As far as I can tell, it's a Casa CMTS. This node likes to either drop packets (on really bad days) or simply take its sweet time responding. In online games, this gives me lag spikes lasting up to five seconds or even leading to disconnects. In streaming services - particularly Netflix - this means dropping from 1080p to potato quality repeatedly in the span of even a 20 minute show. In Skype, it means not hearing people, or hearing people chopped up and robotic-sounding.
So, what have we done about it? I've contacted Rogers a few times. They always say signal strength looks good and nothing is wrong. That's as far as it ever goes. They sent a tech out two weeks who slapped a Return Path Attenuator on the connection to my modem (which isn't where that should go, by the way - it should be at the tap) to bring down my upstream signal strength. Signals on my downlink connections run from about 3.5 to 8 dBmV, and before the attenuator, about 36-37 dBmV upstream, which is now down to about 27-29. Needless to say, none of this has helped. In fact, this week has been worst of all. Signal-to-Noise ratios always seem to be pretty good, hovering around 36-37.
I spoke with a Rogers tech today, and their recommendation was to get a new modem. I went out and picked up another one, same as my previous model (CODA-4582U). This modem, after I factory reset it and switched it into Bridged mode, is just as bad as the previous one. It doesn't seem worse, but it's not better, either.
I have tried running in Bridged and in Router mode. I have tried connecting directly to my PC (Win10), my work laptop (Win7), my personal laptop (Kubuntu), and my wife's PC (Win10) in both of these modes. I've tried wireless and wired, but mostly wired.
The tap in my back yard is rickety and beat up. It's a 4-port tap, which was completely consumed by unmarked connections when the tech came to set us up. He threw a splitter on to one of the connections, and connected us to that. I was worried about this from the get-go, but he told me that if there were connection issues, Rogers would send a team out to replace the 4-port tap with an 8-port tap, but it seems Rogers is rather hesitant to do this. I don't know what the lines on that tap are doing; perhaps one of them is what's causing interference for my line. Who knows?
Here's a PingPlotter diagram of me hitting the CMTS as I write this post. You can see an almost rhythmic pattern to the ping spikes, and I've been seeing this pattern for the last month. https://imgur.com/xEnZYau
What do I do from here? I like the service Rogers offers, and I'd really like to get back to actually being able to use said service.
@Elestriel, I don't have much time tonight to address this, but, just to point out, your pingplot is not an issue. Those high return times from the CMTS are only from the CMTS and do not affect anything beyond the CMTS. That issue of high return times was introduced in firmware version 22.214.171.124, and its remained ever since. We're now on version 126.96.36.199T6.
What those high return times do is ruin a very simple latency test, modem to CMTS and back again. Don't know if its ever going to be fixed. What doesn't change is packet loss. If you have packet loss issues, that is how you detect it. Run a ping test to the CMTS. In this case you can drop the time down to 1 second or less. Pingplotter allows you to overwrite the ping interval in the upper right hand corner. The normal response time from the CMTS is in the 10 to 13 milli-second range. If you drop the ping interval down to 0.1 seconds or less, you will see more high time returns.
So, since you're on an unlimited account, I'd recommend running a ping test at 1 second intervals or less, to the CMTS. Let that run for 24 hours. With Pingplotter, you will probably see packet loss in the 0.1 to 0.3 % range. Running a command line test should result in losses in the 0.1 % range or less. The packet losses will show up in red.
As for actual latency, with the CMTS out of the running for test purposes, the next best target is Rogers DNS. Ping one of the following IPV4 and IPV6 addresses for latency test purposes. I'd recommend 1 second intervals for now.
Rogers IPV4 DNS:
Rogers IPV6 DNS
Primary IPv6 DNS:
Secondary IPv6 DNS:
Pingplotter and the 4582 modem don't play nice together. As a result, Pingplotter will display false packet loss indications:
1. If you ping the modem, you should not see any packet loss; and
2. If you ping the CMTS, Pingplotter will display false packet loss from the modem; and
3. If you ping some target beyond the CMTS, Pingplotter will display false packet loss from both Modem and CMTS.
4. To confirm any packet loss that is observed with Pingplotter for the end target, run a command line ping test. If you don't see any packet loss with a command line ping test, then Pingplotter's packet loss was a false indication.
To run any test looking for packet loss and latency, the order that I recommend is:
1. Ping the modem at a high rate looking for latency and packet loss. Don't be afraid to ping the modem at a very high rate, drop the interval down to 0.05 seconds or so. The data on the plot will be averaged when you use higher plot times, 5 min or above. See the linked post below regarding this issue. Ping the modem for at least an hour, preferably when their isn't anything going on with the ethernet or wifi networks. You can use both IPV4 and IPV6 addresses for the modem.
2. Ping the CMTS at 1 second intervals, looking for packet loss. Ignore the high return times as their meaningless. You can use both IPV4 and IPV6 addresses for the CMTS.
3. Ping the DNS with 1 second intervals, looking for both latency and packet loss. The typical response time will be in the 10 to 13 milli-second range and your packet loss with Pingplotter should be in the 0.1 to 0.2 % range.
Pinging the DNS allows you to look beyond the CMTS and stay within the Rogers network, where you'll see the lowest return times and packet loss numbers. When you go beyond the Rogers network, all bets are off as you cross ISP boundaries and run into congestion on other networks. But, by running testing internally within the Rogers network, that allows users to understand what the modem and Rogers network is capable of.
What this doesn't cover is the issue of peering with and routing to other networks, both of which are black holes as far as I'm concerned. There has never been any discussion in the forum regarding either subject, which is unfortunate as it would probably generate much discussion between the customers and the network engineering staff.
Lastly, before you launch off for any test sessions with Pingplotter, for additional comments on Pingplotter, can you please read thru the following post and the linked post that it contains.
@Elestriel this testing should be done via ethernet. Your plot indicates a wifi connection. That's looking pretty ugly. If this is via wifi, can you run that via ethernet please. If it turns out the same way, I wouldn't bother running it for an extended period as it indicates that there is some problem with the response from the Domain Name Server.
Can you run the same test to the primary IPV6 DNS address, just to see what turns up.