Latency Increase Alberta, CA

Technical Support
21

Here’s the test, came out exactly as I expected. I can’t run the tests on Telus because all but two of your routes come out as ‘no response from host’. This one is with Shaw in a competitive game:

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

|                                      WinMTR statistics                                   |

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

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

|                         router.asus.com -    0 |  747 |  747 |    0 |    0 |    2 |    0 |

|                             96.52.128.1 -    0 |  747 |  747 |    6 |   23 |   36 |    9 |

|                           64.59.186.165 -    0 |  747 |  747 |    4 |    9 |   30 |    9 |

|              rc3no-be6.cg.shawcable.net -    0 |  747 |  747 |   10 |   14 |   41 |   17 |

|            rc2wt-be100.wa.shawcable.net -    0 |  747 |  747 |   27 |   28 |   42 |   27 |

|           rc1wt-be18-1.wa.shawcable.net -    0 |  747 |  747 |   23 |   29 |   56 |   33 |

|      eqix-se2.blizzardentertainment.com -    0 |  747 |  747 |   27 |   29 |   57 |   29 |

|       ae1-br01-eqse2.blizzardonline.net -    0 |  747 |  747 |   27 |   29 |  104 |   28 |

|xe-0-0-1-1-br02-eqch2.blizzardonline.net -    0 |  747 |  747 |   53 |   67 |  461 |   68 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

I just had a talk with a member of the support team, they said it was an issue with trace and that I need to talk to my ISP. However, in my case, I’m being connected to the Los Angeles servers over the closer, lower ping, Chicago servers. My average ping to Los Angeles is 100-105ms while my average ping to Chicago is 70-80ms (this was my average ping before).

Hitting Ctrl + Shift + N in the Practice Range tells me I’m connected to 24.105.40.67 (the Overwatch server IP).

My ISP can’t fix Overwatch making me play on the Los Angeles servers, that looks like an Overwatch problem. That IP is in Irvine, California very close to Los Angeles.

Here are 3 speed tests (Timer Warner, and AT&T speedtest servers) for Los Angeles:

  • TW: 129, 101, 98 (ms)
  • AT&A: 106, 97, 99 (ms)

Here are 3 speed test (Comcast, and Sprint speedtest servers) for Chicago:

  • CC: 87, 85, 88 (ms)
  • Sp: 81, 79, 85 (ms)

It’s pretty clear I would rather play on Chicago servers and not Los Angeles servers, so why is Overwatch making me play on them?

I also don’t think it’s completely my ISP as only Overwatch is having these connection problems. My average ping in Overwatch earlier today was 104ms with spikes as high as 160ms. At the time of posting here I’m seeing 250ms and high spikes into 350ms while ping returns from Los Angeles are at their average 100ms~ range.

Can we please get an option (like most other multiplayer games) to set our server. I don’t see why that would be a bad thing.

1 Like
23

here is a longer WinMTR

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
hitronhub.home 0 245 245 2 27 506 15
68.150.128.1 0 245 245 9 26 508 15
rc3ar-be109-1.ed.shawcable.net 0 245 245 12 16 121 14
66.163.70.129 0 245 245 10 15 121 11
rc3no-be6.cg.shawcable.net 0 245 245 14 19 129 20
rc2wt-be100.wa.shawcable.net 0 245 245 29 34 130 36
rc1wt-be18-1.wa.shawcable.net 0 245 245 30 35 124 35
eqix-se2.blizzardentertainment.com 0 245 245 30 35 124 36
ae1-br01-eqse2.blizzardonline.net 0 245 245 30 35 124 33
xe-0-0-0-1-br01-eqsv5.blizzardonline.net 1 241 240 47 51 122 48
xe-0-0-1-1-br02-eqla1.blizzardonline.net 0 245 245 59 69 193 61
24

B72,

As you already know, reading through your various posts and tickets, your router/modem has a terrible connection. You’re averaging nearly 30 ms just inside your house. Everything outside of your house is being partially affected by the spikes in latency between your pc and router/modem. Their average latency alone is reasonable, but the poor connection within your house drives it far over the edge. I was looking to find other things in your WinMTR, but that’s the only glaring thing we’ve got. Your ping should be in the 50-65 range without this failure if this test displays typical results. Going to point this out so you can leverage it with your ISP.

Host % Sent Recv Best Avrg Wrst Last
hitronhub.home 0 245 245 2 27 506 15

