I am a Rogers customer since 2004 and I must say that I have opened so many tickets ( a year worth) , talked to so many supervisors and senior technicians including Office of the CTO until I was told to switch to ignite to fix my Gigabit Speed Internet high latency and cable noise that started March 2020 , where I used to get between 1500 to 3000 ms ping replies when simply pinging google.com while being wired directly connected to the modem and not through WI-FI
I m in a Brampton area where Rogers rules .. No Bell No fiber otherwise believe me I would have switched in a heartbeat.
Now after not having the issues I mentioned since the switch to Ignite 4 months or so ago.
Guess what!. Its back now with vengeance for the past 3 days
High Pings as high as 3 sec
2021-05-21 12:32:32 AM - Reply from 18.104.22.168: bytes=32 time=19ms TTL=116
2021-05-21 12:32:34 AM - Reply from 22.214.171.124: bytes=32 time=565ms TTL=116
2021-05-21 12:32:35 AM - Reply from 126.96.36.199: bytes=32 time=534ms TTL=116
2021-05-21 12:32:36 AM - Reply from 188.8.131.52: bytes=32 time=497ms TTL=116
2021-05-21 12:32:37 AM - Reply from 184.108.40.206: bytes=32 time=461ms TTL=116
2021-05-21 12:32:37 AM - Reply from 220.127.116.11: bytes=32 time=11ms TTL=116
2021-05-21 12:32:39 AM - Reply from 18.104.22.168: bytes=32 time=394ms TTL=116
2021-05-21 12:32:40 AM - Reply from 22.214.171.124: bytes=32 time=362ms TTL=116
2021-05-21 12:32:40 AM - Reply from 126.96.36.199: bytes=32 time=16ms TTL=116
2021-05-21 12:32:42 AM - Reply from 188.8.131.52: bytes=32 time=293ms TTL=116
2021-05-21 12:32:43 AM - Reply from 184.108.40.206: bytes=32 time=256ms TTL=116
2021-05-21 12:32:44 AM - Reply from 220.127.116.11: bytes=32 time=218ms TTL=116
2021-05-21 12:32:45 AM - Reply from 18.104.22.168: bytes=32 time=178ms TTL=116
2021-05-21 12:51:25 AM - Reply from 22.214.171.124: bytes=32 time=12ms TTL=116
2021-05-21 12:51:29 AM - Reply from 126.96.36.199: bytes=32 time=2565ms TTL=116
2021-05-21 12:51:29 AM - Reply from 188.8.131.52: bytes=32 time=31ms TTL=116
2021-05-21 12:51:33 AM - Reply from 184.108.40.206: bytes=32 time=2586ms TTL=116
2021-05-21 12:51:33 AM - Reply from 220.127.116.11: bytes=32 time=42ms TTL=116
2021-05-21 1:34:22 AM - Reply from 18.104.22.168: bytes=32 time=490ms TTL=116
2021-05-21 1:34:23 AM - Reply from 22.214.171.124: bytes=32 time=453ms TTL=116
2021-05-21 1:34:27 AM - Reply from 126.96.36.199: bytes=32 time=2588ms TTL=116
2021-05-21 1:34:27 AM - Reply from 188.8.131.52: bytes=32 time=56ms TTL=116
This simply drops on you all day to ruin your life or what ever your doing on the internet which is all I do since I work from home or if I am
- Gaming ( Can't Play COD Warzone since there is so much lag or even disconnecting)
- Streaming ( Continuously dropping frames )
- Zoom Meetings ( Cutting off when talking or even disconnecting )
I m simply out of options other than maybe getting Star-link Internet when I have the chance and simply dump this awful service or buy a house and move to an area where Bell have Fiber implementation cause guess what Rogers is still living in the 18th century where they dont offer fiber yet and on top of that if some neighbor turns on their vacuum or blender creates an interference that causes cable noise bleeding into the street junction/hub that ruin everyone's internet experience in the neighbored.
Just disappointing that Rogers comes down to this level of service where they are going backwards and I end up paying a high premium for low quality service.
a Traceroute example from today where i caught the latency . the issue i m seeing that latency this can show anywhere after hop 4 which is the wan gateway
Tracing route to google.com [184.108.40.206]
over a maximum of 64 hops:
1 1 ms 6 ms 6 ms 192.168.110.1
2 13 ms <1 ms <1 ms 192.168.110.2
3 1 ms <1 ms <1 ms 10.0.0.1
4 10 ms 12 ms 16 ms 220.127.116.11
5 2465 ms 18 ms 30 ms 18.104.22.168 <- High latency
6 12 ms 12 ms 10 ms 22.214.171.124
7 20 ms 19 ms 16 ms 126.96.36.199
8 * * * Request timed out.
9 11 ms 12 ms 13 ms 188.8.131.52
10 14 ms 11 ms 17 ms 184.108.40.206
11 12 ms 20 ms 10 ms yyz10s03-in-f14.1e100.net [220.127.116.11]
1 1 ms 6 ms 6 ms 192.168.110.1
2 <1 ms <1 ms <1 ms 192.168.110.2
3 1 ms <1 ms <1 ms 10.0.0.1
4 17 ms 10 ms 9 ms 18.104.22.168
5 8 ms 10 ms 6 ms 22.214.171.124
6 14 ms 13 ms 10 ms 126.96.36.199
7 11 ms 10 ms 9 ms 188.8.131.52
9 10 ms 12 ms 9 ms 184.108.40.206
10 10 ms 12 ms 11 ms 220.127.116.11
11 1335 ms 21 ms 7 ms yyz10s14-in-f14.1e100.net [18.104.22.168] <- High latency
going through the thread I see no response from Rogers as they simply don't care as long as your paying their fees
and not taking actions which isn't a lot since you might be just like me stuck with Rogers as a provider in your area.
i have already put a down payment for Starlink and once i get my turn and install it and compare the service i ll be giving the ignite modem back to rogers, canceling my services and get my self an IP TV and call it a day
Where is the official response from Rogers on this thread since a lot of us customers don't have a good internet service.
i also opened a compliant ticket with CCTS which i would advise everyone on this thread to do https://www.ccts-cprst.ca/for-consumers/complaints/ if your having similar issues in your area
Just give up. You are on a shared cable internet with the rest of your neighborhood. With most people now WFH cable internet has gone down the drain. Hence why almost everyone since March 2020 are experiencing higher latency than normal. Especially older neighborhoods with old wiring.
Rogers are trying their best to alleviate nodes by segmenting them but it can/will take years. If you are experiencing high latency and your signal levels are good, then don't waste your time trying to troubleshoot as it is 99% out of your control.
Don't even try waiting for Rogers Fiber if your neighborhood isn't brand new as it'll probably be 2024 before they start digging up older neighborhoods.
Cable will never be good for latency sensitive applications (gaming, voip etc) and that is a fact. Take my advice and stop wasting your time/money buying new equipment and configuring your network as it is out of your control. Your best bet is Bell DSL or if you can move to somewhere with Bell Fiber.
so the technician tested everything including changing the ignite modem with no help. now its been deferred to the maintenance crew since its a problem at the back end and i can clearly see that in the attached screen shot where you can clearly see Jitter above 35 ms indicating data congestion / data transmission delay starting on the WAN gateway (Hop 4) and then on Rogers backend (Hop 5,6 & 7 ) until it leaves Rogers infrastructure at hop 7 which is what is causing the 2000+ latency .