Greetings @Xemnar!
Do you recall any events happening that preceded this issue occurring? A power outage, construction or an accident in your area perhaps?
Since you've already had a tech out recently, I'd like to take a look at your account and see what notes the tech left behind.
Feel free to send a private message to @CommunityHelps so we can assist you further. For more information on how our Private Messaging system works, you can find out more here.
Regards,
RogersCorey
Greetings @chimetis
If its been determined that there is an issue with your personally owned home equipment, I could look into the history of your account and provide further clarity. If it turns out there's something happening with our service, I can troubleshoot with you.
Feel free to send a private message to @CommunityHelps so we can assist you further. For more information on how our Private Messaging system works, you can find out more here.
Regards,
RogersCorey
Hello @ranjeetbath,
Thank you for joining the conversation here in the Rogers Community Forums!
We do apologize to hear that you are still experiencing an intermittent issue with your connection. We can certainly look into the ticket that was created for you by our maintenance team to see if the issue has been corrected.
Feel free to send us a private message to @CommunityHelps so we can assist you further. For more information on how our Private Messaging system works, please check out our blog.
Regards
RogersJermaine
@kevin_530 I'm seeing the same. Perhaps not as severe as what you are seeing but still erratic.
64 bytes from 8.8.8.8: icmp_seq=779 ttl=116 time=25.464 ms
64 bytes from 8.8.8.8: icmp_seq=780 ttl=116 time=31.427 ms
64 bytes from 8.8.8.8: icmp_seq=781 ttl=116 time=29.044 ms
64 bytes from 8.8.8.8: icmp_seq=782 ttl=116 time=31.839 ms
64 bytes from 8.8.8.8: icmp_seq=783 ttl=116 time=32.742 ms
64 bytes from 8.8.8.8: icmp_seq=784 ttl=116 time=29.595 ms
64 bytes from 8.8.8.8: icmp_seq=785 ttl=116 time=27.566 ms
64 bytes from 8.8.8.8: icmp_seq=786 ttl=116 time=30.357 ms
64 bytes from 8.8.8.8: icmp_seq=787 ttl=116 time=28.404 ms
64 bytes from 8.8.8.8: icmp_seq=788 ttl=116 time=41.591 ms
64 bytes from 8.8.8.8: icmp_seq=789 ttl=116 time=29.108 ms
64 bytes from 8.8.8.8: icmp_seq=790 ttl=116 time=33.024 ms
64 bytes from 8.8.8.8: icmp_seq=791 ttl=116 time=27.921 ms
64 bytes from 8.8.8.8: icmp_seq=792 ttl=116 time=29.796 ms
64 bytes from 8.8.8.8: icmp_seq=793 ttl=116 time=27.863 ms
64 bytes from 8.8.8.8: icmp_seq=794 ttl=116 time=216.110 ms
64 bytes from 8.8.8.8: icmp_seq=795 ttl=116 time=33.034 ms
64 bytes from 8.8.8.8: icmp_seq=796 ttl=116 time=28.810 ms
64 bytes from 8.8.8.8: icmp_seq=797 ttl=116 time=19.726 ms
64 bytes from 8.8.8.8: icmp_seq=798 ttl=116 time=30.223 ms
64 bytes from 8.8.8.8: icmp_seq=799 ttl=116 time=30.492 ms
64 bytes from 8.8.8.8: icmp_seq=800 ttl=116 time=30.143 ms
64 bytes from 8.8.8.8: icmp_seq=801 ttl=116 time=45.875 ms
64 bytes from 8.8.8.8: icmp_seq=802 ttl=116 time=29.151 ms
Still not good
I'm also in Markham and I may be able to shade a bit of light on what has been going on. Rogers has recently been upgrading their old fibre nodes to new DAA nodes. With the new Distributed Access Architecture, functions that used to be performed by infrastructure in the headend are now being pushed out to the next-gen fibre nodes in the neighbourhood. With some CMTS functions now being done at the fibre-coax boundary, the cable modems should now see a much more stable signal. Other upstream network components are also being upgraded. However, these upgrades resulted in a bunch of old, longstanding problems just being replaced with a whole new set of problems.
I, personally, would not have wasted money upgrading the old DOCSIS infrastructure to DAA, especially with tech that is still full of bugs. Rogers should have migrated the legacy infrastructure to FTTH. Now we're stuck with Cable Internet as our only option until another service provider steps up to provide us with something better.
If you have Bell fibre available, or even VDSL/DSL for gaming purposes, its a no brainer to switch off of Docsis cable. There is a low latency extension written for Docsis, but, it will most likely be years before its implemented by ISPs around North America. In the mean time, fibre and VDSL/DSL will beat cable (Docsis) systems hands down.
Here's an example between the cable and VDSL:
https://www.dslreports.com/forum/r32824164-Ping-comparison-between-Rogers-cable-and-Bell-VDSL
Now, one of the problems with switching to Bell is Bell's routing thru Chicago. Bell doesn't appear to peer with anyone, so, you take what you get, in terms of routing to the various game servers around North America. But, you're further ahead to start with in terms of lower fibre latency versus what you get thru any Docsis system from any ISP.
As @-G- has pointed out, Rogers is pushing fibre into the neighbourhoods, either with fibre to the home or fibre beyond the neighbourhood node. That will be a game changer, no pun intended. In the case of fibre to the home, that will allow Rogers to compete with Bell, in terms of latency and data rates. Rogers Nokia Optical Network Terminals (ONTs) are much easier to use due to the ethernet connection to the follow on modem or router. So, if you ever had the choice of the two fibre systems, Rogers would be the one to choose as long as you have a Nokia ONT installed, or its successor. In the case of Rogers fibre installations beyond the node, that might compete with Bell's fibre, but, we haven't seen any data to make that comparison. You would have to be very aware of the network structure in you neighbourhood in order to make that comparison.
That 50 Mb/s download sounds like bonded VDSL/DSL. If you're a gamer, then it would probably make sense to have that VDSL/DSL connection running, and keep the cable connection for high speed downloads and TV.
You can always post a query in the DSLReports forum to see what other users think about VDSL/DSL these days. Its highly dependant on the distance from the pedestal, wherever that is located in the neighbourhood. There is an interleaving setting/capacity that comes into play, and once again, thats dependent on the distance to that pedestal, the names of which don't come to mind. Its been a very long time since I've used DSL.
https://www.dslreports.com/forums/23
The one problem with VDSL/DLS is that the cabling has been left to rot as Bell has been installing Fibre in numerous locations. So, even though Bell's site might indicate that its available, you won't really know if it will work until you have a tech on site to run a few tests to see if the cabling will support VDSL/DSL, and if so, at what data rate? In a worst case scenario, the cabling will be a write-off, so, VDSL/DSL won't be available at your address. Best case scenario, it works really well. Won't know until a tech shows up.
VDSL/DLS operates over the telephone lines by using frequencies above the usual voice frequency range. The tech might install a filter on the inbound telephone line so that telephone line running to the gaming pc's location would use that higher frequency range. There would be another modem installed, this time, to support VDSL/DSL data. That modem would connect to the gaming pc. There are numerous modems that should be available these days. I'm no expert, so you would have to post a question in the DSLReports forum.
So, you would end up with two modems and two possible connections to your pc. If you wanted to run a high speed download, you would just switch the ethernet cables from one modem to the other.
Now, just to point out, if you're not using the telephone cabling in your home, the tech might not install the filter. It might just be a straight thru connection, inbound cable to telephone cable to the gaming pc's location. Not sure if that would impact the noise level or not at the modem.
-
12058 views
-
12 Likes
-
-
