Latency Increase Alberta, CA

Technical Support
13

Out of curiosity why is it that the ping is changing and getting worse only with Overwatch. Are you guys changing something about the servers/routes? I’m just wondering because I know my ISPs aren’t changing anything to cause the problem, mainly because lets face it ISPs want to do as little as possible.

In any case here’s my WinMTR test (predictably the Equinix routes are much higher latency overall with ping jumping on the fifth hop):

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                           192.168.1.254 -    0 |  224 |  224 |    0 |    0 |    3 |    1 |
|                            10.145.148.1 -    0 |  224 |  224 |    4 |    8 |   26 |    9 |
|               STTLWAWBCI01.bb.telus.com -    0 |  224 |  224 |   22 |   23 |   29 |   23 |
|                  six.blizzardonline.net -    0 |  224 |  224 |   21 |   22 |   37 |   23 |
|       ae1-br01-eqse2.blizzardonline.net -    0 |  224 |  224 |   25 |   27 |  152 |   26 |
|                   No response from host -  100 |   45 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   45 |    0 |    0 |    0 |    0 |    0 |
|       be2-pe02-eqla1.blizzardonline.net -    0 |  224 |  224 |   92 |   93 |   99 |   94 |
|                           24.105.30.129 -    0 |  224 |  224 |   93 |   94 |   99 |   94 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Looking glass:

TRACEROUTE:
traceroute to 199.126.69.84 (199.126.69.84), 15 hops max, 60 byte packets
 1  10.56.70.56 (10.56.70.56)  0.318 ms  0.303 ms  0.301 ms
 2  37.244.22.3 (37.244.22.3)  1.111 ms  1.171 ms  1.240 ms
 3  24.105.30.158 (24.105.30.158)  0.915 ms  0.945 ms  1.011 ms
 4  137.221.66.0 (137.221.66.0)  1.640 ms  1.641 ms  1.696 ms
 5  137.221.68.70 (137.221.68.70)  1.604 ms  1.608 ms  1.609 ms
 6  137.221.65.5 (137.221.65.5)  51.456 ms  49.481 ms  49.453 ms
 7  137.221.65.9 (137.221.65.9)  68.804 ms  68.814 ms  68.821 ms
 8  137.221.71.32 (137.221.71.32)  68.124 ms  68.316 ms  68.290 ms
 9  TELUS.com (206.130.10.58)  68.220 ms  68.198 ms  68.305 ms
10  * * *
11  199.126.69.84 (199.126.69.84)  95.817 ms  96.144 ms  96.188 ms
12  199.126.69.84 (199.126.69.84)  97.532 ms  96.555 ms  96.618 ms


12/06/2018 00:27:46 UTC
--------------------

TRACEROUTE:
traceroute to 199.126.69.84 (199.126.69.84), 15 hops max, 60 byte packets
 1  10.57.100.13 (10.57.100.13)  0.339 ms  0.328 ms  0.327 ms
 2  37.244.23.130 (37.244.23.130)  0.523 ms  0.566 ms  0.626 ms
 3  24.105.62.146 (24.105.62.146)  0.870 ms  0.909 ms  0.968 ms
 4  137.221.66.12 (137.221.66.12)  2.471 ms  2.504 ms  2.598 ms
 5  137.221.69.72 (137.221.69.72)  2.407 ms  2.424 ms  2.426 ms
 6  137.221.65.9 (137.221.65.9)  22.478 ms  22.430 ms  22.424 ms
 7  137.221.71.32 (137.221.71.32)  22.177 ms  22.504 ms  22.556 ms
 8  TELUS.com (206.130.10.58)  25.873 ms  25.088 ms  25.081 ms
 9  * * *
10  199.126.69.84 (199.126.69.84)  75.854 ms  75.523 ms  75.849 ms
11  199.126.69.84 (199.126.69.84)  76.190 ms  76.693 ms  76.079 ms


12/06/2018 00:27:46 UTC
--------------------

PING:
PING 199.126.69.84 (199.126.69.84) 56(84) bytes of data.
64 bytes from 199.126.69.84: icmp_seq=1 ttl=53 time=96.8 ms
64 bytes from 199.126.69.84: icmp_seq=2 ttl=53 time=97.1 ms
64 bytes from 199.126.69.84: icmp_seq=3 ttl=53 time=96.6 ms
64 bytes from 199.126.69.84: icmp_seq=4 ttl=53 time=97.2 ms

--- 199.126.69.84 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 96.657/96.975/97.243/0.392 ms