I know you’ve already done troubleshooting on this device, but it clearly hasn’t actually worked. You need to replace the puma 6 modem you have with a different model which doesn’t have these issues. Until this is done, there’s nothing else we can do here.

==================================

As for some of your other points - you’re right, the training server sometimes puts you on a less busy server but it’s not going to happen all the time. This is just the safest way to test without affecting your account. You could also theoretically use a custom game completely full of bots to the same ends.

The ‘routing issue’ you’re referring to doesn’t actually exist however. There was an incorrect assumption made in one of your tickets (Sorry about that) but you’re taking the most direct route to the server. Previously the agent misread the hops you were going through and thought you were going to the east coast, then back to the west. I can assure you that’s not what’s happening. You can look up the places you’re going through on peer DB and you’ll see you take a logical route through our peers for the optimal ping. (Seattle->San Jose->Los Angeles). We can re evalutate if there’s a real spike, somewhere around there, but before we can do that we must eliminate what’s going on with that router/modem you’ve got there.

Re: the france thing, no prob, just wanted to bring it up.

The rest of that post should be covered above by what we found in your WinMTR. Let me know if you’ve got any other questions, but I honestly think all you need to do is get a better device from your ISP or purchase one of your own.

25

Veiledflame,

For your situation, you weren’t having a router issue looks like, so we get a more clear picture of what’s going on here. You were on the Chicago server at the time of this test, looks like. You should have been averaging about 70 MS there. Were you seeing higher than 70 MS latency frequently?

Interestingly, you were routed to Seattle, then Chicago. There may be a more direct route through your ISP which routes players through other canadian provinces before hitting our peers, but it’s also possible this is the quickest route. I can’t know that on my end because I don’t know the resources/business deals your ISP has with other canadian ISPs. Keep in mind that just because something changed doesn’t mean it changed on our end. Deals are made and broken between ISPs regularly. It’s possible your local ISP isn’t working with the same peers as they were before your issue arose. We’ve been using equinix for a while now, however. As of this writing I’m not aware of anything that changed on our end that would cause this.

What I can say is that you are taking the fastest route to that server IF your ISPs fastest route to our Chicago server goes through Seattle Washington first. If they need to contact us for information on our Chicago peer, they can grab our contact information from a peering database and see if we can work out a better route.

I understand that this is frustrating, but the information you’re seeing in other threads are a myriad of different issues at different points of time, and most players are having absolutely fine connections right now. I ask for the tests I ask for so that I can see if there’s anything wrong from our end and help players find the best way to get issues resolved. If this is your ISP’s only route for us though, there’s nothing we can do here. That’s our peer, and that’s the most direct route to the Chicago server, which you will sometimes be put on if that’s the best skill rating matchup for you.

26

Its not a ‘change in peers’ from my ISP…two separate ISPs simultaneously had the same issue immediately after a patch you guys pushed through. If it was a ‘deal’ as you put it, the issue would only persist on 1 of the 2 ISPs i currently have; not to mention it wouldn’t coincide with a patch.

I’ve already clearly proved the issue is on blizzards end, even if its somehow a change you guys made that ended up affecting certain ISPs, its still blizzard’s responsibility to contact & mitigate the issue with the ISPs. Its not their fault you guys made changes to the servers/routes that had a negative impact on ping. Especially considering this is supposed to be a competitive game, but its not anymore to be honest.

So I’m going to clear some things up for you so you see the variables all lined up:

  • Ping issues are ONLY in Overwatch, I tested this extensively in other online games like league for example and I’m stable at about 58ms, which is the norm for my Telus connection (90-95ms in overwatch).
  • WinMTRs show literally not a single issue until it hits a blizzard route relating to Equinix
  • Many other complaints about ping increases. And I mean a lot of them all around the forums. You can claim their part of another problem and they might be, but its no coincidence the amount of threads fluctuated right after a patch. A change you guys made might have created many different variations of a problem.
  • Tested on two separate ISPs. Both ISPs have identical WinMTR results despite being two totally separate companies. Both show complete stability on the ISPs routes. Both increased by 30ms at the exact same time only on blizzard routes.
  • Issues only started the day a patch was pushed through.
  • Last but not least. Your support team already took responsibility for the issue. So I’m trying to comprehend where the doubt lies in this situation. They clearly stated it was Equinix specifically causing the issues, and from that last WinMTR I sent you it indicates the same.

