cancel
Showing results for 
Search instead for 
Did you mean: 

Brutal latency/ping Recently

t27c
I plan to stick around

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 ***

956 REPLIES 956

Re: Brutal latency/ping Recently

I have been complaining to Rogers For years regarding online gaming with high latency and still no fix .. good luck !

Re: Brutal latency/ping Recently

herrshaun
I plan to stick around

So I guess the maintenance wasn't done yet at the time of my post. Got a text the next morning that it was completed. The packet loss has ceased and the pings are mostly in good shape. I will keep an eye on it.

Re: Brutal latency/ping Recently

chemical1
I plan to stick around

Sadly Rogers is my only choice where I live and the issue is still alive and well.  Thought this needed a bump.  Hopefully there will be some network upgrades this year 🙂

Re: Brutal latency/ping Recently

Same issue here,

ping between my computer and modem is 100% successfull,

ping to google.ca gives me tons of intermittent failures currently 13% failure this morning Jan 6th 2021,

Rogers, please give us the 2021 we deserve and fix this latency/packet loss issue!!

I can't keep a connection for working from home!!! 

Re: Brutal latency/ping Recently

borisnet
I plan to stick around

Same here, happened twice today between 11:41 and 11:48 and again between 15:12 and 15:15.

I have opened a ticket a month ago, provided input each time I experienced the issue, asked for escalation and nothing happened. This is depressing.

 

The network must be congested, affecting TCP and UDP while ICMP (ping) is buffered showing the wonderful response time up to 37 seconds... see below

 

What is the best way to get assistance on this?

I monitor all my home infrastructure and everything is clear. Problem lasts only a few minutes but is painful enough to get the entire household incapable of working online.

I confirm it was all clean before the date of the first post on this thread. I was even surprised it was so reliable at the beginning of the pandemic. Sadly, the problem remains and it is very hard to be in touch with anybody with the right skills to confirm the problem on their infrastructure.

I even asked to confirm whether the CMTS infra or the IP infrastructure was at capacity with no reply whatsoever.

 