12/06/2018 00:27:46 UTC
--------------------

PING:
PING 199.126.69.84 (199.126.69.84) 56(84) bytes of data.
64 bytes from 199.126.69.84: icmp_seq=1 ttl=54 time=77.0 ms
64 bytes from 199.126.69.84: icmp_seq=2 ttl=54 time=76.7 ms
64 bytes from 199.126.69.84: icmp_seq=3 ttl=54 time=75.7 ms
64 bytes from 199.126.69.84: icmp_seq=4 ttl=54 time=76.5 ms

--- 199.126.69.84 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 75.736/76.508/77.071/0.526 ms


12/06/2018 00:27:46 UTC
--------------------

MTR:
Start: Tue Jun 12 00:27:46 2018
HOST: Blizzard Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.56.100.81      0.0%    10    0.3   0.3   0.2   0.5   0.0
  2.|-- 37.244.22.131     0.0%    10    0.5   0.5   0.4   0.8   0.0
  3.|-- 24.105.30.158     0.0%    10    0.9   1.0   0.8   2.0   0.0
  4.|-- 137.221.66.4      0.0%    10    1.5   1.5   1.4   1.6   0.0
  5.|-- 137.221.68.72     0.0%    10    1.6   1.5   1.3   2.3   0.0
  6.|-- 137.221.65.5      0.0%    10   47.7  47.8  47.7  48.3   0.0
  7.|-- 137.221.65.9      0.0%    10   68.3  69.7  68.2  81.5   4.1
  8.|-- 137.221.71.32     0.0%    10   68.0  68.2  68.0  68.6   0.0
  9.|-- TELUS.com         0.0%    10   68.0  68.3  68.0  69.4   0.0
 10.|-- ???              100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- 199.126.69.84     0.0%    10   96.9  96.1  95.5  96.9   0.0


12/06/2018 00:27:46 UTC
--------------------

MTR:
Start: Tue Jun 12 00:27:46 2018
HOST: Blizzard Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.57.100.13      0.0%    10    0.3   0.3   0.2   0.5   0.0
  2.|-- 37.244.23.130     0.0%    10    0.5   0.5   0.4   0.5   0.0
  3.|-- 24.105.62.146     0.0%    10    0.9   1.2   0.7   2.4   0.5
  4.|-- 137.221.66.12     0.0%    10    2.5   2.6   2.3   2.9   0.0
  5.|-- 137.221.69.72     0.0%    10    2.4   2.3   2.2   2.4   0.0
  6.|-- 137.221.65.9      0.0%    10   22.3  23.8  22.3  36.1   4.3
  7.|-- 137.221.71.32     0.0%    10   22.2  22.3  22.2  22.8   0.0
  8.|-- TELUS.com         0.0%    10   23.0  22.3  22.1  23.0   0.0
  9.|-- ???              100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- 199.126.69.84     0.0%    10   75.8  76.1  75.5  78.1   0.6


12/06/2018 00:27:46 UTC
--------------------

Edit: Updated looking glass test

14

Just want to chime in here as an Australian.

Something they did a few major patches ago has changed something, Guarantee it.

My friends and I all live within a couple of Kilometers from each other and would get 25-29ms ping, then magically after a major update our ping doubles and even triples, never going below about 50.

Refuse to believe a change with all our ISPs just happened to coincide with the 6 hr patch window.

3 Likes
15

I agree I know for a fact nothing on my ISPs end has changed. All my other games pings have remained stable and identical at their previous values. At this point I’ve had to quit playing blizzard games completely out of frustration and the sheer amount of shot delay/double animations that are occurring. The other ISP I have at my house behaves identically to the other.

The thing that bothers me is if they knew they were making changes to the routes or servers why didn’t they preemptively inform the ISPs of the changes if they did actually need changes to happen. And if they “couldn’t” get the ISPs to prepare for the changes then maybe its not a good idea to push them through seeing as people all over the world seem to be having issues.

All this really comes down to sadly is some quality control instead of just pushing patches through to add more money making content. Not to mention if there’s a change that breaks the game for a good portion of the community you can roll them back, that’s the entire point to a patch and having versioning in software/games.

1 Like
16

Looking Glass

