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

@nolanders have a look at my previous post regarding WinMTR and the white CODA-4582 modem.  Can you confirm that you're running the 4582.  

 

https://communityforums.rogers.com/t5/Internet/Brutal-latency-ping-Recently/m-p/456319#M59026

 

Looking at your trace, it appears to be getting lost within Blizzards own network.  AS57976  is Blizzards network:

 

https://bgp.he.net/AS57976

 

If my interpretation is correct, looks like the path is Rogers -> Equinix (Toronto ??) -> Blizzard

 

It might be possible that Equinix moves data around their network without that path showing up in the trace.  Not sure of that one so don't quote me on it. 

 

 



Re: Brutal latency/ping Recently

nolanders
I Plan to Stick Around

I do have a white coda-4582.

 

And Blizzard addressed this same problem as the ISP's problem. What can i possibly do?

Re: Brutal latency/ping Recently

Can you run a trace using the Battle.net Looking Glass and post the results:  https://us-looking-glass.battle.net/

 

Here's the results to West Ottawa as an example, run for this post.   Note that the trace dies within Rogers network:

 

TRACEROUTE:


traceroute to 174.112.1xx.xxx (174.112.1xx.xxx), 15 hops max, 60 byte packets


1 Blizzard Blizzard 9.412 ms 9.398 ms 9.393 ms
2 24.105.18.131 (24.105.18.131) 13.322 ms 13.333 ms 13.334 ms
3 137.221.105.12 (137.221.105.12) 9.385 ms 9.385 ms 9.385 ms
4 137.221.66.16 (137.221.66.16) 9.354 ms 9.355 ms 9.353 ms
5 137.221.83.80 (137.221.83.80) 40.564 ms 40.581 ms 40.600 ms
6 137.221.65.133 (137.221.65.133) 40.401 ms 38.744 ms 38.897 ms
7 137.221.69.32 (137.221.69.32) 38.397 ms 38.893 ms 38.891 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 40.232 ms 40.242 ms 40.255 ms
9 209.148.237.18 (209.148.237.18) 48.246 ms 48.519 ms 48.506 ms
10 209.148.229.230 (209.148.229.230) 57.238 ms 60.678 ms 60.002 ms
11 209.148.236.170 (209.148.236.170) 54.572 ms 54.493 ms 54.209 ms
12 67.231.221.78 (67.231.221.78) 55.382 ms 54.849 ms 54.844 ms
13 * * *
14 * * *
15 * * *


24/02/2020 22:36:08 UTC
--------------------

MTR:
Start: Mon Feb 24 22:36:08 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.12 0.0% 10 1.1 0.9 0.8 1.1 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 3.2 0.4 26.7 8.2
5.|-- 137.221.83.80 0.0% 10 38.2 44.0 37.9 85.0 14.9
6.|-- 137.221.65.133 0.0% 10 38.0 50.8 37.9 125.4 28.1
7.|-- 137.221.69.32 0.0% 10 38.6 40.8 38.1 56.0 5.8
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 37.8 37.9 37.6 39.8 0.5
9.|-- 209.148.237.18 0.0% 10 48.1 48.2 48.0 48.7 0.0
10.|-- 209.148.229.230 0.0% 10 56.2 57.1 53.7 60.4 2.1
11.|-- 209.148.236.170 0.0% 10 54.3 54.4 54.1 54.6 0.0
12.|-- 67.231.221.78 20.0% 10 55.1 55.0 54.5 55.4 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 22:36:08 UTC
--------------------

 



Re: Brutal latency/ping Recently

nolanders
I Plan to Stick Around

TRACEROUTE:
traceroute to 99.237.xxx.xx (99.237.xxx.xx), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.403 ms 0.404 ms 0.406 ms
2 24.105.18.131 (24.105.18.131) 0.574 ms 0.669 ms 0.757 ms
3 137.221.105.12 (137.221.105.12) 0.942 ms 1.031 ms 1.050 ms
4 137.221.66.16 (137.221.66.16) 0.866 ms 0.887 ms 0.889 ms
5 137.221.83.80 (137.221.83.80) 41.028 ms 41.044 ms 41.354 ms
6 137.221.65.133 (137.221.65.133) 37.875 ms 37.971 ms 37.961 ms
7 137.221.69.32 (137.221.69.32) 38.073 ms 38.319 ms 38.476 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 37.743 ms 37.828 ms 37.824 ms
9 15-cgw01.ym.rmgt.net.rogers.com (209.148.230.137) 48.908 ms 48.576 ms 48.557 ms
10 69.63.249.166 (69.63.249.166) 48.424 ms 48.573 ms 48.439 ms
11 67.231.221.2 (67.231.221.2) 48.939 ms 48.906 ms 48.746 ms
12 * * *
13 * * *
14 * * *
15 * * *


24/02/2020 22:45:32 UTC
--------------------