Captured today for reference:

 

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=20287 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=116 time=19714 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=116 time=18773 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=116 time=17798 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=116 time=16835 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=116 time=15857 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=116 time=14889 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=116 time=13921 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=116 time=12957 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=116 time=12005 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=116 time=11030 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=116 time=10081 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=116 time=9104 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=116 time=8142 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=116 time=7177 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=116 time=6211 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=116 time=5234 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=116 time=4269 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=116 time=3288 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=116 time=2313 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=116 time=1354 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=116 time=449 ms
64 bytes from 8.8.8.8: icmp_seq=28 ttl=116 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=29 ttl=116 time=24.2 ms
64 bytes from 8.8.8.8: icmp_seq=30 ttl=116 time=22.9 ms
64 bytes from 8.8.8.8: icmp_seq=31 ttl=116 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=32 ttl=116 time=22.5 ms
64 bytes from 8.8.8.8: icmp_seq=33 ttl=116 time=29.5 ms
64 bytes from 8.8.8.8: icmp_seq=34 ttl=116 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=35 ttl=116 time=26.3 ms
64 bytes from 8.8.8.8: icmp_seq=36 ttl=116 time=53.0 ms
64 bytes from 8.8.8.8: icmp_seq=37 ttl=116 time=22.9 ms
64 bytes from 8.8.8.8: icmp_seq=38 ttl=116 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=39 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=40 ttl=116 time=24.7 ms
64 bytes from 8.8.8.8: icmp_seq=41 ttl=116 time=28.6 ms
64 bytes from 8.8.8.8: icmp_seq=42 ttl=116 time=18.3 ms
64 bytes from 8.8.8.8: icmp_seq=43 ttl=116 time=24.8 ms
64 bytes from 8.8.8.8: icmp_seq=44 ttl=116 time=28.1 ms
64 bytes from 8.8.8.8: icmp_seq=45 ttl=116 time=22.5 ms
64 bytes from 8.8.8.8: icmp_seq=46 ttl=116 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=47 ttl=116 time=16.7 ms
64 bytes from 8.8.8.8: icmp_seq=48 ttl=116 time=24.4 ms
64 bytes from 8.8.8.8: icmp_seq=49 ttl=116 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=50 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=51 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=52 ttl=116 time=20.9 ms
64 bytes from 8.8.8.8: icmp_seq=53 ttl=116 time=28.6 ms
64 bytes from 8.8.8.8: icmp_seq=54 ttl=116 time=22.1 ms
64 bytes from 8.8.8.8: icmp_seq=55 ttl=116 time=19.7 ms
64 bytes from 8.8.8.8: icmp_seq=56 ttl=116 time=31.4 ms
64 bytes from 8.8.8.8: icmp_seq=57 ttl=116 time=17.4 ms
64 bytes from 8.8.8.8: icmp_seq=58 ttl=116 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=59 ttl=116 time=21.9 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=116 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=116 time=26.1 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=116 time=16.7 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=116 time=19.8 ms
64 bytes from 8.8.8.8: icmp_seq=64 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=65 ttl=116 time=21.4 ms
64 bytes from 8.8.8.8: icmp_seq=66 ttl=116 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=67 ttl=116 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=68 ttl=116 time=37.1 ms
64 bytes from 8.8.8.8: icmp_seq=69 ttl=116 time=46.3 ms
64 bytes from 8.8.8.8: icmp_seq=70 ttl=116 time=48.1 ms
64 bytes from 8.8.8.8: icmp_seq=71 ttl=116 time=17.3 ms
64 bytes from 8.8.8.8: icmp_seq=72 ttl=116 time=21.5 ms
64 bytes from 8.8.8.8: icmp_seq=73 ttl=116 time=19.2 ms
64 bytes from 8.8.8.8: icmp_seq=74 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=75 ttl=116 time=20.8 ms
64 bytes from 8.8.8.8: icmp_seq=76 ttl=116 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=77 ttl=116 time=17.2 ms
64 bytes from 8.8.8.8: icmp_seq=78 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=79 ttl=116 time=27.8 ms
64 bytes from 8.8.8.8: icmp_seq=80 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=81 ttl=116 time=19.4 ms
64 bytes from 8.8.8.8: icmp_seq=82 ttl=116 time=20.9 ms
64 bytes from 8.8.8.8: icmp_seq=83 ttl=116 time=18.6 ms
64 bytes from 8.8.8.8: icmp_seq=84 ttl=116 time=29.0 ms
64 bytes from 8.8.8.8: icmp_seq=85 ttl=116 time=25.8 ms
64 bytes from 8.8.8.8: icmp_seq=86 ttl=116 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=87 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=88 ttl=116 time=16.8 ms
64 bytes from 8.8.8.8: icmp_seq=89 ttl=116 time=24.7 ms
64 bytes from 8.8.8.8: icmp_seq=90 ttl=116 time=18.8 ms
64 bytes from 8.8.8.8: icmp_seq=91 ttl=116 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=116 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=116 time=16.9 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=116 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=116 time=21.0 ms
64 bytes from 8.8.8.8: icmp_seq=96 ttl=116 time=19.9 ms
64 bytes from 8.8.8.8: icmp_seq=97 ttl=116 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=98 ttl=116 time=21.5 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=116 time=27.2 ms
64 bytes from 8.8.8.8: icmp_seq=100 ttl=116 time=26.1 ms
64 bytes from 8.8.8.8: icmp_seq=101 ttl=116 time=24.8 ms
64 bytes from 8.8.8.8: icmp_seq=102 ttl=116 time=16.0 ms
64 bytes from 8.8.8.8: icmp_seq=103 ttl=116 time=27.1 ms
64 bytes from 8.8.8.8: icmp_seq=104 ttl=116 time=21.7 ms
64 bytes from 8.8.8.8: icmp_seq=105 ttl=116 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=106 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=107 ttl=116 time=23.7 ms
64 bytes from 8.8.8.8: icmp_seq=108 ttl=116 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=109 ttl=116 time=44.7 ms
64 bytes from 8.8.8.8: icmp_seq=110 ttl=116 time=30.9 ms
64 bytes from 8.8.8.8: icmp_seq=111 ttl=116 time=51.4 ms
64 bytes from 8.8.8.8: icmp_seq=112 ttl=116 time=16.5 ms
64 bytes from 8.8.8.8: icmp_seq=113 ttl=116 time=32.7 ms
64 bytes from 8.8.8.8: icmp_seq=114 ttl=116 time=15.9 ms
64 bytes from 8.8.8.8: icmp_seq=115 ttl=116 time=18.0 ms
64 bytes from 8.8.8.8: icmp_seq=116 ttl=116 time=25.6 ms
64 bytes from 8.8.8.8: icmp_seq=117 ttl=116 time=21.8 ms
64 bytes from 8.8.8.8: icmp_seq=118 ttl=116 time=13.9 ms
64 bytes from 8.8.8.8: icmp_seq=119 ttl=116 time=19.4 ms
64 bytes from 8.8.8.8: icmp_seq=120 ttl=116 time=19.2 ms
64 bytes from 8.8.8.8: icmp_seq=121 ttl=116 time=25.9 ms
64 bytes from 8.8.8.8: icmp_seq=122 ttl=116 time=20.9 ms
64 bytes from 8.8.8.8: icmp_seq=123 ttl=116 time=19.8 ms
64 bytes from 8.8.8.8: icmp_seq=124 ttl=116 time=21.3 ms
64 bytes from 8.8.8.8: icmp_seq=125 ttl=116 time=16.3 ms
64 bytes from 8.8.8.8: icmp_seq=126 ttl=116 time=17.9 ms
64 bytes from 8.8.8.8: icmp_seq=127 ttl=116 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=128 ttl=116 time=19.9 ms
64 bytes from 8.8.8.8: icmp_seq=129 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=130 ttl=116 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=131 ttl=116 time=17.7 ms
64 bytes from 8.8.8.8: icmp_seq=132 ttl=116 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=133 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=134 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=135 ttl=116 time=20.9 ms
64 bytes from 8.8.8.8: icmp_seq=136 ttl=116 time=22.2 ms
64 bytes from 8.8.8.8: icmp_seq=137 ttl=116 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=138 ttl=116 time=20.7 ms
64 bytes from 8.8.8.8: icmp_seq=139 ttl=116 time=19.2 ms
64 bytes from 8.8.8.8: icmp_seq=140 ttl=116 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=141 ttl=116 time=21.9 ms
64 bytes from 8.8.8.8: icmp_seq=142 ttl=116 time=24.5 ms
64 bytes from 8.8.8.8: icmp_seq=143 ttl=116 time=20.9 ms
64 bytes from 8.8.8.8: icmp_seq=144 ttl=116 time=22.4 ms
64 bytes from 8.8.8.8: icmp_seq=145 ttl=116 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=146 ttl=116 time=17.8 ms
64 bytes from 8.8.8.8: icmp_seq=147 ttl=116 time=22.4 ms
64 bytes from 8.8.8.8: icmp_seq=148 ttl=116 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=149 ttl=116 time=24.9 ms
64 bytes from 8.8.8.8: icmp_seq=150 ttl=116 time=23.4 ms
64 bytes from 8.8.8.8: icmp_seq=151 ttl=116 time=25.5 ms
64 bytes from 8.8.8.8: icmp_seq=152 ttl=116 time=32.5 ms
64 bytes from 8.8.8.8: icmp_seq=153 ttl=116 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=154 ttl=116 time=25.7 ms
64 bytes from 8.8.8.8: icmp_seq=155 ttl=116 time=22.1 ms
64 bytes from 8.8.8.8: icmp_seq=156 ttl=116 time=27.5 ms
64 bytes from 8.8.8.8: icmp_seq=157 ttl=116 time=29.1 ms
64 bytes from 8.8.8.8: icmp_seq=158 ttl=116 time=12.1 ms
64 bytes from 8.8.8.8: icmp_seq=159 ttl=116 time=22.9 ms
64 bytes from 8.8.8.8: icmp_seq=160 ttl=116 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=161 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=162 ttl=116 time=20.8 ms
64 bytes from 8.8.8.8: icmp_seq=163 ttl=116 time=19.7 ms
64 bytes from 8.8.8.8: icmp_seq=164 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=165 ttl=116 time=21.8 ms
64 bytes from 8.8.8.8: icmp_seq=166 ttl=116 time=21.2 ms
64 bytes from 8.8.8.8: icmp_seq=167 ttl=116 time=26.6 ms
64 bytes from 8.8.8.8: icmp_seq=168 ttl=116 time=33.8 ms
64 bytes from 8.8.8.8: icmp_seq=169 ttl=116 time=25.3 ms
64 bytes from 8.8.8.8: icmp_seq=170 ttl=116 time=22.3 ms
64 bytes from 8.8.8.8: icmp_seq=171 ttl=116 time=24.9 ms
64 bytes from 8.8.8.8: icmp_seq=172 ttl=116 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=173 ttl=116 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=174 ttl=116 time=19.2 ms
64 bytes from 8.8.8.8: icmp_seq=175 ttl=116 time=20.5 ms
64 bytes from 8.8.8.8: icmp_seq=176 ttl=116 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=177 ttl=116 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=178 ttl=116 time=23.2 ms
64 bytes from 8.8.8.8: icmp_seq=179 ttl=116 time=17.4 ms
64 bytes from 8.8.8.8: icmp_seq=180 ttl=116 time=18.3 ms
64 bytes from 8.8.8.8: icmp_seq=181 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=182 ttl=116 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=183 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=184 ttl=116 time=16.0 ms
64 bytes from 8.8.8.8: icmp_seq=185 ttl=116 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=186 ttl=116 time=20.8 ms
64 bytes from 8.8.8.8: icmp_seq=187 ttl=116 time=5726 ms
64 bytes from 8.8.8.8: icmp_seq=188 ttl=116 time=4732 ms
64 bytes from 8.8.8.8: icmp_seq=189 ttl=116 time=3739 ms
64 bytes from 8.8.8.8: icmp_seq=190 ttl=116 time=2745 ms
64 bytes from 8.8.8.8: icmp_seq=191 ttl=116 time=1750 ms
64 bytes from 8.8.8.8: icmp_seq=192 ttl=116 time=757 ms
64 bytes from 8.8.8.8: icmp_seq=193 ttl=116 time=46.5 ms
64 bytes from 8.8.8.8: icmp_seq=194 ttl=116 time=37.0 ms
64 bytes from 8.8.8.8: icmp_seq=195 ttl=116 time=26.6 ms
64 bytes from 8.8.8.8: icmp_seq=196 ttl=116 time=18.6 ms
64 bytes from 8.8.8.8: icmp_seq=197 ttl=116 time=36.9 ms
64 bytes from 8.8.8.8: icmp_seq=198 ttl=116 time=17.8 ms
64 bytes from 8.8.8.8: icmp_seq=199 ttl=116 time=15.8 ms
64 bytes from 8.8.8.8: icmp_seq=200 ttl=116 time=30.5 ms
64 bytes from 8.8.8.8: icmp_seq=201 ttl=116 time=16.4 ms
64 bytes from 8.8.8.8: icmp_seq=202 ttl=116 time=19.9 ms
64 bytes from 8.8.8.8: icmp_seq=203 ttl=116 time=22.3 ms
64 bytes from 8.8.8.8: icmp_seq=204 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=205 ttl=116 time=29628 ms
64 bytes from 8.8.8.8: icmp_seq=206 ttl=116 time=28624 ms
64 bytes from 8.8.8.8: icmp_seq=207 ttl=116 time=27627 ms
64 bytes from 8.8.8.8: icmp_seq=208 ttl=116 time=26642 ms
64 bytes from 8.8.8.8: icmp_seq=209 ttl=116 time=25648 ms
64 bytes from 8.8.8.8: icmp_seq=210 ttl=116 time=24654 ms
64 bytes from 8.8.8.8: icmp_seq=211 ttl=116 time=23676 ms
64 bytes from 8.8.8.8: icmp_seq=212 ttl=116 time=22697 ms
64 bytes from 8.8.8.8: icmp_seq=213 ttl=116 time=21707 ms
64 bytes from 8.8.8.8: icmp_seq=214 ttl=116 time=20755 ms
64 bytes from 8.8.8.8: icmp_seq=215 ttl=116 time=19758 ms
64 bytes from 8.8.8.8: icmp_seq=216 ttl=116 time=18767 ms
64 bytes from 8.8.8.8: icmp_seq=217 ttl=116 time=17776 ms
64 bytes from 8.8.8.8: icmp_seq=218 ttl=116 time=16801 ms
64 bytes from 8.8.8.8: icmp_seq=219 ttl=116 time=15835 ms
64 bytes from 8.8.8.8: icmp_seq=220 ttl=116 time=14919 ms
64 bytes from 8.8.8.8: icmp_seq=221 ttl=116 time=13957 ms
64 bytes from 8.8.8.8: icmp_seq=222 ttl=116 time=12986 ms
64 bytes from 8.8.8.8: icmp_seq=223 ttl=116 time=12045 ms
64 bytes from 8.8.8.8: icmp_seq=224 ttl=116 time=11066 ms
64 bytes from 8.8.8.8: icmp_seq=225 ttl=116 time=10089 ms
64 bytes from 8.8.8.8: icmp_seq=226 ttl=116 time=9100 ms
64 bytes from 8.8.8.8: icmp_seq=227 ttl=116 time=8103 ms
64 bytes from 8.8.8.8: icmp_seq=228 ttl=116 time=7129 ms
64 bytes from 8.8.8.8: icmp_seq=229 ttl=116 time=6135 ms
64 bytes from 8.8.8.8: icmp_seq=230 ttl=116 time=5165 ms
64 bytes from 8.8.8.8: icmp_seq=231 ttl=116 time=4144 ms
64 bytes from 8.8.8.8: icmp_seq=232 ttl=116 time=3154 ms
64 bytes from 8.8.8.8: icmp_seq=233 ttl=116 time=2161 ms
64 bytes from 8.8.8.8: icmp_seq=234 ttl=116 time=1206 ms
64 bytes from 8.8.8.8: icmp_seq=235 ttl=116 time=415 ms
64 bytes from 8.8.8.8: icmp_seq=236 ttl=116 time=17.9 ms
64 bytes from 8.8.8.8: icmp_seq=237 ttl=116 time=43.3 ms
64 bytes from 8.8.8.8: icmp_seq=238 ttl=116 time=32.6 ms
64 bytes from 8.8.8.8: icmp_seq=239 ttl=116 time=22.2 ms
64 bytes from 8.8.8.8: icmp_seq=240 ttl=116 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=241 ttl=116 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=242 ttl=116 time=36.7 ms
64 bytes from 8.8.8.8: icmp_seq=243 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=244 ttl=116 time=26.7 ms
64 bytes from 8.8.8.8: icmp_seq=245 ttl=116 time=35.0 ms
64 bytes from 8.8.8.8: icmp_seq=246 ttl=116 time=22.3 ms
64 bytes from 8.8.8.8: icmp_seq=247 ttl=116 time=21.0 ms
64 bytes from 8.8.8.8: icmp_seq=248 ttl=116 time=21.5 ms
64 bytes from 8.8.8.8: icmp_seq=249 ttl=116 time=20.4 ms
64 bytes from 8.8.8.8: icmp_seq=250 ttl=116 time=17.3 ms
64 bytes from 8.8.8.8: icmp_seq=251 ttl=116 time=17.4 ms
64 bytes from 8.8.8.8: icmp_seq=252 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=253 ttl=116 time=17.7 ms
64 bytes from 8.8.8.8: icmp_seq=254 ttl=116 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=255 ttl=116 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=256 ttl=116 time=489 ms
64 bytes from 8.8.8.8: icmp_seq=257 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=258 ttl=116 time=19.2 ms
64 bytes from 8.8.8.8: icmp_seq=259 ttl=116 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=260 ttl=116 time=21.2 ms
64 bytes from 8.8.8.8: icmp_seq=261 ttl=116 time=15.8 ms
64 bytes from 8.8.8.8: icmp_seq=262 ttl=116 time=13771 ms
64 bytes from 8.8.8.8: icmp_seq=263 ttl=116 time=12764 ms
64 bytes from 8.8.8.8: icmp_seq=264 ttl=116 time=11744 ms
64 bytes from 8.8.8.8: icmp_seq=265 ttl=116 time=10726 ms
64 bytes from 8.8.8.8: icmp_seq=266 ttl=116 time=9709 ms
64 bytes from 8.8.8.8: icmp_seq=267 ttl=116 time=8691 ms
64 bytes from 8.8.8.8: icmp_seq=268 ttl=116 time=7682 ms
64 bytes from 8.8.8.8: icmp_seq=269 ttl=116 time=6672 ms
64 bytes from 8.8.8.8: icmp_seq=270 ttl=116 time=5659 ms
64 bytes from 8.8.8.8: icmp_seq=271 ttl=116 time=4642 ms
64 bytes from 8.8.8.8: icmp_seq=272 ttl=116 time=3632 ms
64 bytes from 8.8.8.8: icmp_seq=273 ttl=116 time=2619 ms
64 bytes from 8.8.8.8: icmp_seq=274 ttl=116 time=1636 ms
64 bytes from 8.8.8.8: icmp_seq=275 ttl=116 time=650 ms
64 bytes from 8.8.8.8: icmp_seq=276 ttl=116 time=32.0 ms
64 bytes from 8.8.8.8: icmp_seq=277 ttl=116 time=55.4 ms
64 bytes from 8.8.8.8: icmp_seq=278 ttl=116 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=279 ttl=116 time=24.4 ms
64 bytes from 8.8.8.8: icmp_seq=280 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=281 ttl=116 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=282 ttl=116 time=16.7 ms
64 bytes from 8.8.8.8: icmp_seq=283 ttl=116 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=284 ttl=116 time=18.4 ms
64 bytes from 8.8.8.8: icmp_seq=285 ttl=116 time=26.6 ms
64 bytes from 8.8.8.8: icmp_seq=286 ttl=116 time=20.7 ms
64 bytes from 8.8.8.8: icmp_seq=287 ttl=116 time=18.5 ms
64 bytes from 8.8.8.8: icmp_seq=288 ttl=116 time=20.4 ms
64 bytes from 8.8.8.8: icmp_seq=289 ttl=116 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=290 ttl=116 time=18.6 ms
64 bytes from 8.8.8.8: icmp_seq=291 ttl=116 time=23.7 ms
64 bytes from 8.8.8.8: icmp_seq=292 ttl=116 time=21.2 ms
64 bytes from 8.8.8.8: icmp_seq=293 ttl=116 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=294 ttl=116 time=39.7 ms
64 bytes from 8.8.8.8: icmp_seq=295 ttl=116 time=17.6 ms
64 bytes from 8.8.8.8: icmp_seq=296 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=297 ttl=116 time=32.5 ms
64 bytes from 8.8.8.8: icmp_seq=298 ttl=116 time=18.0 ms
64 bytes from 8.8.8.8: icmp_seq=299 ttl=116 time=37.7 ms
64 bytes from 8.8.8.8: icmp_seq=300 ttl=116 time=22.9 ms
64 bytes from 8.8.8.8: icmp_seq=301 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=302 ttl=116 time=21.9 ms
64 bytes from 8.8.8.8: icmp_seq=303 ttl=116 time=32.7 ms
64 bytes from 8.8.8.8: icmp_seq=304 ttl=116 time=55.2 ms
64 bytes from 8.8.8.8: icmp_seq=305 ttl=116 time=18.4 ms
64 bytes from 8.8.8.8: icmp_seq=306 ttl=116 time=22.6 ms
64 bytes from 8.8.8.8: icmp_seq=307 ttl=116 time=20.8 ms
64 bytes from 8.8.8.8: icmp_seq=308 ttl=116 time=18.5 ms
64 bytes from 8.8.8.8: icmp_seq=309 ttl=116 time=24.0 ms
64 bytes from 8.8.8.8: icmp_seq=310 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=311 ttl=116 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=312 ttl=116 time=21.5 ms
64 bytes from 8.8.8.8: icmp_seq=313 ttl=116 time=13.8 ms
64 bytes from 8.8.8.8: icmp_seq=314 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=315 ttl=116 time=2357 ms
64 bytes from 8.8.8.8: icmp_seq=316 ttl=116 time=1333 ms
64 bytes from 8.8.8.8: icmp_seq=317 ttl=116 time=311 ms
64 bytes from 8.8.8.8: icmp_seq=318 ttl=116 time=26.0 ms
64 bytes from 8.8.8.8: icmp_seq=319 ttl=116 time=29.4 ms
64 bytes from 8.8.8.8: icmp_seq=320 ttl=116 time=25.3 ms
64 bytes from 8.8.8.8: icmp_seq=321 ttl=116 time=21.3 ms
64 bytes from 8.8.8.8: icmp_seq=322 ttl=116 time=27.2 ms
64 bytes from 8.8.8.8: icmp_seq=323 ttl=116 time=31.7 ms
64 bytes from 8.8.8.8: icmp_seq=324 ttl=116 time=37.4 ms
64 bytes from 8.8.8.8: icmp_seq=325 ttl=116 time=18.9 ms
64 bytes from 8.8.8.8: icmp_seq=326 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=327 ttl=116 time=24.5 ms
64 bytes from 8.8.8.8: icmp_seq=328 ttl=116 time=19.8 ms
64 bytes from 8.8.8.8: icmp_seq=329 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=330 ttl=116 time=21.6 ms
64 bytes from 8.8.8.8: icmp_seq=331 ttl=116 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=332 ttl=116 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=333 ttl=116 time=16.3 ms
64 bytes from 8.8.8.8: icmp_seq=334 ttl=116 time=21.3 ms
64 bytes from 8.8.8.8: icmp_seq=335 ttl=116 time=19.4 ms
64 bytes from 8.8.8.8: icmp_seq=336 ttl=116 time=21.0 ms
64 bytes from 8.8.8.8: icmp_seq=337 ttl=116 time=17.7 ms
64 bytes from 8.8.8.8: icmp_seq=338 ttl=116 time=26.5 ms
64 bytes from 8.8.8.8: icmp_seq=339 ttl=116 time=25.1 ms
64 bytes from 8.8.8.8: icmp_seq=340 ttl=116 time=22.0 ms
64 bytes from 8.8.8.8: icmp_seq=341 ttl=116 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=342 ttl=116 time=16.9 ms
64 bytes from 8.8.8.8: icmp_seq=343 ttl=116 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=344 ttl=116 time=21.9 ms
64 bytes from 8.8.8.8: icmp_seq=345 ttl=116 time=17.4 ms
64 bytes from 8.8.8.8: icmp_seq=346 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=347 ttl=116 time=21.9 ms
64 bytes from 8.8.8.8: icmp_seq=348 ttl=116 time=23.2 ms
64 bytes from 8.8.8.8: icmp_seq=349 ttl=116 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=350 ttl=116 time=20.7 ms
64 bytes from 8.8.8.8: icmp_seq=351 ttl=116 time=16.8 ms
64 bytes from 8.8.8.8: icmp_seq=352 ttl=116 time=24.5 ms
64 bytes from 8.8.8.8: icmp_seq=353 ttl=116 time=29.6 ms
64 bytes from 8.8.8.8: icmp_seq=354 ttl=116 time=23.5 ms
64 bytes from 8.8.8.8: icmp_seq=355 ttl=116 time=21.7 ms
64 bytes from 8.8.8.8: icmp_seq=356 ttl=116 time=18.5 ms
64 bytes from 8.8.8.8: icmp_seq=357 ttl=116 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=358 ttl=116 time=17.2 ms
64 bytes from 8.8.8.8: icmp_seq=359 ttl=116 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=360 ttl=116 time=30.2 ms
64 bytes from 8.8.8.8: icmp_seq=361 ttl=116 time=35.9 ms
64 bytes from 8.8.8.8: icmp_seq=362 ttl=116 time=28.5 ms
64 bytes from 8.8.8.8: icmp_seq=363 ttl=116 time=24.4 ms
64 bytes from 8.8.8.8: icmp_seq=364 ttl=116 time=37124 ms
64 bytes from 8.8.8.8: icmp_seq=365 ttl=116 time=36107 ms
64 bytes from 8.8.8.8: icmp_seq=366 ttl=116 time=35121 ms
64 bytes from 8.8.8.8: icmp_seq=367 ttl=116 time=34136 ms
64 bytes from 8.8.8.8: icmp_seq=368 ttl=116 time=33155 ms
64 bytes from 8.8.8.8: icmp_seq=369 ttl=116 time=32167 ms
64 bytes from 8.8.8.8: icmp_seq=370 ttl=116 time=31189 ms
64 bytes from 8.8.8.8: icmp_seq=371 ttl=116 time=30216 ms
64 bytes from 8.8.8.8: icmp_seq=372 ttl=116 time=29229 ms
64 bytes from 8.8.8.8: icmp_seq=373 ttl=116 time=28277 ms
64 bytes from 8.8.8.8: icmp_seq=374 ttl=116 time=27299 ms
64 bytes from 8.8.8.8: icmp_seq=375 ttl=116 time=26314 ms
64 bytes from 8.8.8.8: icmp_seq=376 ttl=116 time=25318 ms
64 bytes from 8.8.8.8: icmp_seq=377 ttl=116 time=24360 ms
64 bytes from 8.8.8.8: icmp_seq=378 ttl=116 time=23379 ms
64 bytes from 8.8.8.8: icmp_seq=379 ttl=116 time=22429 ms
64 bytes from 8.8.8.8: icmp_seq=380 ttl=116 time=21446 ms
64 bytes from 8.8.8.8: icmp_seq=381 ttl=116 time=20456 ms
64 bytes from 8.8.8.8: icmp_seq=382 ttl=116 time=19493 ms
64 bytes from 8.8.8.8: icmp_seq=383 ttl=116 time=18524 ms
64 bytes from 8.8.8.8: icmp_seq=384 ttl=116 time=17538 ms
64 bytes from 8.8.8.8: icmp_seq=385 ttl=116 time=16546 ms
64 bytes from 8.8.8.8: icmp_seq=386 ttl=116 time=15559 ms
64 bytes from 8.8.8.8: icmp_seq=387 ttl=116 time=14561 ms
64 bytes from 8.8.8.8: icmp_seq=388 ttl=116 time=13558 ms
64 bytes from 8.8.8.8: icmp_seq=389 ttl=116 time=12551 ms
64 bytes from 8.8.8.8: icmp_seq=390 ttl=116 time=11548 ms
64 bytes from 8.8.8.8: icmp_seq=391 ttl=116 time=10547 ms
64 bytes from 8.8.8.8: icmp_seq=392 ttl=116 time=9540 ms
64 bytes from 8.8.8.8: icmp_seq=393 ttl=116 time=8555 ms
64 bytes from 8.8.8.8: icmp_seq=394 ttl=116 time=7551 ms
64 bytes from 8.8.8.8: icmp_seq=395 ttl=116 time=6549 ms
64 bytes from 8.8.8.8: icmp_seq=396 ttl=116 time=5555 ms
64 bytes from 8.8.8.8: icmp_seq=397 ttl=116 time=4552 ms
64 bytes from 8.8.8.8: icmp_seq=398 ttl=116 time=3542 ms
64 bytes from 8.8.8.8: icmp_seq=399 ttl=116 time=2539 ms
64 bytes from 8.8.8.8: icmp_seq=400 ttl=116 time=1528 ms
64 bytes from 8.8.8.8: icmp_seq=401 ttl=116 time=587 ms
64 bytes from 8.8.8.8: icmp_seq=402 ttl=116 time=15.3 ms
64 bytes from 8.8.8.8: icmp_seq=403 ttl=116 time=21.0 ms
64 bytes from 8.8.8.8: icmp_seq=404 ttl=116 time=24.2 ms
64 bytes from 8.8.8.8: icmp_seq=405 ttl=116 time=19.4 ms
64 bytes from 8.8.8.8: icmp_seq=406 ttl=116 time=27.3 ms
64 bytes from 8.8.8.8: icmp_seq=407 ttl=116 time=18.4 ms
64 bytes from 8.8.8.8: icmp_seq=408 ttl=116 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=409 ttl=116 time=21.9 ms
64 bytes from 8.8.8.8: icmp_seq=410 ttl=116 time=16.0 ms
64 bytes from 8.8.8.8: icmp_seq=411 ttl=116 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=412 ttl=116 time=35.8 ms
64 bytes from 8.8.8.8: icmp_seq=413 ttl=116 time=20.4 ms
64 bytes from 8.8.8.8: icmp_seq=414 ttl=116 time=19.4 ms
64 bytes from 8.8.8.8: icmp_seq=415 ttl=116 time=18.3 ms
64 bytes from 8.8.8.8: icmp_seq=416 ttl=116 time=21.2 ms
64 bytes from 8.8.8.8: icmp_seq=417 ttl=116 time=24.7 ms
64 bytes from 8.8.8.8: icmp_seq=418 ttl=116 time=23.9 ms
64 bytes from 8.8.8.8: icmp_seq=419 ttl=116 time=31.0 ms
64 bytes from 8.8.8.8: icmp_seq=420 ttl=116 time=19.1 ms
64 bytes from 8.8.8.8: icmp_seq=421 ttl=116 time=17.2 ms
64 bytes from 8.8.8.8: icmp_seq=422 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=423 ttl=116 time=18.8 ms
64 bytes from 8.8.8.8: icmp_seq=424 ttl=116 time=26.8 ms
64 bytes from 8.8.8.8: icmp_seq=425 ttl=116 time=24.7 ms
64 bytes from 8.8.8.8: icmp_seq=426 ttl=116 time=25.7 ms
64 bytes from 8.8.8.8: icmp_seq=427 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=428 ttl=116 time=29.1 ms
64 bytes from 8.8.8.8: icmp_seq=429 ttl=116 time=21.0 ms
64 bytes from 8.8.8.8: icmp_seq=430 ttl=116 time=16.8 ms
64 bytes from 8.8.8.8: icmp_seq=431 ttl=116 time=25.8 ms
64 bytes from 8.8.8.8: icmp_seq=432 ttl=116 time=22.3 ms
64 bytes from 8.8.8.8: icmp_seq=433 ttl=116 time=20.8 ms
64 bytes from 8.8.8.8: icmp_seq=434 ttl=116 time=17.6 ms
64 bytes from 8.8.8.8: icmp_seq=435 ttl=116 time=17.5 ms
64 bytes from 8.8.8.8: icmp_seq=436 ttl=116 time=21.4 ms
64 bytes from 8.8.8.8: icmp_seq=437 ttl=116 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=438 ttl=116 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=439 ttl=116 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=440 ttl=116 time=19.1 ms
64 bytes from 8.8.8.8: icmp_seq=441 ttl=116 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=442 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=443 ttl=116 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=444 ttl=116 time=19.1 ms
64 bytes from 8.8.8.8: icmp_seq=445 ttl=116 time=25.3 ms
64 bytes from 8.8.8.8: icmp_seq=446 ttl=116 time=19.9 ms
64 bytes from 8.8.8.8: icmp_seq=447 ttl=116 time=16.2 ms
64 bytes from 8.8.8.8: icmp_seq=448 ttl=116 time=23.2 ms
64 bytes from 8.8.8.8: icmp_seq=449 ttl=116 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=450 ttl=116 time=23.0 ms
64 bytes from 8.8.8.8: icmp_seq=451 ttl=116 time=15.8 ms
64 bytes from 8.8.8.8: icmp_seq=452 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=453 ttl=116 time=21.3 ms
64 bytes from 8.8.8.8: icmp_seq=454 ttl=116 time=17.7 ms
64 bytes from 8.8.8.8: icmp_seq=455 ttl=116 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=456 ttl=116 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=457 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=458 ttl=116 time=24.6 ms
64 bytes from 8.8.8.8: icmp_seq=459 ttl=116 time=18.0 ms
64 bytes from 8.8.8.8: icmp_seq=460 ttl=116 time=16.2 ms
64 bytes from 8.8.8.8: icmp_seq=461 ttl=116 time=19.7 ms
64 bytes from 8.8.8.8: icmp_seq=462 ttl=116 time=24.1 ms

