Brutal latency/ping Recently

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
super_robot
I Plan to Stick Around
Posts: 64

Re: Brutal latency/ping Recently

@soundwave80 Where are you located?

 

I am around High Park and it isn't available

badinternetsad
I've Been Here Awhile
Posts: 4

Re: Brutal latency/ping Recently

My gaming experience has gotten steadily worse over the last few months. I used to get a stable 50ms to Overwatch's Chicago server, now it bounces from 50-110ms, with the occasional insane packet loss spikes (40%). Rogers support has been less than useless, and refuse to admit that the issue could even possibly be on their end. I've had 2 technicians at my house in the last few months, and it's only gotten worse. My internet doesn't lag or buffer for streaming or browsing, but the gaming ping will spike a little bit. Internet works fine other than gaming.

 

Details:

Router: CODA-4582U

Connection: wired, but also use wireless for xbox, getting same kind of issues there as well

 

Trace Route to Overwatch server:

Tracing route to 24.105.45.109 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms CODA4582 [192.168.0.1]
2 12 ms 25 ms 235 ms 99.235.36.1
3 22 ms 44 ms 28 ms 8083-dgw01.hnsn.rmgt.net.rogers.com [69.63.242.137]
4 18 ms 22 ms 22 ms 3000-dgw02.hnsn.rmgt.net.rogers.com [209.148.232.250]
5 75 ms 20 ms 115 ms 69.63.249.42
6 44 ms 36 ms 41 ms 209.148.233.102
7 47 ms 39 ms 80 ms eqix-dc2.blizzard.com [206.126.237.174]
8 44 ms 45 ms 45 ms ae1-br01-eqdc2.as57976.net [137.221.72.33]
9 41 ms 78 ms 36 ms et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
10 50 ms 38 ms 47 ms et-0-0-0-pe03-eqch2.as57976.net [137.221.69.55]

 

