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
-G-
Resident Expert
Resident Expert
Posts: 1,742

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.

 

 

ryanto
I've Been Here Awhile
Posts: 3

Re: Brutal latency/ping Recently

Before 9am my latency/download/upload is all good.  Once 9am hits, latency is like a ping pong and upload is around 3mbps.  i'm assuming Rogers is capping the upload speeds which is unacceptable.  I'm paying for 20mbps upload service and not even getting close to it.   A second tech is coming out this afternoon.  I'm not optimistic there is a fix in sight because it's not a signal issue.  

super_robot
I Plan to Stick Around
Posts: 64

Re: Brutal latency/ping Recently

@ryanto 

 

The issue is on the network, nothing a tech visiting your house is going to fix. The issue is widespread.

 

 

I shut off my WIFI and ran these tests from my pc wired to the modem after a fresh reboot.

 

 

Pinging www.google.ca [172.217.164.227] with 32 bytes of data:
Reply from 172.217.164.227: bytes=32 time=22ms TTL=55
Reply from 172.217.164.227: bytes=32 time=50ms TTL=55
Reply from 172.217.164.227: bytes=32 time=105ms TTL=55
Reply from 172.217.164.227: bytes=32 time=104ms TTL=55
Reply from 172.217.164.227: bytes=32 time=38ms TTL=55
Reply from 172.217.164.227: bytes=32 time=45ms TTL=55
Reply from 172.217.164.227: bytes=32 time=92ms TTL=55
Reply from 172.217.164.227: bytes=32 time=83ms TTL=55
Reply from 172.217.164.227: bytes=32 time=96ms TTL=55
Reply from 172.217.164.227: bytes=32 time=96ms TTL=55
Reply from 172.217.164.227: bytes=32 time=89ms TTL=55
Reply from 172.217.164.227: bytes=32 time=66ms TTL=55
Reply from 172.217.164.227: bytes=32 time=42ms TTL=55
Reply from 172.217.164.227: bytes=32 time=132ms TTL=55
Reply from 172.217.164.227: bytes=32 time=78ms TTL=55
Reply from 172.217.164.227: bytes=32 time=77ms TTL=55
Reply from 172.217.164.227: bytes=32 time=208ms TTL=55
Reply from 172.217.164.227: bytes=32 time=93ms TTL=55
Reply from 172.217.164.227: bytes=32 time=85ms TTL=55
Reply from 172.217.164.227: bytes=32 time=45ms TTL=55
Reply from 172.217.164.227: bytes=32 time=65ms TTL=55

Ping statistics for 172.217.164.227:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 208ms, Average = 81ms

 

 

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

1 2 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 229 ms 52 ms 62 ms  ***.***.***.***
3 39 ms 93 ms 90 ms 8082-dgw01.etob.rmgt.net.rogers.com [67.231.220.33]
4 37 ms 41 ms 47 ms 0-14-0-7-cgw01.wlfdle.rmgt.net.rogers.com [209.148.232.137]
5 22 ms 54 ms 136 ms 209.148.230.6
6 88 ms 65 ms 116 ms 72.14.209.126
7 64 ms 54 ms 64 ms 209.85.249.37
8 135 ms 60 ms 48 ms 216.239.41.247
9 56 ms 24 ms 76 ms yyz12s05-in-f3.1e100.net [172.217.164.227]

 

 

Speedtest 300/1.5  (supposed to get 15mb up)

-G-
Resident Expert
Resident Expert
Posts: 1,742

Re: Brutal latency/ping Recently


@super_robot wrote:

The issue is on the network, nothing a tech visiting your house is going to fix. The issue is widespread.


I totally agree... and the problem is not caused by "noise" (at least not in my area) nor is this something that can be fixed with new firmware.  I also ran another ping test with the following results:

 

--- 8.8.8.8 ping statistics ---
3600 packets transmitted, 3600 received, 0% packet loss, time 3604050ms
rtt min/avg/max/mdev = 5.434/25.708/1615.135/70.939 ms, pipe 2

 

So, are things better?  Yes, for the most part.  It's not the worst that I have seen.

Fixed?  Definitely not.



super_robot
I Plan to Stick Around
Posts: 64

Re: Brutal latency/ping Recently