Re: Brutal latency/ping Recently

Hello and welcome to our Community @Teremlox!

 

I'd like to run some tests and do some troubleshooting with you to see if I can discern the source of this packet loss for you.

 

Please PM us @CommunityHelps. If you're not familiar with our PMing process, you can find instructions here.

 

Regards,

RogersCorey

Re: Brutal latency/ping Recently

Hey @borisnet!

 

Thank you for providing a detailed explanation of your home internet issue! I can imagine this is an incredibly difficult issue to have to deal with but no worries, you've most certainly come to the right place.

 

Given the nature and consistency of the latency you're experiencing would you mind confirming for us if you log into the gateway's GUI can you tell us if OFDMA is enabled?

 

Thanks!


@RogersAndy

Re: Brutal latency/ping Recently

Mine looks like is disabled

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

Re: Brutal latency/ping Recently

CM128
I've been around

Hi,

 

I've spent the last month on calling Rogers trying to resolve my ongoing latency issues (they started around the end of November, beginning of December).  So far I've made it through a number of phone calls and 2 service appointments to be told that everything looks fine with the modem, lines, etc. or that it's a broader issue affecting the whole area but every time they put in a ticket to look at an area issue, I would get a text message saying they couldn't find anything wrong even though the latency issues have never gone away

 

