Brutal latency/ping Recently

[t27c]

I am wired, with the gigabit package and all of the sudden have gotten constant ping spikes for over the last few days. I haven't been able to play any games online because the crazy ping spikes and latency make it completely unplayable. My speeds are what they are expected to be, no issues there. I have tried hard wiring straight into the modem but alas, the issue still persists. I have tried switching cables, power cycling my devices, factory resetting my devices. The issue still persists. I have called and contacted Rogers multiple times and they say everything seems fine on their end. But still, the issue persists and is steady. resulting in me not able to use any of my gaming devices due to the brutal and constant ping spikes. It's frustrating paying over $100 a month for internet I cant use for the things I want it for. Any help or suggestions are welcomed and appreciated. Thank you

*** Edited Labels ***

[borisnet]

This is now becoming unbearable.

The frequency has increased to every few hours now so I am kind of leaning towards capacity issue now and no improvement in sight. So sad and frustrating since support cannot do anything about large capacity issue.

[lethalsniper]

I know what you mean it does get frustrating especially when it keeps on happening all the time with no fix ..

[stepy2015]

Its happening pretty much all day everyday for me now I am DONE and no updates on my ticket, what is going on Rogers we need transparency 

[jasonchan]

For me, my zoom calls have been brutal - I just checked and the ping is reasonable, but there's still some lost packets.

Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=22ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=16ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=17ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=18ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=17ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=24ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=17ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=22ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=27ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=16ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116

Ping statistics for 8.8.8.8:
Packets: Sent = 204, Received = 202, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 27ms, Average = 10ms

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	669000000	QAM256	8.400	19	38.983
2	657000000	QAM256	9.000	17	40.366
3	663000000	QAM256	8.400	18	40.366
4	651000000	QAM256	9.400	16	40.366
5	597000000	QAM256	10.400	8	40.946
6	603000000	QAM256	10.199	9	40.366
7	609000000	QAM256	10.099	10	40.946
8	615000000	QAM256	9.900	11	40.946
9	621000000	QAM256	9.900	12	40.366
10	633000000	QAM256	10.300	13	40.366
11	639000000	QAM256	9.500	14	40.366
12	645000000	QAM256	8.900	15	40.946
13	279000000	QAM256	8.400	1	40.946
14	579000000	QAM256	10.300	5	40.366
15	585000000	QAM256	10.500	6	40.366
16	591000000	QAM256	10.599	7	40.946
17	675000000	QAM256	8.400	20	40.366
18	681000000	QAM256	8.000	21	40.366
19	687000000	QAM256	7.900	22	38.983
20	693000000	QAM256	8.400	23	40.366
21	699000000	QAM256	7.900	24	38.983
22	705000000	QAM256	7.900	25	38.983
23	711000000	QAM256	8.000	26	38.983
24	717000000	QAM256	7.400	27	38.605
25	723000000	QAM256	6.000	28	38.605
26	825000000	QAM256	7.599	29	38.605
27	831000000	QAM256	7.699	30	38.605
28	837000000	QAM256	7.000	31	38.605
29	843000000	QAM256	6.900	32	38.605
30	849000000	QAM256	7.300	2	38.605
31	855000000	QAM256	6.900	3	38.605
32	861000000	QAM256	6.699	4	38.605

OFDM Downstream Overview

Receiver	FFT type	Subcarr 0 Frequency(MHz)	PLC locked	NCP locked	MDC1 locked	PLC power(dBmv)
0	NA	NA	NO	NO	NO	NA
1	4K	275600000	YES	YES	YES	10.400002

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	38700000	64QAM	40.020	8	6400000
2	21100000	64QAM	39.010	5	3200000
3	32300000	64QAM	39.520	7	6400000
4	25900000	64QAM	39.270	6	6400000
5	0	QAM_NONE	-	---	1600000
6	0	QAM_NONE	-	---	1600000
7	0	QAM_NONE	-	---	1600000
8	0	QAM_NONE	-	---	1600000

OFDM/OFDMA Overview

