Outside of the rogers speedtest, you have to be careful of the 'location' is chooses for you, it can make a big difference.
EG: Waterloo. It trys to give you a waterloo endpoint. Except that to get to that waterloo endpoint, it has to go TO toronto, and then back to waterloo (due to the pathing on how it has to get there). You get better speed tests choosing a toronto server. (and even the toronto servers, you'll get a varying range of speeds... the TELUS one on speedtest.net works best for toronto)
If you want to take a few moments to check and post your signal levels, we could see if anything is a miss there to be causing the issue. (not to say its not a back end, or something else issue).
I am on the 100mbps here.. just pulled 103mbps (due to speedboost)
outside of using a speed test, I was just playing a game of leage of legends which lags so bad now since of course we are in primetime. I use pingplotter to see what is happening, explain 100 percent packet loss and look where the errors are, they are Rogers Nodes. This internet quality is dispicable and Rogers claims of reliable internet are false and a far stretch from the truth.
@RadioStar you've got problems at the first node. That might be due to the Multiple Dwelling Unit (MDU) which would be installed in the utility room downstairs, or possibly due to the neighborhood node. If your building is large enough, it would most likely be an MDU. Any discussion that you have with tech support should include a signal check on your modem and the same check with other modems connected to the MDU or to the neighborhood node, which ever it might be. I suspect that your neighbors are having the same issue. Its certainly worth chasing this down. If you do not get a satisfactory answer from the first line tech support, ask to speak with a manager, and arrange for a visit by a senior tech.
You indicated that you're anticipating switching to Bell Fibe when the building is connected. If Bell only brings the fibre to the MDU, then you will still have the same problem to contend with. That would mean that Bell is still relying on the MDU and the copper cabling from the MDU to your apartment. If Bell brings fibre to every apartment, then yes, you would bypass the existing MDU and cabling. Just be prepared to see the same issue, depending on how Bell wires the building.
Its quite possibly they might Datalink.
Somone i know online, they were posting on twitter a few weeks ago, they were down in Toronto.. that the building was being wired with FTTH.. a fiber outlet in each unit.
I won't argue that there are significant delays and jitter downstream, but, I think that the majority of the problem is the first node after the modem. Looking at the data captures you also have at least one image which shows significant delay to the modem, which itself is unusual. Personally I'd be calling in, again and again to resolve the first hop issue, be it building MDU or neighborhood node. Solve that problem and see what happens to the remaining path to the Riot server. Fwiw, building MDU issues have proven to be a challenge to resolve for some reason, so, it takes persistence and perseverance to see that its corrected.
When you talk with Bell, ask them if they intend to install FTTH (Fibre to the Home) which should mean that your apartment will have a fibre drop somewhere in the apartment itself.
You either have cable problems or possibly a building MDU problem. In the case of large apartment buildings, there can be a Multiple Dwelling Unit (MDU) located in the utility room in the basement to provide data distribution to the whole building. So, you might be on an MDU, or, once again depending on the building size, you might be connected to a neighborhood node, as is typical in a residential area. Judging by your comments about the whole building being affected it sounds like an MDU, which would be beyond the contract tech's responsibility and possibly knowledge as well, so, he or she would call for the maintenance staff to determine what the problem is and correct it.
At the present time your downstream signal levels are slightly low, but that wouldn't cause any issues. The signal to noise ratios are good as well. The problem is the upstream levels. You should have three upstream channels running in the 36 to 40 dBmV range. You only have two upstream channels running and one of them is at the extreme upper DOCSIS limit. So, that is either a cable issue, or possibly an MDU issue. In any event, you need to call tech support, indicate that you only have two upstream channels running with the upper one probably about to fail as well, and ask the CSR to run a signal check on the modem. The check should fail automatically which should then lead to a follow on conversation aimed at getting a tech to visit your home at you're earliest convenience.
Rogers: 1-888-764-3771
@flycasual3989 you have at least one problem, maybe two, on the go at the present time. The first is some type of cable and/or connector problem. This results in the upstream signal levels which are at the DOCSIS limit of 51 dBmV for three or four channel TDMA. Rogers uses 52 dBmV as a failure point for some reason. The normal signal levels are 0 dBmV on the downstream with a signal to noise ratio of 36 to 40 dB, so, your downstream levels aren't too bad. The upstream is normally in the 36 to 40 dBmV range. As the signal losses thru the cable increase, the modem steps up the output power in order to maintain comms with the neighborhood node. You're just at the point of starting to lose the output channels one by one as there is a maximum output power limit for the modem. Call tech support and ask the CSR to run a signal check on your modem. That test might just pass. I wouldn't be surprised given that Rogers uses 52 dBmV. Hopefully it will fail and the result will be a tech visit to your home in the next day or two. In the event that the test does manage to squeak by and pass, advise the CSR that 5 to 50 Mb/s on a 100 Mb/s plan is not acceptable and that the download rates you are seeing are not acceptable. Be rather forceful on this if necessary. If you have any other issues such as pixelating images on cable tv or problems with home phone service, indicate that as well. On a 100/10 Mb/s plan, with good signal levels, you should be seeing around 130 Mb/s for peak download rates during a speedtest. When you run the speedtest use the www.speedtest.net Toronto Telus server or Rogers http://speedcheck.rogers.com/en.html
Once the cable / connector issue has been rectified, the next question is the modem to neighborhood node performance. You can test that by using pingplotter, or WinMTR. Pingplotter is available from pingplotter.com. It will run in pro mode for about 14 days and then downgrade to free version if you don't buy a licence for it. There are free, standard and pro modes available, so you can go freebie version or buy a licence for one of the other two modes. Running pingplotter will allow you to determine if there are any issues from the modem to the neighborhood node or beyond, to your selected target, which could be a gaming server, google, or any other server of your choice. There is a File ... Save Image function that will save the current image, which can then be inserted into a post so that we can see if there any any problems between the modem and neighborhood node or beyond.
WinMTR is a text version of a network test and will show the trace to the target and times to the target. Same idea as pingplotter though, it can be used to look at intermediate hops, such as modem to next node to determine if there are any problems just reaching the neighborhood node. This can be downloaded from https://winmtrnet.codeplex.com This is an updated version that can be used for IPV4 or IPV6 traces.
In either case, if you run the program at various times of the day, morning, noon, early evening, late evening, you will soon see if there are patterns to the problem times, such as in the evening when people are home and the load on the neighborhood node increases. This can result in poor download rates, high ping times and out of spec signal levels.
So, in either case, you can post the results in the forum, text or image for us to have a look at. The image will require moderator approval to make it avaialable to the public but that isn't a problem.
@flycasual3989, can you delete the graphic from your post as it contains your modems IPV6 address. If that was an IPV4 address, ie: 192.168.0.1 or something along those lines I wouldn't be concerned. Whenever you post those image captures, open it with something like Microsoft Paint and wipe out the first IP address if its an IPV6 address.
And... can you try the following. Run the same test but let it run for 200 pings or more. When its running, right click on the top title bar that shows the column headings and select MAX from the popup menu. Drag that column over and park it next to the MIN column so we can compare the two fields. At the top there is a Focus drop down selection menu. Select that and choose "All" to use all the data in the average ping time calculation. On the bottom, right click and select something like 10 minutes for the bottom time display. Do the same image capture as before, but wipe out the first IPV6 address when you save it. I'm curious about what the max number will be over a longer time period.
When you have time, can you log into your modem, navigate to the STATUS ...... DOCSIS EVENT page and have a look for one of the following sequences:
a. CMTS-MAC=00:17:10 which indicates that you are connected to a Casa Systems Cable Modem Termination System (CMTS), or;
b. any of the following which indicates that you are connected to a Cisco Systems CMTS.
1. CMTS-MAC=00:05:00
2. CMTS-MAC=00:12:43
3. CMTS-MAC=00:14:f1
4. CMTS-MAC=00:1e:be
5. CMTS-MAC=00:1f:ca
6. CMTS-MAC=e0:2f:6d Note: there may be other Cicso MAC addresses
as well which are not on this list yet.
Please let me know if you have the CMTS-MAC=00:17:10 sequence in your DOCSIS EVENTS log.
Don't wait to call tech support regarding the signal levels. They won't improve on their own and the sooner that situation is corrected, the sooner you should see uninterrupted service.
I left pingplotter on for a while so it has a lot of pings but here it is, I also did not find any CMTS-MAC=00:17:10 adresses, or any of the other ones you posted. There was a different CMTS-MAC address however. Alright, I'll call them tomorrow about the signal levels.
You have packet loss just getting to the first node beyond the modem, so thats not good. Hopefully by addressing the situation that is currently affecting your signal levels, all of the packet loss on that trace will disappear.
-
15779 views
-
10 Likes
-
-
