OW High latency/ping as of May 15, 2018

Hi all,

as recommended by the blizzard support agent after talking to them with regards to this issue, I thought I’d post it here so others can chime in with their own results.

I live in Alberta, Canada, and noticed just 2 days ago my ping which was normally quite nominal (60-70ms or so) had spiked to a frustrating 150ms+ in-game. I’ve done a little sleuthing to figure out what was happening and have discovered that the issue lies on Blizzard’s end - specifically, a routing problem between their servers in their “blizzardonline-net” group of servers.

For those of you that want to know more and/or are experiencing this issue:

  • the problem is for sure not my - and likely not your! - local connection
  • connecting to a VPN to route into the blizzard network in a different method solves the issue (more on that in a bit).

With regards to reproducing the problem, using a third party public trace you can replicate the issue. I’m focusing on/pinging to OW’s US-West server (24.105.30.129) using the public trace function on Network-Tools-com (results to US-Central are similar). Also, I’ve had to change the server/web extensions from .'s to -'s in order to avoid the forum not letting me post due to including links, so if stuff looks weird that’s why.

TraceRoute from Network-Tools.com to 24.105.30.129
Hop	(ms)	(ms)	(ms)		     IP Address	Host name
1 	  0 	  0 	  0 	     184.105.25.73	 v509.core1.dal1.he.net  
2 	  0 	  0 	  0 	     206.53.202.43	 pr01-eqfr5.blizzardonline.net  
3 	  1 	  1 	  0 	     137.221.74.33	 ae1-br01-eqda6.blizzardonline.net  
4 	  143 	  143 	  144 	     137.221.65.67	 hu-0-0-0-0-pe02-swlv10.blizzardonline.net  
5 	  143 	  143 	  143 	     137.221.83.74	 be3-pe01-swlv10.blizzardonline.net  
6 	  29 	  29 	  29 	     137.221.65.68	 et-0-0-2-br01-eqla1.blizzardonline.net  
7 	  143 	  143 	  143 	     137.221.68.67	 be1-pe01-eqla1.blizzardonline.net  
8 	  145 	  143 	  143 	     24.105.30.129	  -  
Trace complete

as you can see, specifically in hop 3-4 is where you get a massive spike in ping, and the server on hop 6 interestingly is responding normally in addition to some of the earlier servers in the grouping, which strongly indicates the issue is on Blizzard’s end. There was a brief hour or so yesterday in which it seemed to be resolved, and then latency increased once again – judging by the number of posts popping up concerning high ping I’m guessing this issue may be the root cause of a lot of frustration.