On that note here’s what tech support told me:

Hey there,

Tech Specialist Lorrothir at your service. I’m sorry to hear that the issue has persisted beyond what we’ve tried so far. Rest assured I’m here to help in any way I can.

Taking a look over the files it does look like this may be related to an issue we’re tracking. We don’t have many details on this yet, but for now most users I’ve spoken to that have tried a VPN mention it resolved the issue. Though VPN are unsupported and can cost money, so they are not something we can directly suggest or assist with.

Of course I’ll add the details of this report to our tracking on the matter. Hopefully we will have more information very soon on this.

I do sincerely hope this information helps. If there’s anything else you might need just let us know.

Thanks for playing and enjoy the games!

Then after I tried a VPN with the issues still persisting:

Howdy!

I am Game Master and Tech Specialist Vladosiky and I am here to address your connection concern.

This appears to be the Equnix routing issue that many others are experiencing. The Looking Glass test is not being routed through those nodes, as it is our connection to you. and those all appear to be fine.

The VPN is showing higher spikes at the first hop, but that is to be expected. But the Equinix spikes are still there.

Our main tracking thread is here: https://us.forums.blizzard.com/en/overwatch/t/ow-high-latency-ping-as-of-may-15-2018/104218/111

Once we have an update on the situation, we will be making a post there. Hopefully sooner than later! :slight_smile:

The ‘main tracking thread’ he mentioned was the one you had locked and was from what they told me about the Equinix issue. Which clearly isn’t resolved if I’m still getting latency spikes on Equinix routes.

The only logical conclusion given those variables is that you guys made a change on your end, that negatively impacted certain ISPs. And following technical support’s recommendations they told me to write on the forums, not to roll the dice and see if you guys admit the issue, but to see if there were any updates regarding fixes as they already admitted to the problem.

So I’m really not sure where to go from here other than to stop playing the game entirely. Disappointing to say the least but there’s no point in playing a game with massive ping issues.

1 Like
27

VeiledFlame,

You’re correct, we did have a measured issue at a very specific node that was affecting a large number of players, and it looks like we assumed you were suffering from that issue. That particular problem was creating 100+ MS jumps for hundreds of players within a single city in our peering partner’s network, which is unexpectedly high latency jumps.

However, our network engineers resolved that problem by working with the peer, and your issue doesn’t seem to be related, even if you were having a different issue previously. At this point we’re looking into your issue and not seeing major differences from what is expected for the hops you’re going through.

28

The problem is Overwatch is connecting Alberta players to the Los Angeles servers over the much closer, and lower ping, Chicago server. I’ve pointed this out many times in many different threads and have been told: “It’s my ISP having these problems”.

1 Like
29

So, if I’m reading what you wrote correctly you’re saying going from 50-60ms to 90-100ms is an expected result. As well as seeing 400ms jumps on a blizzard hop? Because I’m getting clear ping jumping hence the double animations in the game. If these are pings you guys ‘expect’ you need to higher your standards quite a bit.

I think the sadder part of what you’re implying here is that anyone using the two ISPs I’m using, Shaw & Telus, are expected to have this poor of a ping (and I’m not including people using Bell, Rogers or any of the smaller companies though I bet they have similar results to me). Which in itself should be unacceptable as I’m sure as you know in Canada, ISPs are limited, those two make up a huge portion of the entire countries’ internet since they’re the most widespread and accessible companies for ISPs. Not to mention the smaller companies still use the exact same lines that Shaw & Telus provide. So essentially you guys view these issues as ‘acceptable’ results for a huge portion of your users (as far as Canada is concerned). And since I’m seeing complaints ranging in location including in the USA I doubt its specific to only Albertans.

I really have to say I don’t like the dancing around the truth using ‘expected result’ essentially as a variable you guys can set. For your playerbase I can say the ‘expected result’ was 58-65ms (non-fibre) with Telus; which is now 90-95ms. And shaw was 50-55ms; which is now 70+ms. The original pings are what I ‘expect’, adding 30ms after a patch and calling it normal is ridiculous.

Yeah Nouveau, I don’t understand where the doubt lies in this situation. If you look at my MTR you can clearly see where the problem is. Certainly isn’t my ISP to any degree. My issue only started after a patch went live and has been this way ever since.

1 Like
30