Pinging google.com [172.217.164.206] with 32 bytes of data:
Reply from 172.217.164.206: bytes=32 time=29ms TTL=55
Reply from 172.217.164.206: bytes=32 time=33ms TTL=55
Reply from 172.217.164.206: bytes=32 time=64ms TTL=55
Reply from 172.217.164.206: bytes=32 time=33ms TTL=55
Reply from 172.217.164.206: bytes=32 time=68ms TTL=55
Reply from 172.217.164.206: bytes=32 time=22ms TTL=55
Reply from 172.217.164.206: bytes=32 time=67ms TTL=55
Reply from 172.217.164.206: bytes=32 time=23ms TTL=55
Reply from 172.217.164.206: bytes=32 time=24ms TTL=55
Reply from 172.217.164.206: bytes=32 time=16ms TTL=55
Reply from 172.217.164.206: bytes=32 time=21ms TTL=55
Reply from 172.217.164.206: bytes=32 time=18ms TTL=55
Reply from 172.217.164.206: bytes=32 time=16ms TTL=55
Reply from 172.217.164.206: bytes=32 time=32ms TTL=55
Reply from 172.217.164.206: bytes=32 time=31ms TTL=55
Reply from 172.217.164.206: bytes=32 time=15ms TTL=55
Reply from 172.217.164.206: bytes=32 time=53ms TTL=55
Reply from 172.217.164.206: bytes=32 time=22ms TTL=55
Reply from 172.217.164.206: bytes=32 time=21ms TTL=55
Reply from 172.217.164.206: bytes=32 time=87ms TTL=55
Reply from 172.217.164.206: bytes=32 time=40ms TTL=55
Reply from 172.217.164.206: bytes=32 time=21ms TTL=55
Reply from 172.217.164.206: bytes=32 time=27ms TTL=55
Reply from 172.217.164.206: bytes=32 time=26ms TTL=55
Reply from 172.217.164.206: bytes=32 time=44ms TTL=55
Reply from 172.217.164.206: bytes=32 time=70ms TTL=55
Reply from 172.217.164.206: bytes=32 time=33ms TTL=55
Reply from 172.217.164.206: bytes=32 time=87ms TTL=55
Reply from 172.217.164.206: bytes=32 time=67ms TTL=55
Reply from 172.217.164.206: bytes=32 time=23ms TTL=55
Reply from 172.217.164.206: bytes=32 time=30ms TTL=55
Reply from 172.217.164.206: bytes=32 time=28ms TTL=55
Reply from 172.217.164.206: bytes=32 time=63ms TTL=55
Reply from 172.217.164.206: bytes=32 time=53ms TTL=55
Reply from 172.217.164.206: bytes=32 time=25ms TTL=55
Reply from 172.217.164.206: bytes=32 time=17ms TTL=55
Reply from 172.217.164.206: bytes=32 time=28ms TTL=55
Reply from 172.217.164.206: bytes=32 time=14ms TTL=55
Reply from 172.217.164.206: bytes=32 time=30ms TTL=55
Reply from 172.217.164.206: bytes=32 time=28ms TTL=55
Reply from 172.217.164.206: bytes=32 time=16ms TTL=55
Reply from 172.217.164.206: bytes=32 time=22ms TTL=55
Reply from 172.217.164.206: bytes=32 time=21ms TTL=55
Reply from 172.217.164.206: bytes=32 time=57ms TTL=55
Reply from 172.217.164.206: bytes=32 time=21ms TTL=55
Reply from 172.217.164.206: bytes=32 time=20ms TTL=55
Reply from 172.217.164.206: bytes=32 time=18ms TTL=55
Reply from 172.217.164.206: bytes=32 time=25ms TTL=55
Reply from 172.217.164.206: bytes=32 time=40ms TTL=55
Reply from 172.217.164.206: bytes=32 time=85ms TTL=55
Reply from 172.217.164.206: bytes=32 time=35ms TTL=55
Reply from 172.217.164.206: bytes=32 time=39ms TTL=55
Reply from 172.217.164.206: bytes=32 time=17ms TTL=55
Reply from 172.217.164.206: bytes=32 time=15ms TTL=55
Reply from 172.217.164.206: bytes=32 time=38ms TTL=55
Reply from 172.217.164.206: bytes=32 time=45ms TTL=55
Reply from 172.217.164.206: bytes=32 time=24ms TTL=55
Reply from 172.217.164.206: bytes=32 time=19ms TTL=55
Reply from 172.217.164.206: bytes=32 time=88ms TTL=55
Reply from 172.217.164.206: bytes=32 time=53ms TTL=55
Reply from 172.217.164.206: bytes=32 time=20ms TTL=55
Reply from 172.217.164.206: bytes=32 time=147ms TTL=55
Reply from 172.217.164.206: bytes=32 time=20ms TTL=55
Reply from 172.217.164.206: bytes=32 time=60ms TTL=55
Reply from 172.217.164.206: bytes=32 time=37ms TTL=55
Reply from 172.217.164.206: bytes=32 time=20ms TTL=55
Request timed out.
Request timed out.
Reply from 172.217.164.206: bytes=32 time=24ms TTL=55
Reply from 172.217.164.206: bytes=32 time=28ms TTL=55
Reply from 172.217.164.206: bytes=32 time=32ms TTL=55
Reply from 172.217.164.206: bytes=32 time=22ms TTL=55
Reply from 172.217.164.206: bytes=32 time=24ms TTL=55
Reply from 172.217.164.206: bytes=32 time=15ms TTL=55
Reply from 172.217.164.206: bytes=32 time=42ms TTL=55
Reply from 172.217.164.206: bytes=32 time=52ms TTL=55
Reply from 172.217.164.206: bytes=32 time=34ms TTL=55
Reply from 172.217.164.206: bytes=32 time=56ms TTL=55
Reply from 172.217.164.206: bytes=32 time=25ms TTL=55
Reply from 172.217.164.206: bytes=32 time=20ms TTL=55
Reply from 172.217.164.206: bytes=32 time=14ms TTL=55

Ping statistics for 172.217.164.206:
Packets: Sent = 81, Received = 79, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 147ms, Average = 35ms

 