TRACEROUTE:
traceroute to 68.150.133.154 (68.150.133.154), 15 hops max, 60 byte packets
 1  10.56.100.81 (10.56.100.81)  0.258 ms  0.246 ms  0.244 ms
 2  37.244.22.131 (37.244.22.131)  0.583 ms  0.668 ms  0.804 ms
 3  24.105.30.162 (24.105.30.162)  1.131 ms  1.261 ms  1.298 ms
 4  137.221.66.6 (137.221.66.6)  1.657 ms  1.707 ms  1.790 ms
 5  137.221.68.72 (137.221.68.72)  1.560 ms  1.572 ms  1.572 ms
 6  137.221.65.7 (137.221.65.7)  8.466 ms  8.438 ms  8.430 ms
 7  137.221.70.32 (137.221.70.32)  8.241 ms  8.296 ms  8.268 ms
 8  rt0sj-equinix.cl.shawcable.net (206.223.116.20)  12.180 ms  11.682 ms  11.665 ms
 9  rc4sj-tge0-8-0-0.cl.shawcable.net (66.163.67.122)  12.901 ms  12.910 ms  12.908 ms
10  rc2wt-be60.wa.shawcable.net (66.163.78.73)  28.247 ms  28.572 ms  28.577 ms
11  rc3no-be100.cg.shawcable.net (66.163.75.234)  42.187 ms  41.877 ms  42.309 ms
12  rc1we-be6.ed.shawcable.net (66.163.64.70)  45.980 ms  45.853 ms  45.861 ms
13  dx3sg-la1-s1.ed.int.shawcable.net (64.59.186.78)  46.711 ms  46.784 ms  46.774 ms
14  * * *
15  * * *


11/06/2018 19:13:22 UTC
--------------------

TRACEROUTE:
traceroute to 68.150.133.154 (68.150.133.154), 15 hops max, 60 byte packets
 1  10.57.68.13 (10.57.68.13)  0.359 ms  0.341 ms  0.338 ms
 2  37.244.23.2 (37.244.23.2)  0.956 ms  0.958 ms  0.958 ms
 3  24.105.62.150 (24.105.62.150)  1.164 ms  1.167 ms  1.252 ms
 4  137.221.66.10 (137.221.66.10)  3.866 ms  3.873 ms  3.874 ms
 5  137.221.69.70 (137.221.69.70)  3.852 ms  3.852 ms  3.858 ms
 6  137.221.69.34 (137.221.69.34)  3.829 ms  2.835 ms  2.858 ms
 7  rt1ec-equinix.il.shawcable.net (208.115.136.20)  4.026 ms  2.550 ms  2.517 ms
 8  rc3sc-be25-1.wp.shawcable.net (66.163.75.133)  17.420 ms  17.796 ms  17.775 ms
 9  66.163.70.78 (66.163.70.78)  51.661 ms  51.692 ms  51.693 ms
10  dx3sg-la0-s1.ed.int.shawcable.net (64.59.186.74)  52.991 ms  52.985 ms  52.966 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


11/06/2018 19:13:22 UTC
--------------------

MTR:
Start: Mon Jun 11 19:13:22 2018
HOST: Blizzard                  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.57.100.13                       0.0%    10    0.2   0.3   0.2   0.6   0.0
  2.|-- 37.244.23.130                      0.0%    10    0.5   0.8   0.4   2.4   0.5
  3.|-- 24.105.62.150                      0.0%    10    1.5   1.4   1.1   2.4   0.0
  4.|-- 137.221.66.14                      0.0%    10    2.0   2.1   1.9   2.5   0.0
  5.|-- 137.221.69.68                      0.0%    10    3.7   5.3   1.8  33.3   9.8
  6.|-- 137.221.69.32                      0.0%    10    1.4   2.4   1.2  10.9   3.0
  7.|-- rt1ec-equinix.il.shawcable.net     0.0%    10    2.2   2.1   1.7   2.4   0.0
  8.|-- rc3sc-be25-1.wp.shawcable.net      0.0%    10   16.8  16.9  16.6  17.3   0.0
  9.|-- 66.163.70.78                       0.0%    10   50.7  50.8  50.5  51.0   0.0
 10.|-- dx3sg-la0-s1.ed.int.shawcable.net  0.0%    10   51.9 102.1  51.9 553.1 158.5
 11.|-- ???                               100.0    10    0.0   0.0   0.0   0.0   0.0


11/06/2018 19:13:22 UTC
--------------------