I just wanted to reply one last time on this thread to point out something funny…it took your servers being DDOSed for my ping to normalize. Tested the game the day before any DDOSing happened and I was hovering at 94ms then when I tested last night my ping was 57ms. I have no idea if being DDOSed ‘motivated’ your team to solve the issues or what went on behind the scenes but so far my connection seems fixed. I have yet to run testing about the general ping jumping that was going on but at least my ping dropped by almost 40ms.

Not sure if that’s just coincidental timing but so far my connection is way better either way.

31

With start of season 11, I’ve been getting ridiculous ping issue. My ping is 200+ms which makes it unplayable. This is what comes up with looking-glass

Blockquote
MTR:
Start: Wed Jul 11 06:22:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 1.1 0.0
2.|-- 37.244.22.3 0.0% 10 0.6 0.6 0.4 0.9 0.0
3.|-- 24.105.30.162 0.0% 10 0.8 1.1 0.8 2.1 0.0
4.|-- 137.221.66.2 0.0% 10 1.4 1.6 1.3 2.5 0.0
5.|-- 137.221.68.70 0.0% 10 2.0 1.4 1.2 2.0 0.0
6.|-- 137.221.65.5 0.0% 10 48.2 47.8 47.7 48.2 0.0
7.|-- 137.221.65.9 0.0% 10 68.5 69.6 68.2 81.0 4.0
8.|-- 137.221.71.32 0.0% 10 68.2 68.6 68.1 72.0 1.1
9.|-- TELUScom 0.0% 10 68.1 68.3 68.0 69.8 0.5
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11/07/2018 06:22:10 UTC
--------------------MTR:
Start: Wed Jul 11 06:22:11 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.23.2 0.0% 10 0.6 0.6 0.5 0.8 0.0
3.|-- 24.105.62.150 0.0% 10 1.0 1.1 0.7 2.4 0.3
4.|-- 137.221.66.10 0.0% 10 2.5 2.6 2.4 3.4 0.0
5.|-- 137.221.69.70 0.0% 10 2.4 2.5 2.3 2.8 0.0
6.|-- 137.221.65.9 0.0% 10 32.1 26.0 22.7 45.4 7.4
7.|-- 137.221.71.32 0.0% 10 22.4 22.6 22.1 25.6 1.0
8.|-- TELUScom 0.0% 10 22.1 22.5 22.0 24.0 0.5
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11/07/2018 06:22:10 UTC

32

Minus GunBBang’s post, I am experiencing similar ping/latency issues as described by VeiledFlame, B72, and Nouveau.
I started playing the game with 39-43 ping when I first bought the game 1 year ago. However with patches from Blizzard, I’ve experience gradual ping increases going from 40 to 50, then with the latency update it was around 70.
Now I am experience latency at 90.
With Overwatch being the only game that experienced this double in ping/latency increase.
Unfortunately after the DDoS I am still experiencing the same latency.

If anyone can shed any light on this issue it would be great. Playing widow, I see scope rubber banding or delayed kills, tracer rubber banding. It’s difficult to play competitive with the increased in ping.

I’m thinking maybe its a Canadian thing where blizzard’s update affected canadian ISPs.

1 Like
33

So your ping is sitting at 90+ms right now? Strange because mine had fixed the other day down to 57ms. Though I still had double animations while playing unfortunately (which doesn’t happen in any other game).

There’s definite ping issues with this game even when the ping seems to normalize though. And its really not playable on a competitive level for me. Frustrating when my shots seems sporadically delayed and my ISP/local connection is incredibly stable.

34

VeiledFlame,

It’s possible that something we changed on our end modified the peering your ISP uses to reach us. A lot of changes may be made by us just advertising a different peer. Are you still connecting to the same LA servers, or are you on the Chicago ones now?

Mikoal,

You’re having a different issue as you’re not in the same area as the posters here. That said, can you post a WinMTR during a game with worse latency anyway? I’m curious as to what your connection is doing.

35

VeiledFlame,

Me too, Yesterday, my ping normalized. But again today, it is spiking up to 200ms again

36

Drakuloth,

Sorry for the late reply, I was busy at work and didnt have this thread alert me on any responses.

Please see below for my MTR

The reason why I suspect I have similar issues to VeiledFlame, B72, and Nouveau is because the symptoms are similar, the slow creeping of increase in latency/ping.
True we are from a different part in Canada, however we both do have Shaw and other ISP.
I am connecting to ORD1 i believe this is chicago.
I hope there could be some valuable insight on the MTR provided and not just “it looks ok” or “you’ll need to contact your ISP”