It doesn't matter what time of day it is, I am consistently getting huge spikes in my pings (7-8 times in an hour, each set of spikes lasting for 2-3 minutes before it calms down for a few minutes and starts again).  This affects my ignite TV (shows won't load, freeze, stutter), streaming, online gaming.  At points my wifi on my phone disconnects because the spike is so bad it thinks there is no internet connection.

 

Pings/tracerts I've done:

 

Ping statistics for 8.8.8.8:

    Packets: Sent = 150, Received = 150, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 2295ms, Average = 111ms

 

8 of the 150 pings were higher than 500ms time

 

Target Name: dns.google

         IP: 8.8.8.8

  Date/Time: 2021-01-07 10:12:43 AM - 2021-01-07 11:12:43 AM

 

Hop  Sent  Min        Max        Avg    Host Name / [IP]

  1  1452    0.18        5.83       0.83    10.0.0.1 [10.0.0.1]

  2  1452    6.26    2649.17    67.33   

  3  1452    4.59    2597.87    65.43   67.231.220.69 [67.231.220.69]

  4  1452    8.81    2549.96    68.32   69.63.248.189 [69.63.248.189]

  5  1452    8.02    2574.83    69.37   209.148.235.22 [209.148.235.22]

  6  1452    8.58    2684.49    71.84   72.14.209.126 [72.14.209.126]

  7  1452    7.48    2674.78    73.05   172.253.72.7 [172.253.72.7]

  8  1452    7.76    2678.46    75.65   108.170.226.219 [108.170.226.219]

  9  1452  10.43    2633.87    67.83   dns.google [8.8.8.8]

 

