Latency to Overwatch Servers only

My ping to google is as follows:

Reply from 172.217.1.206: bytes=32 time=18ms TTL=53
Reply from 172.217.1.206: bytes=32 time=25ms TTL=53
Reply from 172.217.1.206: bytes=32 time=22ms TTL=53
Reply from 172.217.1.206: bytes=32 time=20ms TTL=53

Ping statistics for 172.217.1.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 25ms, Average = 21ms

I do the network testing for the overwatch west US server:

Pinging 24.105.30.129 with 32 bytes of data:
Reply from 24.105.30.129: bytes=32 time=196ms TTL=231
Reply from 24.105.30.129: bytes=32 time=187ms TTL=231
Reply from 24.105.30.129: bytes=32 time=193ms TTL=231
Reply from 24.105.30.129: bytes=32 time=190ms TTL=231

Ping statistics for 24.105.30.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 196ms, Average = 191ms

I do a tracert too:
Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  <Redacted>
  2    17 ms    14 ms    14 ms  <Redacted>
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    21 ms    23 ms    30 ms  206.51.46.69
  9    31 ms    24 ms    29 ms  184.105.81.214
 10    56 ms    59 ms    54 ms  184.105.222.105
 11    45 ms    43 ms    44 ms  206.53.202.43
 12   186 ms   189 ms   209 ms  137.221.74.33
 13   196 ms   188 ms   194 ms  137.221.65.67
 14   201 ms   193 ms   199 ms  137.221.65.32
 15    62 ms    63 ms    83 ms  137.221.65.68
 16   194 ms   197 ms   201 ms  137.221.68.69
 17   188 ms   193 ms   189 ms  24.105.30.129

I can ping hop 15 as the time tracert replies but both 16 and 17 are high and 17 matches the latency of my ping. The timeout hops aren’t uncommon a lot of nodes these days just don’t respond to ICMP requests. As you can see it is not my local network but something close to your server.

This has been an issue for over 12 hours now with no change.

Same here, for about the same amount of time too, since last night. My tracert looks similar as well.

  1     1 ms    <1 ms     1 ms  hitronhub.home [192.168.0.1] 
  2    11 ms     9 ms    16 ms  10.69.56.1 
  3    13 ms    12 ms    19 ms  173.246.244.13 
  4    27 ms    33 ms    27 ms  er0-dllstx.zitomedia.net [74.81.98.201] 
  5    24 ms    28 ms    28 ms  v1002.core1.dal1.he.net [184.105.255.93] 
  6    23 ms    24 ms    24 ms  pr01-eqfr5.blizzardonline.net [206.53.202.43] 
  7   162 ms   157 ms   162 ms  ae1-br01-eqda6.as57976.net [137.221.74.33] 
  8    44 ms    44 ms    53 ms  et-0-0-4-br01-eqch2.as57976.net [137.221.65.38] 
  9   161 ms   157 ms   162 ms  be1-pe01-eqch2.as57976.net [137.221.69.67] 
 10   160 ms   159 ms   159 ms  chi-eqch2-ia-bons-02.as57976.net 
[137.221.66.11] 
 11   154 ms   171 ms   170 ms  24.105.62.129 

It seems both of us get routed through the 137.221.74.33 IP address for some reason, which is in Europe. I imagine this has to be a problem on Blizzards end.

1 Like

Been doing it since the 3rd, Blizzard are blaming ISPs and not their servers which is the actual issue.

I did a GEO IP on it and got this:

Continent: North America
Country: United States
Country Code: US
Country CF: 99
Region: South Central
State: Texas
State Code: Tx
State CF: 88
DMA: 623
MSA: 19100
City: Dallas
Postal Code: 75219
Timezone: GMT-06:00
Area Code: 214
City CF: 77
Latitude: 32.80543
Longitude: -96.81423

I think there’s a bad connection either there or here:

137.221.66.11

Continent: North America
Country: United States
Country Code: US
Country CF: 99
Region: Southwest
State: Nevada
State Code: Nv
State CF: 88
DMA: 839
MSA: 29820
City: Las Vegas
Postal Code: 89146
Timezone: GMT-08:00
Area Code: 702
City CF: 77
Latitude: 36.1424
Longitude: -115.22485

Update:
Ok so I went through a VPN in the US I have an ok connection to, got 58ms to google and 61ms to Overwatch server.

It’s definitely a bad routing issue caught up somewhere between me and Nevada or Texas…

That said it’d help if Blizzard can contact these people and get them to fix it :frowning:

How did you do that?

I used NordVPN, it’s working fine for me now. I then selected a VPN server in San Fransisco. It’s really as simple as buy it, install it, and run it and select the server. There’s other options out there I just got a deal on this one and it had good reviews. I should note I get occasional dropped packets tho, not sure if you’d experience that through a VPN too but it’s usually not noticeable.

1 Like