Note that I edited the MTR to not provide links, so i added a space from things like .net or .ca or .com

Note 2: this was playing with 89ish latency.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
homeportal - 0 263 263 0 0 1 0
wnpgmb0412w-ds01-160-1.dynamic.bellmts. net - 47 93 50 20 24 43 21
wnpgmb010ew-gr01-be43.as7122. net - 0 263 263 20 21 48 21
dis12-winnipeg32_9/3/0.net.bell. ca - 0 263 263 20 21 45 20
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
ae55.bar2.toronto1.level3. net - 1 260 259 53 53 79 53
4.69.216.226 - 17 159 132 0 60 74 59
blizzard-en.ear1.newyork5.level3. net - 1 260 259 66 67 97 66
ae1-br01-eqny8.blizzardonline. net - 1 260 259 64 65 176 64
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
No response from host - 100 53 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

37

Here is a traceroute as well

TRACEROUTE:
traceroute to 142.161.145.5 (142.161.145.5), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.376 ms 0.372 ms 0.373 ms
2 37.244.22.3 (37.244.22.3) 0.952 ms 0.968 ms 0.970 ms
3 24.105.30.158 (24.105.30.158) 2.197 ms 2.200 ms 2.201 ms
4 137.221.66.0 (137.221.66.0) 2.219 ms 2.220 ms 2.223 ms
5 137.221.68.66 (137.221.68.66) 2.199 ms 2.203 ms 2.205 ms
6 137.221.68.32 (137.221.68.32) 4.299 ms 3.454 ms 3.442 ms
7 213.248.78.166 (213.248.78.166) 1.453 ms 1.432 ms 1.453 ms
8 dls-b21-link.telia. net (62.115.123.136) 32.659 ms 32.217 ms 32.266 ms
9 213.155.130.179 (213.155.130.179) 42.251 ms 42.269 ms 42.323 ms
10 213.155.130.176 (213.155.130.176) 51.523 ms 51.545 ms 51.567 ms
11 213.248.79.222 (213.248.79.222) 73.450 ms 73.455 ms 73.459 ms
12 * * *
13 * * *
14 * * *
15 * * *

10/07/2018 05:27:46 UTC

TRACEROUTE:
traceroute to 142.161.145.5 (142.161.145.5), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.372 ms 0.364 ms 0.365 ms
2 37.244.23.2 (37.244.23.2) 0.935 ms 0.960 ms 0.965 ms
3 24.105.62.146 (24.105.62.146) 1.102 ms 1.175 ms 2.421 ms
4 137.221.66.8 (137.221.66.8) 2.471 ms 2.473 ms 2.476 ms
5 137.221.69.70 (137.221.69.70) 2.449 ms 2.451 ms 2.454 ms
6 137.221.69.34 (137.221.69.34) 2.433 ms 1.507 ms 1.497 ms
7 xe-0-0-16-2.a02.chcgil09.us.bb.gin.ntt. net (192.80.17.209) 1.477 ms 1.508 ms 1.494 ms
8 ae-4.r08.chcgil09.us.bb.gin.ntt. net (129.250.4.157) 1.996 ms 2.168 ms 2.156 ms
9 ae-0.a01.chcgil09.us.bb.gin.ntt. net (129.250.4.218) 3.708 ms 3.725 ms 3.725 ms
10 ae-0.bell-canada.chcgil09.us.bb.gin.ntt. net (128.241.3.10) 24.234 ms 24.325 ms 24.183 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 184.150.180.219 (184.150.180.219) 49.211 ms 49.648 ms 49.630 ms

10/07/2018 05:27:46 UTC

PING:
PING 142.161.145.5 (142.161.145.5) 56(84) bytes of data.
64 bytes from 142.161.145.5: icmp_seq=1 ttl=47 time=124 ms
64 bytes from 142.161.145.5: icmp_seq=2 ttl=47 time=123 ms
64 bytes from 142.161.145.5: icmp_seq=3 ttl=47 time=122 ms
64 bytes from 142.161.145.5: icmp_seq=4 ttl=47 time=122 ms

— 142.161.145.5 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 122.073/123.011/124.526/0.994 ms

10/07/2018 05:27:46 UTC