It doesn't matter what website or server I ping, I get similar results for all of them.

 

I tried running speedtests using the rogers speedtest page during one of the spikes and running back to back tests got:

1st test: 16ms ping, 370ms jitter, 5.1Mbps down, 19.8Mbps up

2nd test: 14ms ping, 19ms jitter, 822.5Mbps down, 20.6Mbps up

 

Hoping I might have better luck here with getting this resolved as it has made my internet nearly unusable for a month now.

 

Thanks.

Re: Brutal latency/ping Recently

raymond111
I plan to stick around

My pingplotter results from tonight to rogers ipv4 address and google.  Can someone help me interpret this data?  Rogers says there is nothing wrong with my connection and only that my area is due for an upgrade due to congestion but is unable to give me a timeline.  I need to know if there is anything I can do to help my latency/packet loss or am I stuck waiting for Rogers to fix there network?

 

Capture.JPGCapture1.JPGCapture3.JPG

Re: Brutal latency/ping Recently

Hey @CM128 and @raymond111!

 

Welcome to the community CM128!

 

Latency can be an incredibly difficult thing to deal with as a customer for sure, and just as difficult to troubleshoot. I would definitely recommend following the steps available in our Knowledge Base here.

 

If you're able to see latency within the Rogers network that exceeds 100ms, definitely share that traceroute information here and @CommunityHelps via pm so we can have it escalated for you. You can read more about our PM system here.