TRACEROUTE:
traceroute to 99.237.210.73 (99.237.210.73), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.440 ms 0.438 ms 0.442 ms
2 24.105.18.131 (24.105.18.131) 1.811 ms 1.826 ms 1.828 ms
3 137.221.105.12 (137.221.105.12) 3.792 ms 3.795 ms 3.797 ms
4 137.221.66.16 (137.221.66.16) 3.736 ms 3.730 ms 3.731 ms
5 137.221.83.80 (137.221.83.80) 38.061 ms 38.083 ms 38.087 ms
6 137.221.65.133 (137.221.65.133) 39.627 ms 63.208 ms 63.207 ms
7 137.221.69.32 (137.221.69.32) 38.759 ms 38.264 ms 38.243 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 38.363 ms 38.721 ms 38.735 ms
9 15-cgw01.ym.rmgt.net.rogers.com (209.148.230.137) 48.111 ms 48.394 ms 48.390 ms
10 69.63.249.166 (69.63.249.166) 49.261 ms 48.459 ms 48.443 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


24/02/2020 22:45:33 UTC
--------------------

MTR:
Start: Mon Feb 24 22:45:33 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 1.6 0.7 0.5 1.6 0.0
3.|-- 137.221.105.12 0.0% 10 1.1 0.9 0.7 1.4 0.0
4.|-- 137.221.66.16 0.0% 10 0.5 5.3 0.4 46.4 14.5
5.|-- 137.221.83.80 0.0% 10 38.2 41.7 38.2 56.5 6.1
6.|-- 137.221.65.133 0.0% 10 38.2 40.7 37.9 56.4 5.9
7.|-- 137.221.69.32 0.0% 10 38.2 39.9 38.1 54.3 5.0
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 38.2 38.0 37.7 38.6 0.0
9.|-- 15-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.8 48.4 48.0 48.8 0.0
10.|-- 69.63.249.166 0.0% 10 48.7 48.7 48.5 48.9 0.0
11.|-- 67.231.221.2 50.0% 10 48.9 49.0 48.8 49.2 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 22:45:32 UTC
--------------------

MTR:
Start: Mon Feb 24 22:45:33 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 1.6 0.7 0.5 1.6 0.0
3.|-- 137.221.105.12 0.0% 10 1.0 0.8 0.7 1.0 0.0
4.|-- 137.221.66.16 0.0% 10 0.5 5.4 0.3 46.5 14.5
5.|-- 137.221.83.80 0.0% 10 38.1 41.3 37.9 56.4 6.0
6.|-- 137.221.65.133 0.0% 10 38.1 44.3 37.9 92.9 17.2
7.|-- 137.221.69.32 0.0% 10 38.1 39.6 38.1 51.6 4.2
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 38.3 38.0 37.7 38.7 0.0
9.|-- 15-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.5 48.3 48.1 48.7 0.0
10.|-- 69.63.249.166 0.0% 10 48.7 48.6 48.3 49.0 0.0
11.|-- 67.231.221.2 80.0% 10 48.7 48.8 48.7 48.8 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 22:45:32 UTC
--------------------

 

Re: Brutal latency/ping Recently

Ok, so, similar results, the trace dies within the Rogers network, or, in other words, there appears to be so much traffic within the Rogers network that the trace, most likely an ICMP trace simply times out enroute and dies within the Rogers network.  So, the question for @RogersAndy at this point is why is the trace from Blizzards Looking Glass dying with the Rogers network?



Re: Brutal latency/ping Recently

