@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:
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.
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
--------------------
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?
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 ]
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.
@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.
-
203729 views
-
156 Likes
-
-