@RogersAndy

Re: Brutal latency/ping Recently

borisnet
I plan to stick around

Thank you @RogersAndy for the reply.

 

Channel 0 has OFDMA as operate and Channel 1 has OFDMA disabled see attached:

20210109-OFDMA settings.png

 

Let me know if this is expected as I see other post having both channels disabled. The values on the channel 0 row do not look to change over time.

 

Looking forward to what to check next.

Re: Brutal latency/ping Recently

What is OFDMA what’s it supposed to do ? Mine is still disabled

Re: Brutal latency/ping Recently


@lethalsniper wrote:
What is OFDMA what’s it supposed to do ? Mine is still disabled

It all has to do with how the modem encodes and sends data on the upstream channels.

 

Up until now, the DOCSIS 3.1-capable modems are only using D3.1 on the Downstream channels; they still use D3.0 on the Upstream channels.  Having OFDMA enabled means that your modem is using DOCSIS 3.1 on the Upstream channels as well... and from the sounds of it, Rogers may be running into problems having D3.0 and D3.1 modems coexisting on the same cable plant in this configuration.

 

One advantage to implementing D3.1 Upstream is the potential for higher speeds.  (The fastest speed that you can get with D3.0, with 4 bonded 6.4 MHz 64-QAM channels, is 108 Mb/s.)  However, there are other advantages that you can achieve depending on how you implement D3.1 and how you allocate spectrum for D3.0 and D3.1 channels.  I don't have OFDMA enabled on my modem so I can't really comment on Rogers' implementation.  (There are some D3.1 upstream configurations that can be problematic, depending on which CPE gear is in the mix... for example, if you have TaFDM enabled and have OFDMA and SC-QAM operating on the same frequencies / different times.  If Rogers is asking whether you have OFDMA enabled on you modem, presumably they are in the midst of trying to resolve some issues with their implementation in the real world.  This is pure speculation on my part.)

