Need Assistance With WinMTR results

Hello. I had made a thread a week ago and just got around to testing yesterday, but the update to my thread was ignored and i would like to get to the bottom of this issue. TL;DR i am getting latency spikes at this address and i would like to know what it represents and what i can do about it:

ae1-br01-eqch2.as57976.net

I ran it for both the central and western IPs. Over the last week the issue has come and gone. I played many hours and had several great matches with no issue. Today it is particularly prevalent. I played for several minutes for each after the issue occurred as recommended (it happened immediately), however it continued be persistent through the whole tests.

The addresses in question from the results are quite cryptic so i am unsure exactly what they represent. Hopefully someone won’t mind taking a look at these as it would be cool to get to the bottom of this. I have never had such an issue playing Overwatch, and i’ve played since beta. I’ll post the central first, follower by western. (I accidentally left the western test running in the background while typing this for a few minutes after playing but i don’t believe that will matter). Thank you in advance.

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

WinMTR statistics - 24.105.62.129 (US Central)

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



Cogeco.local -   0|1035|1035|0|9|19|6|

10.67.128.1 -   2|981|967|7|11|20|13|

10.0.67.113 -   2|981|967|8|13|23|14|

10.0.18.78 -   2|981|967|8|12|25|13|

|hu0-1-0-0.rcr21.yhm01.atlas.cogentco.com -  2 |981|967|8|13|25|9|

|   be2621.ccr31.yyz02.atlas.cogentco.com -  2|977|962|9|14|27|13|

|   be2993.ccr21.cle04.atlas.cogentco.com -   2|965|947|16|19|107|18|

|   be2717.ccr41.ord01.atlas.cogentco.com -   2|981|967|23|28|37|25|

|   be2765.ccr41.ord03.atlas.cogentco.com -   2|981|967|23|28|36|30|

|38.104.102.29 -    2|981|967|22|26|44|25|

|ae1-br01-eqch2.as57976.net -    2|981|967|22|32|217|29|  <<<<<<<<<<

|be1-pe01-eqch2.as57976.net -    2|981|967|22|27|40|24|

|chi-eqch2-ia-bons-02.as57976.net -    2|981|967|24|29|37|30|

|24.105.62.129 -    2|981|967|22|25|37|25|
|------------------------------------------|

|WinMTR statistics - 24.105.30.129 (US West)|

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

 Cogeco.local -    0|1050|1050|0|9|2010|

10.67.128.1 -    1|1010|1000|7|11|20|10|

10.0.67.113 -    1|1010|1000|8|13|22|13|

10.0.18.78 -    1|1010|1000|8|12|26|12|

|hu0-1-0-0.rcr21.yhm01.atlas.cogentco.com -  1|1010|1000|8|13|24|13|

|be2622.ccr32.yyz02.atlas.cogentco.com - 1|1010|1000|9|14|24|12|

|be2994.ccr22.cle04.atlas.cogentco.com -  1|1011|100|15|19|30|19|

|be2718.ccr42.ord01.atlas.cogentco.com - 1|1011|1001|23|26|43|28|

|be2766.ccr41.ord03.atlas.cogentco.com -  1|1011|1001|22|27|37|25|

| 38.104.102.29 -  1|1011|1001|21|25|56|24|

|  ae1-br01-eqch2.as57976.net -  1|1010|1000|64|75|273|71|  <<<<<<

|  137.221.65.132 -    1 |1010|1000|63|70|198|64|  <<<<<<<<

|  et-0-0-2-br01-eqla1.as57976.net -  2|986|971|64|84|3537|66|  <<<<<<<

| be1-pe01-eqla1.as57976.net -  1|1010|1000|63|68|76|69|

| 24.105.30.129 -  1|1010|1000|63|66|80|64|

Out of curiosity i did a couple more brief tests on Central IP and both times it was the following that was the problem. Now i am interested in what this is.

ae1-br01-eqch2.as57976.net

Also just browsing and i saw this post, so i may as well toss in my modem’s model number in case it is relevant. It’s an “Arris TG3452A/CG” .

Drakuloth
Customer Support
(source)
Extra post here just for curiosity’s sake. Are you still having problems with this? We’ve recently started getting reports of problems like this with specific modems/routers. Can you get your router and modem makes/models for me? They should be on a sticker on the devices, or stamped onto the plastic.

Howdy!

When reviewing a WinMTR, Tracert or pathping it’s important to always troubleshoot top down. Meaning we see the issue starting at hop 2:

10.67.128.1 - 2|981|967|7|11|20|13|

This is an internal ISP likely hosted by your Internet Service Provider that should look into this.

ae1-br01-eqch2.as57976.net is a peering node to us. Though it may show a large spike that is likely not the core issue in this case. Both tests show packet loss occurring starting at hop 2 which is likely the core issue here.

Thank you.