Downstream Overview

Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 591000000 256QAM 0.900 7 40.946
2 849000000 256QAM -5.400 2 37.356
3 855000000 256QAM -5.700 3 37.636
4 861000000 256QAM -6.400 4 37.636
5 579000000 256QAM 0.600 5 40.366
6 585000000 256QAM 0.600 6 40.946
7 279000000 256QAM 1.500 1 40.366
8 597000000 256QAM 0.800 8 40.946
9 603000000 256QAM 0.900 9 40.366
10 609000000 256QAM 0.300 10 40.366
11 615000000 256QAM 0.500 11 40.366
12 621000000 256QAM -0.300 12 40.366
13 633000000 256QAM -0.500 13 40.366
14 639000000 256QAM -0.100 14 40.366
15 645000000 256QAM 0.100 15 40.946
16 651000000 256QAM 0.400 16 40.366
17 657000000 256QAM 0.300 17 40.366
18 663000000 256QAM 0.700 18 40.946
19 669000000 256QAM 0.800 19 40.946
20 675000000 256QAM 0.500 20 40.946
21 681000000 256QAM 0.000 21 40.366
22 687000000 256QAM -0.100 22 40.366
23 693000000 256QAM -0.700 23 40.946
24 699000000 256QAM -0.900 24 40.366
25 705000000 256QAM -1.500 25 40.366
26 711000000 256QAM -1.500 26 40.366
27 717000000 256QAM -2.100 27 38.983
28 723000000 256QAM -1.700 28 40.366
29 825000000 256QAM -4.500 29 38.983
30 831000000 256QAM -4.300 30 38.983
31 837000000 256QAM -4.400 31 38.605
32 843000000 256QAM -5.000 32 38.605

 

Upstream Overview

Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 22100000 ATDMA - 64QAM 32.500 1 3200000
2 36996000 ATDMA - 64QAM 31.500 4 6400000
3 30596000 ATDMA - 64QAM 31.250 3 6400000
4 25300000 ATDMA - 64QAM 32.750 2 3200000

 

super_robot
I Plan to Stick Around
Posts: 64

Re: Brutal latency/ping Recently

Here's some information. Latency is bad, upload speed is bad, packet loss(not caught in info below). Being at home 24/7 makes this very irritating. 

 

1 * * * Request timed out.
2 29 ms 89 ms 32 ms 
3 77 ms 151 ms 62 ms 8082-dgw01.etob.rmgt.net.rogers.com [67.231.220.33]
4 73 ms 51 ms 44 ms 0-5-0-7-cgw01.wlfdle.rmgt.net.rogers.com [209.148.231.209]
5 68 ms 58 ms 56 ms 209.148.235.141
6 * * * Request timed out.
7 73 ms 29 ms 41 ms 108.170.250.241
8 20 ms 101 ms 27 ms 108.170.226.217
9 53 ms 50 ms 54 ms yyz10s03-in-f3.1e100.net [172.217.0.227]

 

Ping statistics for 172.217.0.227:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 183ms, Average = 50ms

 

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1633000000256QAM1.2001338.983
2621000000256QAM1.7001240.366
3639000000256QAM1.5001440.366
4645000000256QAM-0.1001540.946
5651000000256QAM0.3001640.366
6657000000256QAM0.1001740.366
7663000000256QAM-0.1001840.366
8669000000256QAM1.2001940.946
9675000000256QAM0.5002040.946
10681000000256QAM1.3002140.946
11687000000256QAM0.6002240.366
12693000000256QAM0.4002340.366
13699000000256QAM0.4002440.366
14705000000256QAM0.1002540.366
15711000000256QAM1.5002640.366
16717000000256QAM1.5002740.366
17723000000256QAM1.5002840.366
18825000000256QAM-1.5002940.366
19831000000256QAM-2.2003038.983
20837000000256QAM-2.9003138.983
21843000000256QAM-2.6003238.983
22849000000256QAM-3.600238.983
23855000000256QAM-2.600340.366
24861000000256QAM-2.700438.983
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
136996000ATDMA - 64QAM49.25046400000
222100000ATDMA - 64QAM45.25013200000
330596000ATDMA - 64QAM47.75036400000
425300000ATDMA - 64QAM46.00023200000

 

 

 

 