Re: Brutal latency/ping Recently

bluerose
I've been here awhile
Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1591000000QAM2563.599738.983
2597000000QAM2562.500838.983
3603000000QAM2561.599938.983
4855000000QAM2562.299340.946
5861000000QAM2562.200440.366
6579000000QAM2564.699539.854
7585000000QAM2563.900640.366
8849000000QAM2562.500240.946
9609000000QAM2561.2991038.983
10615000000QAM2561.5991138.605
11621000000QAM2562.0991240.366
12633000000QAM2562.7991338.983
13639000000QAM2562.5991438.983
14645000000QAM2562.2991538.983
15651000000QAM2562.0991640.946
16657000000QAM2561.5991738.983
17663000000QAM2561.5001838.605
18669000000QAM2562.2001940.366
19675000000QAM2562.2992038.983
20681000000QAM2563.2002138.983
21687000000QAM2563.5992240.366
22693000000QAM2563.7002340.946
23699000000QAM2563.7992440.946
24705000000QAM2563.5992540.946
25711000000QAM2563.2002640.366
26717000000QAM2562.9002740.366
27723000000QAM2563.2002840.366
28825000000QAM2561.9002938.983
29831000000QAM2561.4003038.605
30837000000QAM2562.2003140.366
31843000000QAM2562.2993240.366
32279000000QAM2567.199140.366
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
04K275600000YESYESYES3.900002
1NANANONONONA
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
13230000064QAM31.77076400000
23870000064QAM33.02086400000
32110000064QAM31.26053200000
42590000064QAM31.77066400000
50QAM_NONE----1600000
60QAM_NONE----1600000
70QAM_NONE----1600000
80QAM_NONE----1600000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0OPERATE0.212210.55439.600038.031530.25002K
1DISABLED0.00000.00000.00000.00000.00002K