After a bit of back and forth with Blizzard support to rule out my local connection, they have made a case report and acknowledged that this issue is on their end, so I’m hopeful that we’ll see a resolution soon (my existing ticket # is US63327880 if anyone else needs to reference it).

R.e. VPN: using a VPN to change the way I’m routing into the OW US-West does reduce the ping, down to where it’d normally be (reporting 60-70ms in-game). From my provider I’m routing to Seattle -> OW US-West – so, this adds distance overall, but results in a playable game which is a plus.

This isn’t a great permanent solution but it is an option if you’re experiencing this issue like me, until some sort of more permanent resolution is made on Blizz’s end.

20 Likes

Been having the exact same issue the past day or two…

Before this mess, my ping hovered around 40-50ms with occasional spikes up to 120ms; now, every time I join a match or the practice range (regardless of actual network speed) my ping starts at 300ms+ and quickly stablizes to 170ms - funny, because just yesterday I started using Ethernet to solve the aforementioned lag spikes present before this high-ping issue. My network’s download speed (~10.0Mbps) remained the same for any sort of download; also, my ping for other online titles (such as CSGO, PUBG or Fortnite) remains a healthy 40-50ms.

From Tucson, AZ

2 Likes

Vancouver, BC here. Having the same problem since yesterday; ping has gone from ~50 to ~165.

2 Likes

Sorry that you guys are experiencing this as well, but we’re all in this together at least…

I have had some success with using a VPN to play - it’s been a lot more consistent than just living with whatever 160+ms I end up getting by trying to play normally right now.

I’d definitely recommend to anyone else experiencing that to look into one of the bigger popular VPN services until the issue gets solved.

I’m just glad Blizz is aware and is likely taking steps to get this fixed (…hopefully before the next event launches…).

If any of you have any questions about VPNs or the like, I’m happy to try to help you out with it.

1 Like

What is the best VPN service out there?

1 Like

+1 from Vancouver.
Usually 50-60ms. Since a day or two ago it has shot up to 160+

3 Likes

Used to be at 40-54 ms. Since the last 2 patches I am constantly at 143 ms. I hope this gets fixed soon. I might add that I cleaned caches, restarted internet multiple times, and tried other solutions and still nothing.

2 Likes

There’s several that a lot of people use - for gaming specifically, these are the names that keep coming up from my cursory research in no particular order:

  • VyprVPN (Goldenfrog)
  • IPVanish
  • NordVPN
  • PIA (Private Internet Access)
  • ExpressVPN

I can’t directly link them in this forum, but they’re easy enough to find with a google search. As for which one is best for you, you’ll have to do a little research yourself and decide what looks like the best fit.

Have any of these actually worked for you? I tried a few yesterday and ‘cant connect to game servers’ when i try ro launch the game

I am having the exact same issues. It seems to be the final few connections to blizzardonline.

I have NordVPN but it only brings it down to about 100.

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     8 ms     7 ms  10.250.0.1
  3    12 ms    11 ms    11 ms  172.30.1.5
  4    13 ms    13 ms    13 ms  172.30.2.14
  5    23 ms    20 ms    21 ms  10ge5-8.core1.cys1.he.ne(t) [184.105.45.217]
  6    24 ms    25 ms    26 ms  10ge13-3.core1.den1.he.ne [184.105.64.41]
  7    33 ms    36 ms    34 ms  100ge14-1.core1.mci3.he.ne [184.105.64.50]
  8    46 ms    46 ms    47 ms  100ge8-1.core2.chi1.he.et [184.105.81.210]
  9    49 ms    49 ms    50 ms  eqix-ix-ch1.blizzard.c [208.115.136.85]
 10    47 ms    48 ms    49 ms  ae1-br01-eqch2.blizzardonline.nt [137.221.69.33]
 11    77 ms    74 ms    74 ms  xe-0-0-0-0-br01-eqla1.blizzardonline.nt [137.221.65.52]
 12   189 ms   189 ms   189 ms  be1-pe01-eqla1.blizzardonline.nt [137.221.68.67]
 13   191 ms   189 ms   198 ms  lax-eqla1-ia-bons-02.blizzardonline.et [137.221.66.3]
 14   190 ms   189 ms   188 ms  24.105.30.129

However the VPN bringing my ping down to around 100 still has it feeling unplayable. With rubber banding.

This traceroute is not making much sense, as it looks like to be jumping from a single ISP hub to one of the Blizzard Nodes… I feel there is information missing. Can you please run a WinMTR test instead:

  1. Download WinMTR from http://winmtr.net/download-winmtr/ (Console players need a Windows Desktop Computer connected to the same network as their console to do this.)
  2. Unzip the WinMTR.zip file to the Desktop.
  3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
  4. Run the WinMTR.exe
  5. Type the IP address you want to trace in the “Host” field. To get the correct IP you will actually need to open up the game and go Practice Vs AI or Quick Play and if you are on PC hit Ctrl+Shift+N and it will bring up the ingame network diagnostic graph, or go to Video > Options > Display Network Performance Graph if you are on any platform including Console. In the top left corner is the IP address you want to run WinMTR to.
    Network Graph
    note When looking at the IP it will show up ingame as something like 12.34.56.78:12345. You will want to leave the last 5 digits and the colon at the end off and the IP you want to use is just the 12.34.56.78
  6. Once you notice the connection issue while playing, play for about 6 more minutes, minimize the game and click on “Stop”.
  7. Click on “Copy text to clipboard”, then return to this forum thread.
  8. Type two sets of four squiggly lines and then paste the contents of the WinMTR test between: ~~~~ Paste WinMTR Test Results Here ~~~~

If in the event you can’t even connect to Overwatch and get into any game mode at all, please use one of the following IP addresses based on your geographical region:

  • US West - 24.105.30.129
  • US Central - 24.105.62.129
  • Brazil - 54.207.107.12
  • Europe - 185.60.114.159
  • Europe - 185.60.112.157
  • Korea - 211.234.110.1
  • Taiwan - 203.66.81.98

Your numbers look relatively normal. Did you have any connection problems while running this Traceroute? It can be more accurate to capture information by doing a WinMTR instead, see my reply above.

Well I used to have a ping of 50-60. Now I’m at 150 if I’m lucky. I didn’t have a connection problem during the Traceroute.

Here are the results of the WinMTR. I had a ping of about 155 the whole time.

|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  217 |  217 |    0 |    0 |    3 |    0 |
|                              10.250.0.1 -    0 |  217 |  217 |    6 |    9 |   19 |    6 |
|                              172.30.1.5 -    0 |  217 |  217 |    9 |   13 |   18 |   12 |
|                             172.30.2.14 -    0 |  217 |  217 |   10 |   14 |   19 |   10 |
|               10ge5-8.core1.cys1.he.net -    0 |  217 |  217 |   18 |   22 |   35 |   23 |
|              10ge13-3.core1.den1.he.net -    0 |  217 |  217 |   21 |   24 |   30 |   25 |
|             100ge14-1.core1.mci3.he.net -    0 |  217 |  217 |   33 |   38 |   49 |   35 |
|              100ge8-1.core2.chi1.he.net -    0 |  217 |  217 |   42 |   47 |   60 |   43 |
|                eqix-ix-ch1.blizzard.com -    0 |  217 |  217 |   46 |   49 |   63 |   57 |
|       ae1-br01-eqch2.blizzardonline.net -    0 |  217 |  217 |   47 |   55 |  190 |   55 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~~~

I am also experiencing this. Used to have latency of 30-40, now usually sits at 110-120.

Tracing route to 24.105.62.129 over a maximum of 30 hops

 1    <1 ms    <1 ms    <1 ms  10.6.0.1
 2    <1 ms    <1 ms    <1 ms  192.206.106.1
 3    37 ms     2 ms     2 ms  172.31.10.9
 4     2 ms     2 ms     2 ms  38.104.212.58
 5     3 ms     3 ms     3 ms  be4393.nr12.b020735-3.oma01.atlas.cogentco.com [38.104.212.57]
 6     3 ms     3 ms     3 ms  te0-0-2-1.rcr11.oma01.atlas.cogentco.com [154.24.48.249]
 7     6 ms     6 ms     8 ms  be3154.rcr21.dsm01.atlas.cogentco.com [66.28.4.197]
 8    13 ms    13 ms    13 ms  be2639.ccr41.ord01.atlas.cogentco.com [154.54.29.49]
 9    13 ms    13 ms    13 ms  be2765.ccr41.ord03.atlas.cogentco.com [154.54.45.18]
10    23 ms    15 ms    15 ms  38.104.102.29
11    18 ms    16 ms    16 ms  ae1-br01-eqch2.blizzardonline.net [137.221.69.33]
12   110 ms   110 ms   110 ms  be1-pe01-eqch2.blizzardonline.net [137.221.69.67]
13   109 ms   110 ms   108 ms  24.105.62.129
1 Like

Yeah. The last few jumps for blizzardonline have a dramatic jump.

Hi WyomingMyst - yes, that IS what the traceroute is doing because it’s using a public trace available at Network-Tools (dot) com.

The purpose of me showing this is to illustrate how the problem exists independently of my own personal connection.

To be clear: I have already been through a support ticket with other Blizzard technical agents and given them all sorts of traceroutes and MTR data and info from Blizz’s own Looking Glass to verify the issue at hand. The agents confirmed for me that this is on Blizzard’s end and a case would be created - and encouraged me to post here by way of additional information for those afflicted besides myself. :slight_smile:

@Timotmcc: someone else indicated NordVPN worked for them, I myself use PIA and it allows me to play. They have a “Seattle” endpoint and a “Silicon Valley” endpoint that both bring the ping down to an acceptable level for me personally - though gameplay is not as smooth as the raw connection was before this debacle.

1 Like

Upvote,

I am also having the same issue. Everything is fine on my end. Frustrating though. I hope this is a problem they can solve fast. I just got the new pink mercy skin! :smiley:

My ping went from 70ms to 180ms on Thursday, glad to see that it isn’t just me!

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   42 |   42 |    0 |    0 |    1 |    0 |
|            lo0-0-agg01-van.teksavvy.com -    0 |   42 |   42 |   23 |   46 |   67 |   42 |
|           ae0-10-bdr01-van.teksavvy.com -    0 |   42 |   42 |   24 |   46 |   67 |   40 |
|                  v704.core1.yvr1.he.net -    0 |   42 |   42 |   24 |   49 |   72 |   45 |
|             100ge10-2.core1.sea1.he.net -   11 |   28 |   25 |   63 |   85 |  111 |   77 |
|      eqix-se2.blizzardentertainment.com -    7 |   32 |   30 |   63 |   85 |  111 |   76 |
|       ae1-br01-eqse2.blizzardonline.net -   10 |   31 |   28 |   64 |   89 |  112 |   73 |
|xe-0-0-1-1-br02-eqch2.blizzardonline.net -    0 |   42 |   42 |   85 |  126 |  252 |  114 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    8 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Vancouver, BC, also having problems, weird routing which seems to be on blizzard’s side, going through Europe?

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  BlackNBlue.teksavvy.com [192.168.1.1]
  2    74 ms    13 ms    12 ms  24.80.128.1
  3    22 ms    11 ms    14 ms  69-172-144-1.cable.teksavvy.com [69.172.144.1]
  4    11 ms    11 ms    12 ms  xe-1-3-1-1395-agg01-van.teksavvy.com [76.10.191.33]
  5    55 ms    11 ms    20 ms  ae0-10-bdr01-van.teksavvy.com [76.10.191.1]
  6    18 ms    11 ms    21 ms  v704.core1.yvr1.he.net [66.160.158.249]
  7    43 ms    43 ms    47 ms  100ge10-2.core1.sea1.he.net [184.105.64.109]
  8    43 ms    41 ms    42 ms  six.blizzardonline.net [206.81.81.122]
  9    42 ms    41 ms    42 ms  ae1-br01-eqse2.blizzardonline.net [137.221.73.33]
 10    61 ms    61 ms    61 ms  xe-0-0-0-1-br01-eqsv5.blizzardonline.net [137.221.65.40]
 11    71 ms    79 ms    65 ms  xe-0-0-1-1-br02-eqla1.blizzardonline.net [137.221.65.6]
 12   163 ms   162 ms   168 ms  be2-pe02-eqla1.blizzardonline.net [137.221.68.73]
 13   164 ms   163 ms   163 ms  lax-eqla1-ia-bons-03.blizzardonline.net [137.221.66.7]
 14   164 ms   163 ms   162 ms  24.105.30.129

Trace complete.