MTR:
Start: Mon Jun 11 19:13:22 2018
HOST: Blizzard                  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.56.100.81                       0.0%    10    0.2   0.3   0.2   0.3   0.0
  2.|-- 37.244.22.131                      0.0%    10    0.5   0.6   0.4   1.3   0.0
  3.|-- 24.105.30.162                      0.0%    10    1.2   1.0   0.7   2.0   0.0
  4.|-- 137.221.66.6                       0.0%    10    1.6   1.7   1.4   2.1   0.0
  5.|-- 137.221.68.72                      0.0%    10    1.4   1.4   1.3   1.8   0.0
  6.|-- 137.221.65.7                       0.0%    10    8.5  10.0   8.4  23.8   4.8
  7.|-- 137.221.70.32                      0.0%    10    8.3   9.7   8.2  22.8   4.5
  8.|-- rt0sj-equinix.cl.shawcable.net     0.0%    10    8.6  10.5   8.6  11.9   0.9
  9.|-- rc4sj-tge0-8-0-0.cl.shawcable.net  0.0%    10   11.4  11.0   9.7  12.9   0.8
 10.|-- rc2wt-be60.wa.shawcable.net        0.0%    10   26.9  27.0  26.8  27.3   0.0
 11.|-- rc3no-be100.cg.shawcable.net       0.0%    10   42.1  42.2  41.9  42.7   0.0
 12.|-- rc1we-be6.ed.shawcable.net         0.0%    10   46.1  46.0  45.8  46.4   0.0
 13.|-- dx3sg-la1-s1.ed.int.shawcable.net  0.0%    10   48.1  78.3  46.7 360.2  99.0
 14.|-- ???                               100.0    10    0.0   0.0   0.0   0.0   0.0


11/06/2018 19:13:22 UTC
--------------------

WinMTR

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          hitronhub.home -    0 |   40 |   40 |    4 |   15 |   51 |   14 |
|                            68.150.128.1 -    0 |   40 |   40 |    9 |   15 |   50 |   14 |
|          rc3ar-be109-1.ed.shawcable.net -    0 |   40 |   40 |   12 |   19 |   49 |   15 |
|                           66.163.70.129 -    0 |   40 |   40 |   12 |   18 |   64 |   16 |
|              rc3no-be6.cg.shawcable.net -    0 |   40 |   40 |   14 |   21 |   53 |   16 |
|            rc2wt-be100.wa.shawcable.net -    0 |   40 |   40 |   31 |   37 |   56 |   36 |
|           rc1wt-be18-1.wa.shawcable.net -    0 |   40 |   40 |   31 |   37 |   54 |   35 |
|      eqix-se2.blizzardentertainment.com -    0 |   40 |   40 |   30 |   36 |   54 |   34 |
|       ae1-br01-eqse2.blizzardonline.net -    0 |   40 |   40 |   32 |   37 |   53 |   34 |
|xe-0-0-0-1-br01-eqsv5.blizzardonline.net -    0 |   40 |   40 |   50 |   55 |   66 |   55 |
|xe-0-0-1-1-br02-eqla1.blizzardonline.net -    0 |   40 |   40 |   59 |   71 |  106 |   78 |
17

Hey folks,

I checked out these tests as well as information on your accounts’ average ping to games lately. They both seem pretty close to expected values for the route you’re taking to our servers through the peers we use for your ISPs in Alberta. You’re hovering about 10 MS from what we expect for you across our peers specifically, and B72’s test was so short we can’t be sure the results aren’t skewed by some of those brief spikes in the test. I can’t say for sure why the ping increased, but I can say that at least what you’re seeing on our networks at least for now SEEMS normal.

As part of my investigation in our tools, I also did a search for both of your ISPs and it looks like you’re both very close to what others on your ISPs are getting as well. As a result, I don’t think there’s anything to be done routing-wise for you. We should instead focus on the spikes you mentioned in the OP, B72, unless we get some more WinMTRs with glaring problems with routing.

Unfortunately with the tools I have on my end I can’t see the ‘spikes’ you’re talking about, just your averages. I did see one instance for each of you in the last week where you were on an unexpected server.

B72 - you ended up on a France server, but you were logged into EU when that happened.

VeiledFlame - you wound up on a Brazilian server, I’m unsure why this happened. You may have been partied with a friend from near those servers or taken a very obscene spike latency spike while the matchmaker was testing your connection to the LA servers. That may have made the servers temporarily think that Brazil was the best connection option at the time.

These were single issues, however, and shouldn’t be confused with your normal connection changes. VeiledFlame - you did your test to the login servers, not the game servers. This isn’t going to be indicative of your in game ping as a result. So, here’s what I need you two to do to look into the spikes you reported a bit more.

In the WinMTR article is a process to get your game server IP from the in game network graph (Ctrl+Shift+N).