Re: Brutal latency/ping Recently

bluerose
I've been here awhile

i get high latency and getting disconnected from warzone servers, also modem reboots everyday. I use an asus rt ax86u router and modem in bridge mode, had to unbridge the modem to get these modem stats

 

PING
12
ms
JITTER
2
ms
DOWNLOAD
515.4
Mbps
 
 
UPLOAD
32.6
Mbps
this is with laptop plug directly to modem, i get the same speeds with the asus router 

Re: Brutal latency/ping Recently

borisnet
I plan to stick around

Thanks @-G- for the theory - it is interesting and while not confirmed it could make sense as it seems difficult to address.

 

The consistency of the problem I could observe is that:

- it happens everyday although it can be hard to catch if you are doing something else than being online (arguably easier to notice with the pandemic and all the activities online impacted by connectivity outages in a household)

- it clears itself after a few minutes. That is the part that is surprising to me. In your theory, is there anything that could explain the fact that the problem does not last as long as a normal congestion issue

- there will be roughly 4 to 5 short outages (less than 3 min) and then it comes back to normal connectivity

 

@RogersAndy 

If this is something Rogers is working on, I am happy to monitor the CMTS portion of the modem in more details if that can help diagnose, troubleshoot and fix the issue.

I am or was on the beta track for modem firmware. Again, if there is something to be tried, I would be happy to contribute from my end.

Re: Brutal latency/ping Recently

-G-
Resident Expert
Resident Expert

@borisnet wrote:

Thanks @-G- for the theory - it is interesting and while not confirmed it could make sense as it seems difficult to address.

 

The consistency of the problem I could observe is that:

- it happens everyday although it can be hard to catch if you are doing something else than being online (arguably easier to notice with the pandemic and all the activities online impacted by connectivity outages in a household)

- it clears itself after a few minutes. That is the part that is surprising to me. In your theory, is there anything that could explain the fact that the problem does not last as long as a normal congestion issue

- there will be roughly 4 to 5 short outages (less than 3 min) and then it comes back to normal connectivity


If Rogers is in the process of making DOCSIS-related changes in parts of their network, there are any of a number of things that could be causing the problems that have been reported here.  Something as "simple" as intermittently losing a Primary channel in a Downstream Bonding Group would cause a modem to reboot.  D3.1 Upstream-related changes could also result in interoperability issues and other unforeseen side-effects that might not have been seen during lab testing.  It could be anything, but at least the problem appears to be localized... and I want to stress again that I am in no position to speculate as to what the problem(s) could be because I am not affected and I have no information that I could even use to hazard a guess.  I'm sure that Rogers would have identified the root cause by now and just need some time to get the underlying issues resolved.

Re: Brutal latency/ping Recently

borisnet
I plan to stick around

Happened again today at:

-11:52am - interrupted calls for everybody in the house - same behaviour as before.

- 8:06pm and 8:08pm - same symptom as before

 

It would be great if @RogersAndy can confirm whether Rogers as an organization is aware of the problem and what else we can do as customers experiencing outages every day. It was not that bad before this thread started and I would have hoped for quicker resolution if not at least transparent communication around the effort associated with the resolution.

 

Re: Brutal latency/ping Recently

zunee
I'm here a lot

For almost 4 months now, I've had random latency issues with rogers network (best I can tell),  yet of course my modem signal is fine according to Rogers...   I'm just about at my wits end after replacing some internal network gear, and still having the same problems.   To troubleshoot this I've been monitoring latency using SmokePing and i've had a ping running from the router hitting the WAN ip and then the first hop into Rogers network.  When the issue ocurrs,  the ping to 174.114.80.1 (the first hop for me in Rogers network), spikes to 20-40 seconds for ~20-40 seconds (rendering any zoom meeting basically useless).    I also ping the WAN ip and it's latency is fine, is there anything else I can do to prove to Rogers this is their problem?  From where I sit this has to be from the modem forward.


Note I use the Rogers modem (hitron coda, which is brand new) bridged into a Ubiquity EdgeRouter 4 (which is a very very decent router).   All my tracing is done hard wired into the switch (which has also been replaced), no IP internally exhibits any packet loss whatsoever.

Thanks

Re: Brutal latency/ping Recently

borisnet
I plan to stick around

@zuneeExactly the same symptom as you described and same monitoring in place. Started late November. It would be great if Rogers could leverage their community of advanced users and allow us to engage with people working on fixing the issue. 

Without showing intent from their end, it seems like they either do not know what is going on or do not want to work with their customers.