So.. decided to pick up the phone after wasting so much time with the chat support. I've had 4 cases open, techs deployed all the stuff.

 

 

The lady who picked up the phone bluntly said high latency and slow speeds are to be expected with the current situation.

 

While this answer isn't really what I was hoping for, I can appreciate the honesty. They should pass the information along to the front line support wasting everyone's time.

-G-
Resident Expert
Resident Expert
Posts: 1,742

Re: Brutal latency/ping Recently


@super_robot wrote:

The lady who picked up the speed bluntly said high latency and slow speeds are to be expected with the current situation.

 

While this answer isn't really what I was hoping for, I can appreciate the honesty. They should pass the information along to the front line support wasting everyone's time.


Thanks for the update, and kudos to Rogers for their simple, straight, honest response.

 

I know that we're all stressed out over everything at the moment but I remain hopeful that the present world situation will improve (and the sooner, the better) and that once our lives gets back to being more normal, that the Rogers network issues will get resolved and that things will even be better than ever as well as a result.



super_robot
I Plan to Stick Around
Posts: 64

Re: Brutal latency/ping Recently

Not sure we can say "kudos" Rogers. It's not like they released a statement or anything.

 

They are still doing useless troubleshooting with everyone and wasting their time. 

 

Thankful for that one agent but yeah, not impressed with Rogers as a whole.

xdCanuck
I Plan to Stick Around
Posts: 11

Re: Brutal latency/ping Recently

My issues cleared up for a whole week again, just as it had once before, and I'm back in the hole. I got a response from the CCTS and then from Rogers, who conveniently called during the week in which it had cleared up, to which I told them the issues were okay at the time but that I would contact them again if anything arose. I'm in touch with a resolution team member who can hopefully be more helpful than whomever my tickets were being raised to who closed them instantly as they "didn't find an issue". I'm effectively getting the same WinMTR/traceroute/ping test as I did the past few months when it occurs. Notice below a 96% packet loss from hitronhub.home (my local network), and 45/40 on Rogers DNS servers.

 

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| hitronhub.home - 96 | 244 | 12 | 0 | 0 | 1 | 1 |

| 99.250.138.1 - 0 | 1168 | 1168 | 9 | 49 | 434 | 14 |

| 8082-dgw02.ktgc.rmgt.net.rogers.com - 1 | 1165 | 1164 | 9 | 46 | 449 | 85 |

| 209.148.237.53 - 0 | 1168 | 1168 | 10 | 48 | 436 | 18 |

| 209.148.227.157 - 0 | 1168 | 1168 | 11 | 53 | 802 | 21 |

| 10.202.47.161 - 45 | 422 | 235 | 0 | 62 | 330 | 43 |

| dns.cp.net.rogers.com - 40 | 454 | 275 | 0 | 57 | 416 | 23 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

However, when I test a game I play I get this

 

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| hitronhub.home - 86 | 509 | 76 | 0 | 0 | 3 | 1 |

| 99.250.138.1 - 0 | 2238 | 2238 | 6 | 39 | 657 | 18 |

| 8082-dgw01.ktgc.rmgt.net.rogers.com - 0 | 2238 | 2238 | 5 | 34 | 448 | 10 |

| 209.148.236.185 - 0 | 2238 | 2238 | 7 | 39 | 449 | 22 |

| 209.148.235.145 - 0 | 2238 | 2238 | 9 | 38 | 265 | 19 |

| No response from host - 100 | 449 | 0 | 0 | 0 | 0 | 0 |

| 172.65.243.154 - 4 | 1973 | 1906 | 6 | 37 | 270 | 54 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

Notice no issues except on hitronhub.home. I do not know if this means that not only was my original modem given to me awful, but the replacement one I had brand new as well. I suppose it's not impossible. However, this just leads me to believe the failure is with Rogers DNS servers, as they're the only common pattern besides hitronhub.home.

 

 

 

herrshaun
I Plan to Stick Around
Posts: 71

Re: Brutal latency/ping Recently

Absolutely insane timeouts lately:

 

Ping statistics for 2607:f8b0:400b:801::2004:
Packets: Sent = 3600, Received = 3592, Lost = 8 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 160ms, Average = 13ms

 

I don't want to be insensitive, but maybe it's time the engineers went back to work?