Channel Index	State	lin Digital Att	Digital Att	BW (sc's*fft)	Report Power	Report Power1_6	FFT Size
0	DISABLED	0.0000	0.0000	0.0000	0.0000	0.0000	2K
1	DISABLED	0.0000	0.0000	0.0000	0.0000	0.0000	2K

[lethalsniper]

Once again Rogers tech a no show .. waisted my time and superintendent time was supposed to be here from 8-10 am for a upload noise issue .. no call . Nothing .. how can I escalate this issue? Unprofessional! This is not the first time this has happened.. @rogerstony @Datalink @RogersRob @CommunityHelps 

[tulowindow]

Hello,

Latency Spikes - All Day & Night until about Midnight. I have ping spikes occurring all throughout the day and night. Generally speaking, they don't go away until about after midnight which leads me to believe it's nothing on my end. At points in time when there are few people online, such as 2AM, the connection is perfect. During high volume hours, nothing but latency spikes. I'm growing ever frustrated.

To be clear, I don't believe this is an issue on my end for a few reasons. I've tested the modem in gateway mode & in bridge mode both. I've pinged directly to my modem and to my router and gotten <1ms or at worst 1-2ms without spiking at all. I've got a pretty high performance ASUS ROG router as well. Needless to say, even in Gateway mode, the problem persists. I've used completely new coax from the wall to the modem which changes nothing. I've done extensive ping testing at numerous times of the day and it's always the same. Latency spikes during high volume times, and coast is clear after midnight. Growing quite tired of this situation.

Rogers customer service will tell me "there's nothing wrong with your line" etc. Standard stuff. Here's an example of me pinging google at 11:00 AM today. You will notice that my normal low ping is between 12-20ms.... but there are numerous spikes to 45ms+ and the real problematic ones are the ones hitting 80ms, 90ms, even 100ms.

While it may seem insignificant, when I'm playing online video games it can cause me issues with stability. Certain games that I play have netcode which allows for cross-continent play and these 100ms spikes causes severe rubber banding in-game. My game jerks around crazily when these spikes occur, and they are constant. If the ping was 50 and it was stable, that would be fine. It's not though, the only constant with my latency is the constant instability. Observe this less than 60 second example and how many spikes occur within the minute.

C:\Users\User>ping -t www.google.com

Pinging www.google.com [172.217.164.228] with 32 bytes of data:
Reply from 172.217.164.228: bytes=32 time=34ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=99ms TTL=116
Reply from 172.217.164.228: bytes=32 time=46ms TTL=116
Reply from 172.217.164.228: bytes=32 time=17ms TTL=116
Reply from 172.217.164.228: bytes=32 time=47ms TTL=116
Reply from 172.217.164.228: bytes=32 time=13ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=20ms TTL=116
Reply from 172.217.164.228: bytes=32 time=44ms TTL=116
Reply from 172.217.164.228: bytes=32 time=13ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=41ms TTL=116
Reply from 172.217.164.228: bytes=32 time=22ms TTL=116
Reply from 172.217.164.228: bytes=32 time=38ms TTL=116
Reply from 172.217.164.228: bytes=32 time=17ms TTL=116
Reply from 172.217.164.228: bytes=32 time=81ms TTL=116
Reply from 172.217.164.228: bytes=32 time=34ms TTL=116
Reply from 172.217.164.228: bytes=32 time=30ms TTL=116
Reply from 172.217.164.228: bytes=32 time=15ms TTL=116
Reply from 172.217.164.228: bytes=32 time=23ms TTL=116
Reply from 172.217.164.228: bytes=32 time=72ms TTL=116
Reply from 172.217.164.228: bytes=32 time=97ms TTL=116
Reply from 172.217.164.228: bytes=32 time=13ms TTL=116
Reply from 172.217.164.228: bytes=32 time=12ms TTL=116
Reply from 172.217.164.228: bytes=32 time=80ms TTL=116
Reply from 172.217.164.228: bytes=32 time=14ms TTL=116
Reply from 172.217.164.228: bytes=32 time=39ms TTL=116
Reply from 172.217.164.228: bytes=32 time=31ms TTL=116
Reply from 172.217.164.228: bytes=32 time=17ms TTL=116
Reply from 172.217.164.228: bytes=32 time=17ms TTL=116
Reply from 172.217.164.228: bytes=32 time=12ms TTL=116
Reply from 172.217.164.228: bytes=32 time=17ms TTL=116
Reply from 172.217.164.228: bytes=32 time=15ms TTL=116
Reply from 172.217.164.228: bytes=32 time=14ms TTL=116
Reply from 172.217.164.228: bytes=32 time=18ms TTL=116
Reply from 172.217.164.228: bytes=32 time=25ms TTL=116
Reply from 172.217.164.228: bytes=32 time=24ms TTL=116
Reply from 172.217.164.228: bytes=32 time=26ms TTL=116
Reply from 172.217.164.228: bytes=32 time=18ms TTL=116
Reply from 172.217.164.228: bytes=32 time=20ms TTL=116
Reply from 172.217.164.228: bytes=32 time=21ms TTL=116
Reply from 172.217.164.228: bytes=32 time=23ms TTL=116
Reply from 172.217.164.228: bytes=32 time=38ms TTL=116
Reply from 172.217.164.228: bytes=32 time=20ms TTL=116
Reply from 172.217.164.228: bytes=32 time=16ms TTL=116
Reply from 172.217.164.228: bytes=32 time=14ms TTL=116
Reply from 172.217.164.228: bytes=32 time=113ms TTL=116
Reply from 172.217.164.228: bytes=32 time=37ms TTL=116
Reply from 172.217.164.228: bytes=32 time=21ms TTL=116
Reply from 172.217.164.228: bytes=32 time=20ms TTL=116
Reply from 172.217.164.228: bytes=32 time=46ms TTL=116
Reply from 172.217.164.228: bytes=32 time=36ms TTL=116
Reply from 172.217.164.228: bytes=32 time=12ms TTL=116
Reply from 172.217.164.228: bytes=32 time=17ms TTL=116
Reply from 172.217.164.228: bytes=32 time=98ms TTL=116
Reply from 172.217.164.228: bytes=32 time=14ms TTL=116
Reply from 172.217.164.228: bytes=32 time=49ms TTL=116
Reply from 172.217.164.228: bytes=32 time=33ms TTL=116
Reply from 172.217.164.228: bytes=32 time=38ms TTL=116
Reply from 172.217.164.228: bytes=32 time=105ms TTL=116
Reply from 172.217.164.228: bytes=32 time=46ms TTL=116
Reply from 172.217.164.228: bytes=32 time=18ms TTL=116
Reply from 172.217.164.228: bytes=32 time=29ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=29ms TTL=116
Reply from 172.217.164.228: bytes=32 time=14ms TTL=116
Reply from 172.217.164.228: bytes=32 time=27ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=53ms TTL=116
Reply from 172.217.164.228: bytes=32 time=30ms TTL=116
Reply from 172.217.164.228: bytes=32 time=21ms TTL=116
Reply from 172.217.164.228: bytes=32 time=50ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=19ms TTL=116
Reply from 172.217.164.228: bytes=32 time=23ms TTL=116
Reply from 172.217.164.228: bytes=32 time=14ms TTL=116
Reply from 172.217.164.228: bytes=32 time=60ms TTL=116
Reply from 172.217.164.228: bytes=32 time=21ms TTL=116
Reply from 172.217.164.228: bytes=32 time=45ms TTL=116
Reply from 172.217.164.228: bytes=32 time=15ms TTL=116
Reply from 172.217.164.228: bytes=32 time=14ms TTL=116
Reply from 172.217.164.228: bytes=32 time=78ms TTL=116

Why can't Rogers offer a stable product?

[lethalsniper]

I’m getting the exact same issue when gaming and when pinging google.com I’m in the north york area sheppard and Donmills area.

[super_robot]

Sniper ; is BELL available in your area? 

Rogers has had severe issues all over the GTA. If you've gone through all the hoops with Rogers and still feel like you are in the dark, open a complaint with CCTS.

Your neighborhood is likely congested and will need a node segmentation. All your efforts from your end will be in vain. 

At my old place I had a Rogers office of the president rep reach out to me and flat out say that the service will not get better until they segment the node. He then provided me with discounts and credit. I had no other option because BELL wasn't around and all resellers were selling Rogers.

You will likely not get better service quality but could likely get a cheaper monthly rate/credit if BELL is not an option in your neighborhood.

I feel you guys' pain, I've wasted so much time to finally get to the bottom of it and even then there wasn't a resolution as far as the service quality is concerned. 

My problems went away when I moved to my new house.. BELL is available here so likely taking a load off Rogers' neighborhood hub.

[lethalsniper]

No bell in my area, I have another technician coming out to look at a upload issue thats causing noise it’s like the 3rd guy here and they still can tell me exactly where the noise is coming from I can’t get a clear answer why it’s happening.. every time I call in they find upload noise coming in to building then in the end no fix then again call in again noise in the upload this is starting to get annoying.. yea if I don’t get a clear answer by the end of the week I will reach out to the CCTS thanks. @super_robot

[tulowindow]

No bell in my area either... Except for 10mbps/1mbps.... Which is not an option for me as I have a need for better upload... (even though there is only 30 max on rogers and syncing at 5-10 during these lag times) how do you complain to ccts. The connection is clearly overloaded. It's sad that this laggy cable service costs $130/mo from a billion dollar company when there are options like beanfield in Toronto which is independent offering symmetrical gigabit with outstanding performance and amazing routing for only $50/mo.

Also, I just came back to my computer and it's now 2:12 PM.... 3 hours later. The spikes have only gotten worse as user volume has increased. 11:00 AM looks like a sterling connection compared to now. Here's a quick 20 second test. Brutal, in the span of 20 seconds I bounced to 200+ and 100+ in separate spikes. 

C:\Users\User>ping -t google.com

Pinging google.com [172.217.1.14] with 32 bytes of data:
Reply from 172.217.1.14: bytes=32 time=23ms TTL=116
Reply from 172.217.1.14: bytes=32 time=48ms TTL=116
Reply from 172.217.1.14: bytes=32 time=47ms TTL=116
Reply from 172.217.1.14: bytes=32 time=50ms TTL=116
Reply from 172.217.1.14: bytes=32 time=49ms TTL=116
Reply from 172.217.1.14: bytes=32 time=59ms TTL=116
Reply from 172.217.1.14: bytes=32 time=34ms TTL=116
Reply from 172.217.1.14: bytes=32 time=27ms TTL=116
Reply from 172.217.1.14: bytes=32 time=212ms TTL=116
Reply from 172.217.1.14: bytes=32 time=30ms TTL=116
Reply from 172.217.1.14: bytes=32 time=26ms TTL=116
Reply from 172.217.1.14: bytes=32 time=97ms TTL=116
Reply from 172.217.1.14: bytes=32 time=40ms TTL=116
Reply from 172.217.1.14: bytes=32 time=56ms TTL=116
Reply from 172.217.1.14: bytes=32 time=68ms TTL=116
Reply from 172.217.1.14: bytes=32 time=79ms TTL=116
Reply from 172.217.1.14: bytes=32 time=33ms TTL=116
Reply from 172.217.1.14: bytes=32 time=72ms TTL=116
Reply from 172.217.1.14: bytes=32 time=42ms TTL=116
Reply from 172.217.1.14: bytes=32 time=29ms TTL=116
Reply from 172.217.1.14: bytes=32 time=110ms TTL=116
Reply from 172.217.1.14: bytes=32 time=76ms TTL=116
Reply from 172.217.1.14: bytes=32 time=62ms TTL=116
Reply from 172.217.1.14: bytes=32 time=14ms TTL=116
Reply from 172.217.1.14: bytes=32 time=45ms TTL=116
Reply from 172.217.1.14: bytes=32 time=19ms TTL=116
Reply from 172.217.1.14: bytes=32 time=39ms TTL=116
Reply from 172.217.1.14: bytes=32 time=51ms TTL=116
Reply from 172.217.1.14: bytes=32 time=22ms TTL=116
Reply from 172.217.1.14: bytes=32 time=36ms TTL=116
Reply from 172.217.1.14: bytes=32 time=42ms TTL=116
Reply from 172.217.1.14: bytes=32 time=40ms TTL=116

Brutal.

[lethalsniper]

Would anyone know why the IP MDU or CMTS address on hop 2 would of changed ? i noticed the change when I did a tracerout @Datalink

[AngryChicken]

It's the nature of dynamic routing.  Big ISPs like Rogers will have multiple, redundant paths through their backbone network and from time to time their routers will "prefer" one path over another to the same destination (less latency, lower cost, better bandwidth..) and you will see a new path when you conduct a traceroute.  This can change dynamically at any time depending on real-time conditions in their network.

[lethalsniper]

Would that mean they splitted our node in our area ? My brother in-law lives in the same building but on different floors as me and his cmts IP address is different then mine .. his is the IP I had before I just hope it’s for the best hopefully it fixes something

[AngryChicken]

🙂  That thought had crossed my mind.  It's totally possible, especially because the CMTS is the first router that your traffic encounters on its way into the Rogers backbone.  Here's hoping!

[lethalsniper]

I hope so it would help on latency issue / slow speeds .. can anyone confirm this please ?

[SquishyTomato]

Been happening to me for over a year, on 2 diffrent routers.

This is a rogers issue to the core.

[SquishyTomato]

Still happening in Blizzard games, constant rubber banding and DC, and its not my router, my line has been changed and the tech people have been to my house 3 straight times

I'm so over it

[jcoll83ca]

I figured I might as well chime in here. I'm also experiencing high ping/latency and also packet burst issues when gaming after 10pm AST.  It is especially bad Friday and Saturday. Games like Fortnite and Modern Warfare ill get 100+ ping and severe packet burst. It literally makes the games unplayable. I have tried everything I can to resolve the issue on my end. Port forwarding, changing DNS servers, putting the router in bridge mode and using my own router.. nothing works.

I have tried working with the tech support team and they have told me there is "noise" on the line which could be causing the issue. Each time I contact them they somehow reset the signals going to the router and it temporarily fixes the problem but then it just reoccurs.

At this point I'm at a loss as to what else can be done other then a tech coming out, which they seem reluctant to do.

[SquishyTomato]

The noise on the line is insane, I've had a tech come in 3 times to "fix" the noise in the line, still get insane lag spikes.

same issues as you, Warzone is unplayable due to the lag and packet loss

[AngryChicken]

I would reach out to the community support moderators about this, though I haven’t seen a post by them on this thread in over a week. Likely they are getting tired of repeating plays from the same playbook all the time as Rogers corporate had done nothing to ameliorate the situation and probably won’t unless you open a formal complaint. And by that, I mean with the CCTS. If you are not aware of that organization, you will find it in a quick Google search! I have an open complaint with them and it’s now back to Rogers to suggest a remedy.

Ultimately the remedy is to ease the congestion in their network which is causing the latency issues which quite a few users are experiencing. This will never be solved in “the last mile”, meaning the cables to our houses and the equipment therein (ie their modem). The problem can only be resolved by upgrading and segmenting their infrastructure in the core of their network and where it serves our neighborhoods, so we have more traffic lanes into their network.

Yes we’re all living with COVID (it sucks!) and all the resultant stay-at-home workers and learners saturating the network, but.... at the end of the day it is a contract. We pay them handsomely for the service and despite all their legalese in their terms of service with us (and which is worded in their favour) they have to deliver the service we pay for.

My hats are off to the wonderful community support ninjas that I have met on this forum. Not at all their fault so let’s help one another by opening up complaints with the CCTS and put Rogers’ feet to the fire.

[PizzaBear]

@SquishyTomato

I am curious about a couple things, can you provide to the forums how your modem signal page is showing.

Also, can you do a ping test of 50 pings to:
192.168.50.1 ( if asus, or 192.168.1.1 )

if you modem is in bridge mode ( also ping 192.168.100.1 ).

Also ping 8.8.8.8

Don't post the entire ping, just copy/paste the ping result (min,max,avg)