I decided to run tests through the looking glass as well, here is what I got (It's a little long and I'm unsure if this should've been trimmed or not):

TRACEROUTE:
traceroute to 99.226.24.255 (99.226.24.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.326 ms 0.344 ms 0.349 ms
2 24.105.18.131 (24.105.18.131) 0.513 ms 0.600 ms 0.681 ms
3 137.221.105.16 (137.221.105.16) 0.848 ms 0.889 ms 0.991 ms
4 137.221.66.22 (137.221.66.22) 1.142 ms 1.160 ms 1.165 ms
5 137.221.83.86 (137.221.83.86) 38.062 ms 38.080 ms 38.142 ms
6 137.221.65.133 (137.221.65.133) 38.308 ms 38.056 ms 38.207 ms
7 137.221.69.32 (137.221.69.32) 38.214 ms 38.512 ms 38.488 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 37.734 ms 37.569 ms 37.605 ms
9 43-cgw01.ym.rmgt.net.rogers.com (209.148.235.102) 47.932 ms 48.059 ms 48.050 ms
10 209.148.233.89 (209.148.233.89) 61.698 ms 61.839 ms 61.833 ms
11 64.71.240.6 (64.71.240.6) 63.054 ms 62.626 ms 65.176 ms
12 66.185.91.250 (66.185.91.250) 63.186 ms 62.653 ms 62.703 ms
13 * * *
14 * * *
15 * * *


24/02/2020 23:28:14 UTC
--------------------

TRACEROUTE:
traceroute to 99.226.24.255 (99.226.24.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.805 ms 0.809 ms 0.814 ms
2 24.105.18.131 (24.105.18.131) 1.751 ms 1.785 ms 1.816 ms
3 137.221.105.16 (137.221.105.16) 1.788 ms 1.796 ms 1.811 ms
4 137.221.66.22 (137.221.66.22) 27.995 ms 28.049 ms 28.046 ms
5 137.221.83.86 (137.221.83.86) 38.551 ms 38.581 ms 38.595 ms
6 137.221.65.133 (137.221.65.133) 38.517 ms 47.035 ms 47.282 ms
7 137.221.69.32 (137.221.69.32) 39.362 ms 38.617 ms 38.616 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 38.093 ms 38.140 ms 37.941 ms
9 43-cgw01.ym.rmgt.net.rogers.com (209.148.235.102) 48.663 ms 48.002 ms 48.011 ms
10 209.148.233.89 (209.148.233.89) 61.785 ms 61.765 ms 61.772 ms
11 64.71.240.6 (64.71.240.6) 65.687 ms 65.291 ms 64.270 ms
12 * * *
13 * * *
14 * * *
15 * * *


24/02/2020 23:28:14 UTC
--------------------

TRACEROUTE:
traceroute to 99.226.24.255 (99.226.24.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.600 ms 1.535 ms 1.669 ms
2 24.105.18.131 (24.105.18.131) 1.519 ms 1.653 ms 1.770 ms
3 137.221.105.16 (137.221.105.16) 1.675 ms 1.713 ms 1.724 ms
4 137.221.66.22 (137.221.66.22) 1.661 ms 1.672 ms 1.699 ms
5 137.221.83.86 (137.221.83.86) 38.756 ms 38.769 ms 38.800 ms
6 137.221.65.133 (137.221.65.133) 38.344 ms 38.432 ms 38.423 ms
7 137.221.69.32 (137.221.69.32) 77.897 ms 77.904 ms 76.963 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 38.061 ms 38.182 ms 38.420 ms
9 43-cgw01.ym.rmgt.net.rogers.com (209.148.235.102) 48.224 ms 48.280 ms 48.427 ms
10 209.148.233.89 (209.148.233.89) 61.854 ms 61.670 ms 61.916 ms
11 64.71.240.6 (64.71.240.6) 67.301 ms 66.604 ms 64.698 ms
12 * * *
13 * * *
14 * * *
15 * * *


24/02/2020 23:28:17 UTC
--------------------

PING:
PING 99.226.24.255 (99.226.24.255) 56(84) bytes of data.

--- 99.226.24.255 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2997ms

 

24/02/2020 23:28:14 UTC
--------------------

PING:
PING 99.226.24.255 (99.226.24.255) 56(84) bytes of data.

--- 99.226.24.255 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3008ms

 

24/02/2020 23:28:14 UTC
--------------------

TRACEROUTE:
traceroute to 99.226.24.255 (99.226.24.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.502 ms 3.502 ms 3.510 ms
2 24.105.18.131 (24.105.18.131) 5.125 ms 5.157 ms 5.166 ms
3 137.221.105.16 (137.221.105.16) 5.176 ms 5.183 ms 5.192 ms
4 137.221.66.22 (137.221.66.22) 5.116 ms 5.129 ms 5.131 ms
5 137.221.83.86 (137.221.83.86) 41.783 ms 41.823 ms 41.839 ms
6 137.221.65.133 (137.221.65.133) 41.418 ms 42.121 ms 42.073 ms
7 137.221.69.32 (137.221.69.32) 42.073 ms 41.273 ms 41.259 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 41.189 ms 41.196 ms 41.197 ms
9 43-cgw01.ym.rmgt.net.rogers.com (209.148.235.102) 48.192 ms 48.471 ms 48.419 ms
10 209.148.233.89 (209.148.233.89) 61.716 ms 61.760 ms 61.795 ms
11 64.71.240.6 (64.71.240.6) 66.161 ms 65.416 ms 66.403 ms
12 * * *
13 * * *
14 * * *
15 * * *


24/02/2020 23:28:20 UTC
--------------------

PING:
PING 99.226.24.255 (99.226.24.255) 56(84) bytes of data.

--- 99.226.24.255 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

 

24/02/2020 23:28:19 UTC
--------------------

PING:
PING 99.226.24.255 (99.226.24.255) 56(84) bytes of data.

--- 99.226.24.255 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3009ms

 

24/02/2020 23:28:22 UTC
--------------------

TRACEROUTE:
traceroute to 99.226.24.255 (99.226.24.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.078 ms 1.088 ms 1.092 ms
2 24.105.18.131 (24.105.18.131) 6.798 ms 6.804 ms 6.810 ms
3 137.221.105.16 (137.221.105.16) 6.738 ms 6.754 ms 6.759 ms
4 137.221.66.22 (137.221.66.22) 6.566 ms 6.615 ms 6.641 ms
5 137.221.83.86 (137.221.83.86) 39.035 ms 39.056 ms 39.069 ms
6 137.221.65.133 (137.221.65.133) 38.658 ms 38.263 ms 38.261 ms
7 137.221.69.32 (137.221.69.32) 38.523 ms 38.552 ms 38.557 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 39.481 ms 39.501 ms 39.487 ms
9 43-cgw01.ym.rmgt.net.rogers.com (209.148.235.102) 48.741 ms 48.338 ms 48.328 ms
10 209.148.233.89 (209.148.233.89) 66.703 ms 61.715 ms 61.946 ms
11 64.71.240.6 (64.71.240.6) 63.908 ms 63.266 ms 64.154 ms
12 * * *
13 * * *
14 * * *
15 * * *


24/02/2020 23:28:27 UTC
--------------------

MTR:
Start: Mon Feb 24 23:28:14 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.8 0.0
2.|-- 24.105.18.131 0.0% 10 0.8 6.4 0.6 53.3 16.5
3.|-- 137.221.105.16 0.0% 10 0.9 1.0 0.8 1.3 0.0
4.|-- 137.221.66.22 0.0% 10 4.1 1.0 0.4 4.1 1.1
5.|-- 137.221.83.86 0.0% 10 38.1 49.8 38.0 103.4 24.7
6.|-- 137.221.65.133 0.0% 10 38.0 54.8 37.9 167.4 41.3
7.|-- 137.221.69.32 0.0% 10 38.2 42.7 38.1 83.4 14.3
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 37.7 38.3 37.7 42.5 1.3
9.|-- 43-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.1 48.9 48.0 55.0 2.1
10.|-- 209.148.233.89 0.0% 10 61.8 61.9 61.7 62.1 0.0
11.|-- 64.71.240.6 0.0% 10 66.8 64.4 62.6 66.8 1.3
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 23:28:14 UTC
--------------------

MTR:
Start: Mon Feb 24 23:28:14 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.5 0.2 1.1 0.0
2.|-- 24.105.18.131 0.0% 10 0.8 1.1 0.5 4.3 1.1
3.|-- 137.221.105.16 0.0% 10 1.2 1.4 0.8 4.1 0.9
4.|-- 137.221.66.22 0.0% 10 0.9 0.9 0.4 2.6 0.5
5.|-- 137.221.83.86 0.0% 10 38.0 43.3 38.0 63.6 10.4
6.|-- 137.221.65.133 0.0% 10 38.3 50.5 38.1 126.9 28.9
7.|-- 137.221.69.32 0.0% 10 38.5 43.8 38.0 79.9 13.2
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 39.1 41.9 37.7 45.7 2.7
9.|-- 43-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.0 48.1 48.0 48.4 0.0
10.|-- 209.148.233.89 0.0% 10 61.7 61.8 61.5 62.4 0.0
11.|-- 64.71.240.6 0.0% 10 63.1 64.1 62.4 66.4 1.1
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 23:28:14 UTC
--------------------

MTR:
Start: Mon Feb 24 23:28:17 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 5.9 0.5 51.2 15.9
3.|-- 137.221.105.16 0.0% 10 0.8 0.9 0.7 1.4 0.0
4.|-- 137.221.66.22 0.0% 10 0.4 0.6 0.4 0.8 0.0
5.|-- 137.221.83.86 0.0% 10 38.0 40.6 38.0 61.8 7.4
6.|-- 137.221.65.133 0.0% 10 39.0 44.6 37.9 92.5 16.9
7.|-- 137.221.69.32 0.0% 10 38.1 53.4 38.1 115.0 27.7
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 37.8 37.8 37.6 38.1 0.0
9.|-- 43-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.1 48.3 48.1 49.5 0.3
10.|-- 209.148.233.89 0.0% 10 62.0 62.1 61.6 63.4 0.3
11.|-- 64.71.240.6 0.0% 10 64.0 64.5 62.9 66.8 1.1
12.|-- 66.185.91.250 90.0% 10 62.7 62.7 62.7 62.7 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 23:28:17 UTC
--------------------

TRACEROUTE:
traceroute to 99.226.24.255 (99.226.24.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.425 ms 0.394 ms 0.531 ms
2 24.105.18.131 (24.105.18.131) 1.253 ms 1.274 ms 1.276 ms
3 137.221.105.16 (137.221.105.16) 1.278 ms 1.281 ms 1.284 ms
4 137.221.66.22 (137.221.66.22) 0.589 ms 0.618 ms 0.623 ms
5 137.221.83.86 (137.221.83.86) 38.207 ms 38.234 ms 38.392 ms
6 137.221.65.133 (137.221.65.133) 38.786 ms 38.236 ms 38.228 ms
7 137.221.69.32 (137.221.69.32) 38.184 ms 38.198 ms 38.779 ms
8 igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105) 37.982 ms 38.253 ms 38.238 ms
9 43-cgw01.ym.rmgt.net.rogers.com (209.148.235.102) 48.035 ms 48.434 ms 48.626 ms
10 209.148.233.89 (209.148.233.89) 71.407 ms 62.069 ms 62.073 ms
11 64.71.240.6 (64.71.240.6) 65.251 ms 64.378 ms 64.366 ms
12 66.185.91.250 (66.185.91.250) 63.534 ms * *
13 * * *
14 * * *
15 * * *


24/02/2020 23:28:31 UTC
--------------------

MTR:
Start: Mon Feb 24 23:28:20 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.6 0.4 0.3 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 5.8 0.6 51.3 16.0
3.|-- 137.221.105.16 0.0% 10 1.0 0.9 0.9 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 0.5 1.0 0.4 4.9 1.2
5.|-- 137.221.83.86 0.0% 10 39.7 38.2 37.9 39.7 0.5
6.|-- 137.221.65.133 0.0% 10 38.1 38.2 38.0 38.5 0.0
7.|-- 137.221.69.32 0.0% 10 38.1 41.9 38.1 72.5 10.7
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 38.3 38.4 37.7 41.4 0.9
9.|-- 43-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.2 48.2 48.0 48.7 0.0
10.|-- 209.148.233.89 0.0% 10 61.8 61.9 61.7 62.1 0.0
11.|-- 64.71.240.6 0.0% 10 63.0 64.9 63.0 66.1 0.9
12.|-- 66.185.91.250 80.0% 10 63.1 63.1 63.0 63.1 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 23:28:19 UTC
--------------------

PING:
PING 99.226.24.255 (99.226.24.255) 56(84) bytes of data.

--- 99.226.24.255 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3002ms

 

24/02/2020 23:28:31 UTC
--------------------

PING:
PING 99.226.24.255 (99.226.24.255) 56(84) bytes of data.

--- 99.226.24.255 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

 

24/02/2020 23:28:33 UTC
--------------------

MTR:
Start: Mon Feb 24 23:28:24 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 1.2 0.3 8.6 2.5
2.|-- 24.105.18.131 0.0% 10 0.9 5.6 0.5 47.2 14.6
3.|-- 137.221.105.16 0.0% 10 0.9 2.0 0.8 9.3 2.6
4.|-- 137.221.66.22 0.0% 10 0.6 4.4 0.4 37.0 11.5
5.|-- 137.221.83.86 0.0% 10 38.3 40.9 37.9 60.4 7.0
6.|-- 137.221.65.133 0.0% 10 38.0 47.1 37.9 72.4 14.8
7.|-- 137.221.69.32 0.0% 10 38.4 38.5 38.2 39.8 0.3
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 40.9 40.0 37.7 48.3 3.4
9.|-- 43-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.1 48.2 48.0 48.4 0.0
10.|-- 209.148.233.89 0.0% 10 62.0 61.8 61.5 62.0 0.0
11.|-- 64.71.240.6 0.0% 10 66.1 64.9 62.8 69.3 1.8
12.|-- 66.185.91.250 70.0% 10 63.2 63.0 62.8 63.2 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 23:28:24 UTC
--------------------

MTR:
Start: Mon Feb 24 23:28:32 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 1.3 0.5 3.9 1.0
3.|-- 137.221.105.16 0.0% 10 0.8 0.9 0.8 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 0.4 0.5 0.4 0.7 0.0
5.|-- 137.221.83.86 0.0% 10 38.1 38.2 37.9 39.3 0.3
6.|-- 137.221.65.133 0.0% 10 37.9 47.1 37.8 94.3 19.7
7.|-- 137.221.69.32 0.0% 10 38.2 43.4 38.0 88.7 15.9
8.|-- igw01.chcrmk.phub.net.cable.rogers.com 0.0% 10 37.8 37.8 37.6 38.0 0.0
9.|-- 43-cgw01.ym.rmgt.net.rogers.com 0.0% 10 48.0 48.1 47.9 48.5 0.0
10.|-- 209.148.233.89 0.0% 10 61.7 61.8 61.5 62.6 0.0
11.|-- 64.71.240.6 0.0% 10 65.8 64.4 62.8 66.8 1.4
12.|-- 66.185.91.250 40.0% 10 62.4 62.5 62.2 62.8 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


24/02/2020 23:28:31 UTC
--------------------

 

Re: Brutal latency/ping Recently

BoldAdanac
I Plan to Stick Around

Its actually hilarious the mod edited out (The mods are spending their time editing posts instead of looking into the issue.) This entire situation is a massive joke and I have no more patience.  I was tier 3 at a competitor and man let me tell you the way rogers is handling this is actually disgusting. I had the maintenance team come to my house today for the second time, this time the actual rogers maintenance tech left me with his phone number and is going to be running so diags over the next few days in the area. He believes my issue is related to the fact I am the 10th node in and the systems are designed to only go 5 deep - This certainly is a issue, and again proves rogers will just keep adding nodes connected with coax carriers just to get the CX count up not thinking or caring about how it will effect existing infrastructure. My issue started on FEB 14th, before that I have had solid internet connection for months, so unless rogers installed 7 nodes in one day (which didn't happen) the issue is deeper. I am dropping out through every hop except for the local system...... This issue is clearly much deeper than my neighborhood node as when the maitence tech ran a ping to the first node on the pole the latency was very good.  The tech today said I was the only one of two people from my area who have complained so the ticket was low on the totem pole and it was only the fact that I have now called more than 10 times in a two week period. I am so sick and tired of this battle now and everyday it becomes more apparent that this is not something that will be identified in a timely manner or at all, and then I log in to messages from moderators telling me to keep in on topic LOL. I have one topic and that is GET MY INTERNET WORKING.  The results below speak for themselves. [   Modem Connection Results <- Signal Strength  ]Hops.jpgPing.jpg

Re: Brutal latency/ping Recently

FlailingPyro
I've Been Here Awhile
 

Re: Brutal latency/ping Recently

GR4230543
I Plan to Stick Around

@DatalinkI have also run this test, as you suggest, using both the battle.net authentication, and a game (can't remember which). Results (including 100% packet loss): 

 

TRACEROUTE:
traceroute to 99.225.228.91 (99.225.228.91), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  3.030 ms  3.018 ms  3.021 ms
 2  24.105.18.131 (24.105.18.131)  2.966 ms  2.994 ms  2.999 ms
 3  137.221.105.16 (137.221.105.16)  3.003 ms  3.007 ms  3.010 ms
 4  137.221.66.18 (137.221.66.18)  2.997 ms  3.000 ms  3.004 ms
 5  137.221.83.82 (137.221.83.82)  90.494 ms  90.502 ms  90.509 ms
 6  137.221.65.133 (137.221.65.133)  154.543 ms  151.433 ms  147.779 ms
 7  137.221.69.32 (137.221.69.32)  38.141 ms  38.510 ms  38.530 ms
 8  igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105)  38.789 ms  38.176 ms  38.162 ms
 9  209.148.237.14 (209.148.237.14)  48.478 ms  48.314 ms  48.399 ms
10  209.148.233.89 (209.148.233.89)  61.955 ms  61.606 ms  62.099 ms
11  64.71.240.6 (64.71.240.6)  63.281 ms  62.420 ms  62.422 ms
12  66.185.91.250 (66.185.91.250)  62.841 ms  62.463 ms  62.992 ms
13  * * *
14  * * *
15  * * *


25/02/2020 00:03:16 UTC
--------------------

PING:
PING 99.225.228.91 (99.225.228.91) 56(84) bytes of data.

--- 99.225.228.91 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3006ms



25/02/2020 00:03:16 UTC
--------------------

MTR:
Start: Tue Feb 25 00:03:16 2020 Blizzard  1.|-- Blizzard                           0.0%    10    0.7   0.4   0.2   0.7   0.0
  2.|-- 24.105.18.131                           0.0%    10    0.6   1.1   0.5   5.1   1.3
  3.|-- 137.221.105.16                          0.0%    10    1.1   0.9   0.8   1.1   0.0
  4.|-- 137.221.66.18                           0.0%    10    0.4   1.1   0.4   3.8   0.9
  5.|-- 137.221.83.82                           0.0%    10   38.1  46.8  38.0  81.0  16.6
  6.|-- 137.221.65.133                          0.0%    10   38.0  46.8  38.0  79.8  14.9
  7.|-- 137.221.69.32                           0.0%    10   38.1  44.7  38.0  75.6  13.5
  8.|-- igw01.chcrmk.phub.net.cable.rogers.com  0.0%    10   37.8  38.3  37.7  41.5   1.0
  9.|-- 209.148.237.14                          0.0%    10   48.0  48.7  48.0  52.8   1.3
 10.|-- 209.148.233.89                          0.0%    10   61.9  61.9  61.6  62.2   0.0
 11.|-- 64.71.240.6                             0.0%    10   63.7  64.4  62.3  67.1   1.3
 12.|-- 66.185.91.250                          60.0%    10   63.0  62.9  62.4  63.2   0.0
 13.|-- ???                                    100.0    10    0.0   0.0   0.0   0.0   0.0


25/02/2020 00:03:16 UTC

 

Second test:

 

TRACEROUTE:
traceroute to 99.225.228.91 (99.225.228.91), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.996 ms  0.999 ms  0.987 ms
 2  24.105.18.3 (24.105.18.3)  1.896 ms  1.919 ms  1.926 ms
 3  137.221.105.12 (137.221.105.12)  1.967 ms  1.971 ms  1.975 ms
 4  137.221.66.16 (137.221.66.16)  1.917 ms  1.928 ms  1.933 ms
 5  137.221.83.80 (137.221.83.80)  38.796 ms  38.817 ms  38.822 ms
 6  137.221.65.133 (137.221.65.133)  38.639 ms  38.445 ms  38.511 ms
 7  137.221.69.32 (137.221.69.32)  38.396 ms  38.386 ms  38.598 ms
 8  igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105)  37.906 ms  37.924 ms  37.927 ms
 9  46-cgw01.ym.rmgt.net.rogers.com (209.148.235.94)  48.321 ms  48.207 ms  48.200 ms
10  209.148.233.89 (209.148.233.89)  61.686 ms  61.658 ms  61.803 ms
11  64.71.240.6 (64.71.240.6)  63.510 ms  62.991 ms  64.932 ms
12  66.185.91.250 (66.185.91.250)  63.178 ms  62.628 ms  62.626 ms
13  * * *
14  * * *
15  * * *


25/02/2020 00:01:47 UTC
--------------------

PING:
PING 99.225.228.91 (99.225.228.91) 56(84) bytes of data.

--- 99.225.228.91 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



25/02/2020 00:01:47 UTC
--------------------

MTR:
Start: Tue Feb 25 00:01:47 2020 Blizzard  1.|-- Blizzard                            0.0%    10    0.3   0.3   0.2   0.4   0.0
  2.|-- 24.105.18.3                             0.0%    10    0.6   1.2   0.5   6.4   1.7
  3.|-- 137.221.105.12                          0.0%    10    0.8   0.8   0.6   1.0   0.0
  4.|-- 137.221.66.16                           0.0%    10    0.7   3.3   0.4  28.1   8.7
  5.|-- 137.221.83.80                           0.0%    10   38.2  38.5  38.0  40.1   0.7
  6.|-- 137.221.65.133                          0.0%    10   38.1  38.0  37.9  38.1   0.0
  7.|-- 137.221.69.32                           0.0%    10   67.2  44.1  38.0  67.2  11.5
  8.|-- igw01.chcrmk.phub.net.cable.rogers.com  0.0%    10   37.7  37.7  37.6  37.8   0.0
  9.|-- 46-cgw01.ym.rmgt.net.rogers.com         0.0%    10   48.4  48.3  48.0  48.5   0.0
 10.|-- 209.148.233.89                          0.0%    10   61.7  61.8  61.2  62.2   0.0
 11.|-- 64.71.240.6                             0.0%    10   64.8  64.0  62.2  65.8   1.0
 12.|-- 66.185.91.250                          50.0%    10   62.7  62.7  62.3  62.9   0.0
 13.|-- ???                                    100.0    10    0.0   0.0   0.0   0.0   0.0


25/02/2020 00:01:47 UTC
--------------------

Re: Brutal latency/ping Recently

FlailingPyro
I've Been Here Awhile

I have been having this issue for a while now as well. I initially was told to trade in my Rocket modem for the new modem. I obliged and went and got it. The CODA i received didn't have working internet. It wouldn't connect to their servers. I contacted support again and was offered a tech to come over and replace it. Tech came over, replaced it. It works. Except of course for the very fun latency issue my initial modem had as well. So now I've been calling them every now and then with some calls up to 1hour long. They state they have no idea of this issue, never heard of it and that's it's "not an issue". I get told my internet is working fine. So I state my issues, they tell me my ping is fine. Which i know it is and tell them again, its the spikes. I get told it's a hardware issue with my devices, all 4 of them. I state that's impossible cause I run tests on all of them, and they all have identical issues. I then get told its a "gaming issue", cause of course over 5+ games all having the same issue is obviously the problem.  I explain the absurdity of that explanation. The tech then tries to sell me a rental Wi-fi booster for $5 a month. Do you expect me to pay you more money to fix a service that isn't working. The one that i'm ALREADY paying you for? I asked how a Wi-fi booster will fix the issues on my 2 wired connections. And the tech stated it would help the other devices. I declined. I then get told "Your internet speeds are fine, there is no issue". Cause of course I would call 3 times in 10 days for "no issue" and sit on hold for over 20+ mins every time cause I love wasting my time. I request a technician to come over and witness the problem so it can be fixed. "That will cost $50". So we ended the call with her setting up ANOTHER modem swap, which will fix nothing. This is 3 separate tech's, all saying roughly the same thing. It's revolting to deal with and not feel listened to.

So to summarize, my devices are the problem or its games that are the issue, not rogers. A wi-fi booster will help wired connection issues for $5. And you refuse to send a tech for free for an issue with YOUR service. I think my internet issue isn't the only issue I have. I have an issue with customer service. If this modem magically fixes the spikes, great. If it doesn't (likely) and I still have received 0 help from tech support or technicians. The clearest option is to cancel this garbage. I'm not paying monthly for a broken service that isn't being taken responsibility for.

Re: Brutal latency/ping Recently

nolanders
I Plan to Stick Around

Here is a more detailed response from tech support at Blizzard. 

 

https://imgur.com/a/on1rWwX

 

https://imgur.com/a/on1rWwX 

Re: Brutal latency/ping Recently

nolanders
I Plan to Stick Around

Now that blizzard confirmed that the issue is from rogers network, what's next to do? or what can be done to speed the process of rogers acknowledging this?

 

https://imgur.com/a/on1rWwX

Re: Brutal latency/ping Recently

Now that is the $50 million dollar question.  So far, there doesn't seem to be much of a reaction to all of the posts.  Not sure what its going to take, social shaming, cajoling, pleading, sacrifice to the nearest volcano?  Don't know.



Re: Brutal latency/ping Recently

t27c
I Plan to Stick Around
I think most of us just want Rogers to at the VERY least acknowledge that there is some sort of issue. The fact that since I have created this thread, there is now over 160 responses and many people who are experiencing the same issue. All ranging from the KWC and GTA areas. I think most of us find it hard to believe that all of these cases are “our problem”. Especially after conducting all the tests that are asked of us and the results showing that there is an issue somewhere in Rogers network. But alas, we are continued to be told it’s hardware issues, despite having tested on multiple devices, switching modems multiple times to nothing improving. Being told it’s a local networking issue despite tests showing there is no issues on our side of things. Being told it’s “the game” when it occurs in every game no matter the platform or game developer. I deeply appreciate the time these moderators have put in to address and help us out, and not to mention dealing with the backlash of things not being solved. But I think if Rogers was willing to admit there is an issue, people will be more patient and forgiving. It is much easier to forgive someone who is honest and up front about a mistake, than someone who blames someone else for their mistake. I think if Rogers would just go through this thread and read the countless complaints about the same latency and packet loss issue, maybe we could work together on a solution so that we get the service we pay quite a lot for, and that Rogers will not lose anymore money giving people discounts and credit, and even the countless people who are on the verge of canceling due to the poor service right now

Re: Brutal latency/ping Recently

GR4230543
I Plan to Stick Around

Hi @Datalink, are you able to confirm that my results are also "within rogers network" as an issue?

 

TRACEROUTE:
traceroute to 99.225.228.91 (99.225.228.91), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  3.030 ms  3.018 ms  3.021 ms
 2  24.105.18.131 (24.105.18.131)  2.966 ms  2.994 ms  2.999 ms
 3  137.221.105.16 (137.221.105.16)  3.003 ms  3.007 ms  3.010 ms
 4  137.221.66.18 (137.221.66.18)  2.997 ms  3.000 ms  3.004 ms
 5  137.221.83.82 (137.221.83.82)  90.494 ms  90.502 ms  90.509 ms
 6  137.221.65.133 (137.221.65.133)  154.543 ms  151.433 ms  147.779 ms
 7  137.221.69.32 (137.221.69.32)  38.141 ms  38.510 ms  38.530 ms
 8  igw01.chcrmk.phub.net.cable.rogers.com (208.115.136.105)  38.789 ms  38.176 ms  38.162 ms
 9  209.148.237.14 (209.148.237.14)  48.478 ms  48.314 ms  48.399 ms
10  209.148.233.89 (209.148.233.89)  61.955 ms  61.606 ms  62.099 ms
11  64.71.240.6 (64.71.240.6)  63.281 ms  62.420 ms  62.422 ms
12  66.185.91.250 (66.185.91.250)  62.841 ms  62.463 ms  62.992 ms
13  * * *
14  * * *
15  * * *


25/02/2020 00:03:16 UTC
--------------------

PING:
PING 99.225.228.91 (99.225.228.91) 56(84) bytes of data.

--- 99.225.228.91 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3006ms



25/02/2020 00:03:16 UTC
--------------------

MTR:
Start: Tue Feb 25 00:03:16 2020 Blizzard  1.|-- Blizzard                           0.0%    10    0.7   0.4   0.2   0.7   0.0
  2.|-- 24.105.18.131                           0.0%    10    0.6   1.1   0.5   5.1   1.3
  3.|-- 137.221.105.16                          0.0%    10    1.1   0.9   0.8   1.1   0.0
  4.|-- 137.221.66.18                           0.0%    10    0.4   1.1   0.4   3.8   0.9
  5.|-- 137.221.83.82                           0.0%    10   38.1  46.8  38.0  81.0  16.6
  6.|-- 137.221.65.133                          0.0%    10   38.0  46.8  38.0  79.8  14.9
  7.|-- 137.221.69.32                           0.0%    10   38.1  44.7  38.0  75.6  13.5
  8.|-- igw01.chcrmk.phub.net.cable.rogers.com  0.0%    10   37.8  38.3  37.7  41.5   1.0
  9.|-- 209.148.237.14                          0.0%    10   48.0  48.7  48.0  52.8   1.3
 10.|-- 209.148.233.89                          0.0%    10   61.9  61.9  61.6  62.2   0.0
 11.|-- 64.71.240.6                             0.0%    10   63.7  64.4  62.3  67.1   1.3
 12.|-- 66.185.91.250                          60.0%    10   63.0  62.9  62.4  63.2   0.0
 13.|-- ???                                    100.0    10    0.0   0.0   0.0   0.0   0.0

Re: Brutal latency/ping Recently

GR4230543
I Plan to Stick Around

Just an update here - I've been on hold with rogers chat for the past hour or so, where I get a "please wait while..." message variant, and then get disconnected after some number of minutes. my guess is they are understaffed at the moment.

 

In the meantime, I've been looking up competitor internet plans. I'm thinking of going back to virgin mobile internet, which was very consistent and good overall service (i only left because of the sticker speeds I was offered with Rogers, which are occasionally more or less accurate).

 

Does anyone else have good experience with some of Roger's competitors?

Re: Brutal latency/ping Recently

geokilla007
I Plan to Stick Around

@nolanders. Your imgur link doesn't seem to work.

Re: Brutal latency/ping Recently

nolanders
I Plan to Stick Around

In the imgur links i provided, the problem stems from rogers network specifically 67.231.221.5 and 99.237.140.1 which are the 333 bloor street east 9th floor rogers communications center and 1 Mount Pleasant Road, rogers communications center.

Re: Brutal latency/ping Recently

nolanders
I Plan to Stick Around

Re: Brutal latency/ping Recently

@GR4230543 with the exception of @nolanders Battle-net trace, every other trace appears to time out before getting to the users CMTS.  So, its stalling out within the Rogers network. 

 

On the other hand, if you run a trace in the opposite direction, the trace stalls out within Blizzards network.  

 

This leaves the user in a position of being unable to really determine what problems might exist in either network, which is an unsatisfactory state of affairs.  

 

 



Re: Brutal latency/ping Recently

pmakshou
I Plan to Stick Around

So Rogers tech support came today and it's supposedly something with the node outside.

We'll see what happens. This is pathetic. They said they're sending a "senior technician" and the guys just goes, "Yup everything looks good here. Must be outside" and I'm like "That's what I keep telling you guys but you guys don't listen."

 

So now it's supposedly going to take 3-5 days to fix the internet. That's on top of the 2 weeks it's been like this already. What the heck? I'm going to ask them to skip my bill this month. This is unacceptable.