Node Congestion

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Resident Expert
Resident Expert
Posts: 7,064

Re: Node Congestion

@maniac are you seeing the low rates via ethernet, wifi or both?  

 

Call tech support and ask the tech for the following DOCSIS 3.1 OFDM information:

 

1.  Signal level

2.  Signal to noise ratio

3.  QAM level. 

 

That data isn't presented to the user but tech support has access to it.  While they are all important, the QAM level will tell you in an instant what that modem is capable of providing.  The QAM level, should be 1024 for that modem running with optimum signal levels and signal to noise ratios.  64 QAM is the bottom level QAM for that modem.  Below that it will bail out of the OFDM channel and use the upper DOCSIS 3.0 channels for download purposes.  Even with that, the 4582 modem is a good performing modem even if its running on DOCSIS 3.0 channels.  

 

If the tech can't find the data, insist on him or her finding someone that can find it.  Don't take no for an answer.  Please post the data. 

 

For the speedtests you can use https://www.rogers.com/customer/support/article/internet-speedtest or you can use the www.speedtest.net Toronto, Montreal or Moncton Rogers servers, which ever is closer.  If you go to change the default server, type in Rogers to display all of the Rogers test servers.  Use the nearest Rogers server.  



I'm Here A Lot
Posts: 7

Re: Node Congestion

xo1, that is exactly what I'm thinking.

One person admitted bad congestion, the others did not.

I have started searching for alternatives already. Bell vs. TekSavy vs. CanNet vs. CarryTel. But I know if they are using Rogers to the home anyway then there is not much point in switching to anyone except Bell.  😞

Bell tells me "We currently do not bring fibre to this address but we do bring it to your neighbourhood".

 

I have just run several test:

Speedtest.net is giving me 9/1 to 12/2 to 20/1 at best.

fast.com is giving me 20/2 to 50/12.

I've tried wireless and plugged in directly to modem. Numbers are all over the place. Plugged in is consistantly faster, but I don't pass 50/12.  My plan us 300.

I don't know why speedtest.net is sooo bad

 

It's crazy that there is no speed test tool built into the modem to alleviate any in-between hardware.

 

 

 

I'm Here A Lot
Posts: 7

Re: Node Congestion

Thanks for the direction Datalink. I'll give that a try and report back when I have the numbers.

 

Right now, I turned off IP6 (just in case) and reset my wifi adapters on 3 laptops I am using just to make sure I'm starting fresh.  Speedtest.net is giving me 33/21, 21/18, 22/15, etc.  I know this is over WiFi so it may not be true but it should be better than that regardless (it was far better in the past).  I'll go plugin directly again later.

 

I am in Vaughan, Ontario. When I use my IP to find my location it always thinks I'm in Richmond Hill, Ontario (nearby). I guess that's where by node is coming from? buh. I always choose a nearby server when I use Speedtest.net. If nothing available in Richmond Hill I choose Toronto.

 

 

Resident Expert
Resident Expert
Posts: 7,064

Re: Node Congestion

Fwiw, since January there have been real issues with the Rogers network which results in slow speeds, latency and packet loss.   This also affects TPIA customers.  Rogers is completely silent on the issue so, no one outside of the company knows what the problem is.  It would appear that the field techs have some idea of the fact that a problem exists, but, they're not saying anything.  So, beyond the signal data at the modem and no packet loss to the Cable Modem Termination System (CMTS) which is the first hop beyond the modem enroute to anywhere, one can only conclude that the network issues are at play and are resulting in your poor network results.  

 

Note that I'm making an assumption here that you're running an ethernet connected desktop or laptop to run the speedtests in order to rule out any wifi issues. 

 

Edit:  for now select the www.speedtest Rogers Toronto server.  

 

The issue of wrong location data is due to the fact that ISPs move IP address blocks around and don't update the various location service providers with the updated location to IP block data.  So, end result, users end up with wrong geographic locations.  Normally not a big deal, but, if you've signed up to some type of streaming service that uses Geolocation data to allow viewing of a particular event type, NHL hockey for example this becomes a complete headache.  Its yet another ongoing problem that's been around for at least 5 years, probably longer, with no solution in sight. 

 

Note that with DOCSIS 3.1 running on the downstream side, the front Downstream LED should be light blue, it supposed to be Magenta, officially.  From your signal data above, your modem is running DOCSIS 3.1 on the downstream side.  

 