Speed test download is fine (300mb) but Upload varies between 1mb-2mb and I should be getting 15.

 

 

 

 

Mike_x_Wilk
I Plan to Stick Around
Posts: 10

Re: Brutal latency/ping Recently

Well, after the tech was at the house he said he would submit a ticket to engineering. When nothing happened for a week I made some additional contact noting the promise of the ticket being submitted as well as describing the issue as an upstream only issue and pointed them to this thread. Within a few hours my modem rebooted on its own in the middle of the day while I was on. That didn't seem to do anything. Then a hour or so later my modem was remote updated with new firmware. It took about 15 minutes of flashing red and green before it was done. Since then... no issues. Rogers never acknowledged the problem or contacted me about what they were going to do, but whatever they did it worked.

rivx
I'm Here A Lot
Posts: 5

Re: Brutal latency/ping Recently

@Mike_x_Wilk what firmware are you on?

ignOred
I'm Here A Lot
Posts: 5

Re: Brutal latency/ping Recently

I'm in the same boat as you. Have had COUNTLESS techs visit with no resolution - Rogers 'support' refuses to acknowledge that it's an issue on their end. I don't know what else I can do. Can we at least get an update or SOME form of communication from Rogers that they're at least TRYING to fix this issue?

herrshaun
I Plan to Stick Around
Posts: 71

Re: Brutal latency/ping Recently

@Mike_x_Wilk Please give us some more info on this. I am currently ping testing while on webcam, and am getting way more spikes than when I've been just playing games and watching videos.

 

What firmware is the new one? @CommunityHelps is this available for us as well?

herrshaun
I Plan to Stick Around
Posts: 71

Re: Brutal latency/ping Recently

Is anyone still here? Is the thread locked? Why'd it get so quiet?

 

Still getting the odd ping spike and would love to know what the status is on the firmware.

-G-
Resident Expert
Resident Expert
Posts: 2,468

Re: Brutal latency/ping Recently

For me, when I run ping tests to 8.8.8.8, I usually see RTTs < 15 ms but I also regularly see spikes in the 40 - 120 ms range.  I know that is still not great for many of you but those spikes are now 100-times lower than they were before.



super_robot
I Plan to Stick Around
Posts: 64

Re: Brutal latency/ping Recently

I think people much like myself have given up or moved on and ordered BELL.

 

Same story here 

 

Pinging www.google.ca [172.217.1.163] with 32 bytes of data:
Reply from 172.217.1.163: bytes=32 time=47ms TTL=55
Reply from 172.217.1.163: bytes=32 time=29ms TTL=55
Reply from 172.217.1.163: bytes=32 time=13ms TTL=55
Reply from 172.217.1.163: bytes=32 time=31ms TTL=55
Reply from 172.217.1.163: bytes=32 time=64ms TTL=55
Reply from 172.217.1.163: bytes=32 time=78ms TTL=55
Reply from 172.217.1.163: bytes=32 time=16ms TTL=55
Reply from 172.217.1.163: bytes=32 time=283ms TTL=55
Reply from 172.217.1.163: bytes=32 time=95ms TTL=55
Reply from 172.217.1.163: bytes=32 time=33ms TTL=55
Reply from 172.217.1.163: bytes=32 time=72ms TTL=55
Reply from 172.217.1.163: bytes=32 time=35ms TTL=55
Reply from 172.217.1.163: bytes=32 time=137ms TTL=55
Reply from 172.217.1.163: bytes=32 time=35ms TTL=55

 

 

Tracing route to www.google.ca [172.217.1.163]
over a maximum of 30 hops:

1 * * * Request timed out.
2 57 ms 152 ms 44 ms
3 77 ms 37 ms 62 ms 8082-dgw02.etob.rmgt.net.rogers.com [67.231.220.37]
4 41 ms 49 ms 50 ms 0-15-0-6-cgw01.bloor.rmgt.net.rogers.com [209.148.232.141]
5 114 ms 50 ms 41 ms 209.148.235.30

 

 

Upload still garbage (1-2mb) instead of 15, been through many tickets, technicians. It's pretty obvious to me that their infrastructure cannot handle the current load given the circumstances though they will never admit it.