Follow this process at the beginning of a game and run your WinMTR for that whole game. If you see a situation where you’re getting several bad spikes, save that test and upload the results here. If you get nothing, repeat this until you catch a game with some spikes in it. I also need you to grab some screenshots of your network graph when things get nasty for you. If you can upload those to imgur or a similar website and link it here, we can check that for options. Place your link between two ` marks if you get a link error while posting. It’ll look like this:

link goes here

Thanks for the info and patience. Hopefully with this data we can get a better look at what’s going on for you.

18

Dystilled,

You’re in Australia, unfortunately this isn’t going to be the same problem as these two players are mentioning. I’m pretty sure you’re noticing the change from latency to RTT we did back in march. If this isn’t the case, you’ll want to create your own thread.

19

Before I even begin to talk about the issue there is something about that WinMTR article that always bothered me. For Overwatch, it firsts tells you to get the ip for the server you will play on by joining the practice range and using ctrl+shift+n. This is weird because the practice range will always put you on the least busy server (usually asia?) Sounds like you would get a lot of WinMTRs from servers the user isn’t even playing on.

Anyways…

Yes, that’s the issue. Latency is much higher than before (couple months ago), due to routing. Unless I am misunderstanding what you are saying here.

Again, that’s kind of the whole issue. Of course we are getting similar latency to everyone else on our ISP, because everyone on our ISPs (Telus, Shaw) is affected by this routing issue. It’s not like we want better latency then everyone else, we just want the latency we used to be getting with our ISPs.

This was on purpose just to test something. I know the issue I am having and wouldn’t mistake it for being put on the wrong server.

I shouldn’t have used the word ‘Spike’, that was my mistake. I should have said fluctuations. Before this routing issue, I used to get around 57RTT flat. It would stay there all day. Now, my RTT fluctuates from 75 - 85 constantly changing. Obviously, not groundbreaking, but it was a symptom I noticed.

I can tell you for sure that this issue isn’t ‘normal’ and I won’t let it be passed off as such. I’ve played fps games for quite a while, I’ve been top500 NA in Overwatch on a couple accounts. I know the game and I know the latency I used to, and should be getting.

I think many people, including myself, whose ISPs are Shaw or Telus would appreciate if you continued to look into the matter. I’ll be back with a longer WinMTR, as you requested.

3 Likes
20

@Drakuloth ‘Normal’ pings don’t hit 95ms…you can’t begin to claim that’s a typical ping, there’s a bigger issue obviously since everyone seems to be having close to double their ping. So technically you’re correct, these are ‘normal’ values for the new lower standards you guys are setting for ping. I used to have 40ms (50ms with the patch that changed how the ping is displayed) on my shaw connection, now it jumps to 75-85 exactly like B72 said; the connection I have with Telus to your servers aren’t a stable 95ms, it keeps slingshotting back and forth. I’ve had non-stop double animations every 2nd or 3rd shot which is indicative of a problem even without the need to test. Though don’t get me wrong I understand the need for proof on the matter, however if you browse the forums every 2nd topic is about ping issues. And I know you’re aware of the other topics since a good portion of them I see you’re the one asking for WinMTRs. If that alone doesn’t set an alarm off of a bigger issue I don’t know what will.

Also in response about being on a brazilian server: I never test my ping with a friend. There’s no reason I should be routed to a brazilian server and I have no earthly idea why its routing me there. Why would a latency spike cause the servers to ‘think’ I want to be on a brazilian server, are these not based on a geo-location & the fact I picked US servers in the blizzard launcher? This has been happening ever since you guys patched the game and for example I go in the practice range I get put on a foreign server that has 250ms+. Its been happing for a year at least but its much worse now. To fix that issue I have to keep leaving the practice range and rejoining until it puts me on a US server. I have to do that about 3 or 4 times before it corrects itself. This happens on both of my ISPs Shaw and Telus.

Furthermore the netgraph doesn’t show ping spikes. Like B72 said above, the issue is the general increase in ping. Since the increase of ping has happened I’ve seen plenty of complaints about rubber-banding, delayed shots, and double animations.

I will say I don’t like being told a 30ms ping increase is a ‘typical & normal’ result. Yes we know everyone using the ISPs are getting the same results, that’s the problem. Blizzard support already confirmed the issues, it’s not really a question of if they exist its a question on how & when you guys intend to fix them. The Equinix issue that blizzard support kindly told me about is what I’m assuming is the cause.

All that being said, I’d be happy to run more WinMTRs this evening on my Telus connection and if I have time on my Shaw connection. I’ll run my tests in the practice range, Quick Play, & Competitive (though playing in competitive is just asking to lower your rank at this point).

1 Like
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