Ask the Tier I tech to pass you onto a Tier II tech.  What you want to know is the load level of the neighbourhood node and CMTS that you're connected to.  Hopefully the Tier II tech can tell you what the percentage level happens to be.  Just let the Tier II tech know that you're experiencing miserably slow data rates and you would like to know what the load factors happen to be.  Maybe that might shed some light on the situation.  The Tier I tech will probably give you some static on this, but, simply ask if he or she has access to the neighbourhood node and CMTS load data.  If not, get on with it.  I think you're beyond the Tier I tech level at this point, time to look for answers from above.

 

Edit II:  When you have a desktop or laptop connected via ethernet to the modem, have a look at the connected port LED at the back of the modem.  It should be flashing amber, indicating a 1 Gb/s transfer rate with the connected device.  If its flashing green, that indicates a 10/100 Mb/s transfer rate.  Those transfer rates are device to device, not the data rate that your internet plan dictates.  To run 300 Mb/s, the connected port LED at the back of the modem should be flashing amber.  Assuming that's the case, and you have a capable desktop or laptop connected to the modem, and the modems DOCSIS 3.1 OFDM QAM Level is at 1024, then the inescapable conclusion is that your neighbourhood node, or connected CMTS is hopelessly overloaded.  You would need the load numbers to determine which one is the problem but my bet would be on the neighbourhood node,which might require splitting in order to spread the load across two or mode nodes. 



I Plan to Stick Around
Posts: 13

Re: Node Congestion

Yeah if Bell doesn't have fiber in your area unfortunately you are out of luck.  DSL is God awful by design. Just try arguing with support for a rebate.  So far I have gotten a $100, but I am not going to stop until my bill is refunded for May-June (my node is supposed to be split on the 30th of June which should solve my congestion problems).  At this point if constant stable internet is not essential, just try and get your money back.

I Plan to Stick Around
Posts: 57

Re: Node Congestion

I've been having issues in my neighborhood for almost two years now. Back then I was told my neighborhood was still under their threshold to initiate any upgrades.

 

Fast forward to today and they finally say they are going to do a node segmentation but can't even give me a ballpark whether it'll be even this year.

 

I am in the same boat as you, no other options. Aside from sending a PM to the Mods here and getting a high5 for providing stats,there isn't much you can do.

 

Really concerning given the fact it is one of the two large ISPs.

I'm Here A Lot
Posts: 7

Re: Node Congestion

@Datalinktoday when I am plugged in I am getting anywhere from 60/10 to 80/20.  So it's better for some reason, but still not right.  My internet has also completely dropped a couple times. (I can see my google home display immediately tell me when there is no internet)

 

I am plugged directly in to the modem. When I do a trecrt to google.ca I get the following first 4 hops:

1 4 ms 5 ms 4 ms CODA4582 [192.168.0.1]
2 152 ms 15 ms 14 ms 99.228.xx.xx
3 16 ms 32 ms 21 ms 8077-dgw01.mtnk.rmgt.net.rogers.com [66.185.91.177]
4 33 ms 17 ms 29 ms 209.148.229.81

 

Spent 1 hour on live chat with tech support. They would not give me the numbers you asked for Signal, Noise Ratio, QAM. But they told me the numbers are "all fine".  They suggested 3 things:

1) That I don't plug the modem into a power bar. I plug directly into the wall outlet. (I have not changed it yet).

2) That I remove all my other devices to rule anything weird out (which I did).

3) That I PHONE in and ask for level 2 or back end support to check my node. (lololol)

 

I'll try calling now.

 

Edit 1: Tech Support guy (on the phone) says my top speed of 80/20 today is not nearly high enough for Ignite 300 plan. He would think 175Mbps is more like a normal speed to expect. So another tech is now scheduled to come to my house (staying outside of course). "The technician should be able to tell if there is a node congestion problem". 

 

I Plan to Stick Around
Posts: 57

Re: Node Congestion

Yea.. plugging your modem in the wall will help fix the latency experienced at the 2nd hop

 

*facepalm*

 

You're wasting your time amigo, same yourself the trouble.

 

 

I'm Here A Lot
Posts: 7

Re: Node Congestion

So tech support guy told me "I see in the notes here on your file that the maintenance person indicates your node has congestion, and they have escalated to have the node split up to resolve the speed issues.... could take weeks or months... no one has a clue".

 

So now I either stick with Rogers Ignite 300u with my horrible 20Mbps download average; or I cancel and get Bell who claims I will get close to 50Mbps on their service.  😡  

 

 

I'm an Enthusiast
Posts: 961

Re: Node Congestion

Bell.. it took them 1 year to do mine