PING:
PING 142.161.145.5 (142.161.145.5) 56(84) bytes of data.
64 bytes from 142.161.145.5: icmp_seq=1 ttl=48 time=70.1 ms
64 bytes from 142.161.145.5: icmp_seq=2 ttl=48 time=69.4 ms
64 bytes from 142.161.145.5: icmp_seq=3 ttl=48 time=69.4 ms
64 bytes from 142.161.145.5: icmp_seq=4 ttl=48 time=69.3 ms

— 142.161.145.5 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 69.394/69.614/70.164/0.453 ms

10/07/2018 05:27:46 UTC

MTR:
Start: Tue Jul 10 05:27:46 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 1.3 0.0
2.|-- 37.244.22.3 0.0% 10 0.5 0.7 0.5 1.9 0.0
3.|-- 24.105.30.158 0.0% 10 1.0 1.2 0.8 2.3 0.3
4.|-- 137.221.66.0 0.0% 10 1.4 1.6 1.4 2.3 0.0
5.|-- 137.221.68.66 0.0% 10 2.5 1.8 1.3 2.5 0.0
6.|-- 137.221.68.32 0.0% 10 1.4 2.2 1.2 9.4 2.4
7.|-- 213.248.78.166 0.0% 10 2.0 1.9 1.4 3.5 0.5
8.|-- dls-b21-link.telia. net 0.0% 10 31.8 33.8 31.5 42.2 3.1
9.|-- 213.155.130.179 0.0% 10 42.5 42.2 42.0 42.5 0.0
10.|-- 213.155.130.176 0.0% 10 51.7 51.8 51.5 52.9 0.5
11.|-- 213.248.79.222 0.0% 10 73.4 73.7 73.3 74.2 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- 184.150.180.219 0.0% 10 101.5 101.2 100.8 101.5 0.0
17.|-- 142.161.0.104 50.0% 10 121.9 108.4 101.3 121.9 8.4
18.|-- wnpgmb0412w-ds01-145-5.dynamic.bellmts. net 0.0% 10 119.9 120.9 119.3 124.5 2.0

10/07/2018 05:27:46 UTC

MTR:
Start: Tue Jul 10 05:27:47 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.23.2 0.0% 10 0.6 0.6 0.4 0.9 0.0
3.|-- 24.105.62.146 0.0% 10 1.0 1.2 0.8 2.2 0.0
4.|-- 137.221.66.8 0.0% 10 2.2 2.2 1.9 3.3 0.3
5.|-- 137.221.69.70 0.0% 10 1.9 2.0 1.8 3.1 0.3
6.|-- 137.221.69.34 0.0% 10 1.7 1.3 1.2 1.7 0.0
7.|-- xe-0-0-16-2.a02.chcgil09.us.bb.gin.ntt. net 0.0% 10 3.0 3.3 1.2 8.7 2.3
8.|-- ae-4.r08.chcgil09.us.bb.gin.ntt. net 0.0% 10 1.8 1.9 1.7 2.8 0.0
9.|-- ae-0.a01.chcgil09.us.bb.gin.ntt. net 0.0% 10 3.2 4.2 1.4 13.9 3.9
10.|-- ae-0.bell-canada.chcgil09.us.bb.gin.ntt. net 0.0% 10 24.4 24.6 24.1 25.6 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- 184.150.180.219 0.0% 10 50.8 49.6 49.0 50.8 0.3
16.|-- 142.161.0.104 60.0% 10 50.2 50.0 49.8 50.2 0.0
17.|-- wnpgmb0412w-ds01-145-5.dynamic.bellmts. net 0.0% 10 69.7 70.1 69.2 75.2 1.7

10/07/2018 05:27:46 UTC

38

guess i replied too late?

39

Heya Mikoal,

Whatever your problem is, it’s not related to what was happening with the rest of the players in this thread. Your test is different from the other ones in this forum. The looking glass you sent in had some issues once the connection got really close to you, but that’s just to the LA authentication servers, not Chicago play servers. I doubt it’s relevant to this issue.

For your specific issue, I recommend contacting our support team or posting your own thread with information on what you’ve done.

It looks like everybody from Alberta has stopped posting in this thread, so I’m going to go ahead and close this out. The rest of you are in different parts of Canada, so whatever routing was going on previoulsy, you’re likely using entirely different backbones. Canada’s a big place.