Not shocking that there’s connection problems relating to this game. Seems every other person is either complaining and saying they’re quitting Overwatch, or trying to get help with the ever increasing ping. Not quite sure how or why specifically Overwatch seems to steadily have ping increases with each patch, but I’m not really surprised anymore. Which is sad in itself.
I was recommended by Blizzard support to create this thread to help track the issue at hand that they called the “Equinix” issue. Supposedly only affects certain ISPs. That’s all they told me, I guess its been an issue that keeps coming and going according to them. I’ve tested this across two seperate ISPs and 3 different PCs. All have identical results.
Symptoms:
- Double animations
- Significant shot delay
- Phantom hitmarkers
Looking Glass
TRACEROUTE:
traceroute to 199.126.69.84 (199.126.69.84), 15 hops max, 60 byte packets
1 10.56.100.81 (10.56.100.81) 0.346 ms 0.334 ms 0.324 ms
2 37.244.22.131 (37.244.22.131) 0.638 ms 0.660 ms 0.736 ms
3 24.105.30.158 (24.105.30.158) 1.101 ms 1.139 ms 1.213 ms
4 137.221.66.4 (137.221.66.4) 1.850 ms 1.934 ms 2.037 ms
5 137.221.68.72 (137.221.68.72) 1.554 ms 1.558 ms 1.558 ms
6 137.221.65.21 (137.221.65.21) 33.052 ms 32.084 ms 33.122 ms
7 137.221.65.49 (137.221.65.49) 49.014 ms 48.941 ms 48.937 ms
8 137.221.65.44 (137.221.65.44) 61.073 ms 61.028 ms 61.015 ms
9 137.221.65.15 (137.221.65.15) 66.731 ms 66.742 ms 66.742 ms
10 137.221.71.32 (137.221.71.32) 67.403 ms 68.775 ms 68.779 ms
11 TELUS.com (206.130.10.58) 66.457 ms 66.544 ms 66.341 ms
12 * * *
13 199.126.69.84 (199.126.69.84) 95.590 ms 94.944 ms 95.484 ms
14 199.126.69.84 (199.126.69.84) 95.910 ms 95.894 ms 96.169 ms
05/06/2018 03:41:28 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=117 time=96.3 ms
64 bytes from 199.126.69.84: icmp_seq=2 ttl=117 time=96.2 ms
64 bytes from 199.126.69.84: icmp_seq=3 ttl=117 time=96.2 ms
64 bytes from 199.126.69.84: icmp_seq=4 ttl=117 time=96.3 ms
--- 199.126.69.84 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 96.230/96.305/96.369/0.052 ms
05/06/2018 03:41:28 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=118 time=77.4 ms
64 bytes from 199.126.69.84: icmp_seq=2 ttl=118 time=77.6 ms
64 bytes from 199.126.69.84: icmp_seq=3 ttl=118 time=77.8 ms
64 bytes from 199.126.69.84: icmp_seq=4 ttl=118 time=77.6 ms
--- 199.126.69.84 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 77.466/77.652/77.819/0.233 ms
05/06/2018 03:41:28 UTC
--------------------
TRACEROUTE:
traceroute to 199.126.69.84 (199.126.69.84), 15 hops max, 60 byte packets
1 10.57.68.13 (10.57.68.13) 1.593 ms 1.572 ms 1.567 ms
2 37.244.23.2 (37.244.23.2) 1.565 ms 1.564 ms 1.563 ms
3 24.105.62.146 (24.105.62.146) 2.418 ms 2.418 ms 2.416 ms
4 137.221.66.8 (137.221.66.8) 2.392 ms 2.410 ms 2.410 ms
5 137.221.69.66 (137.221.69.66) 223.578 ms 223.594 ms 223.596 ms
6 137.221.65.12 (137.221.65.12) 19.554 ms 22.156 ms 22.113 ms
7 137.221.65.15 (137.221.65.15) 27.975 ms 25.524 ms 25.505 ms
8 137.221.71.32 (137.221.71.32) 24.792 ms 24.878 ms 24.740 ms
9 TELUS.com (206.130.10.58) 24.808 ms 24.672 ms 24.650 ms
10 * * *
11 199.126.69.84 (199.126.69.84) 76.682 ms 76.528 ms 76.158 ms
12 199.126.69.84 (199.126.69.84) 77.329 ms 76.742 ms 76.939 ms
05/06/2018 03:41:28 UTC
--------------------
MTR:
Start: Tue Jun 5 03:41:28 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.56.70.56 0.0% 10 0.3 0.3 0.2 0.6 0.0
2.|-- 37.244.22.3 0.0% 10 0.7 0.6 0.5 0.7 0.0
3.|-- 24.105.30.158 0.0% 10 1.9 1.4 0.8 3.0 0.5
4.|-- 137.221.66.0 0.0% 10 1.8 1.6 1.5 1.8 0.0
5.|-- 137.221.68.70 0.0% 10 1.4 13.5 1.3 61.4 21.1
6.|-- 137.221.65.21 0.0% 10 32.0 32.7 32.0 35.0 0.7
7.|-- 137.221.65.49 0.0% 10 50.0 50.2 49.9 51.6 0.3
8.|-- 137.221.65.44 0.0% 10 921.1 192.4 62.0 921.1 276.0
9.|-- 137.221.65.15 0.0% 10 222.3 110.1 67.5 263.3 73.0
10.|-- 137.221.71.32 0.0% 10 67.5 67.8 67.3 70.5 0.9
11.|-- TELUS.com 0.0% 10 66.6 67.7 66.5 77.6 3.4
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- 199.126.69.84 0.0% 10 95.7 95.7 95.3 96.0 0.0
05/06/2018 03:41:28 UTC
--------------------
MTR:
Start: Tue Jun 5 03:41:28 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.57.68.13 0.0% 10 0.4 0.4 0.2 0.8 0.0
2.|-- 37.244.23.2 0.0% 10 0.8 0.8 0.5 1.8 0.3
3.|-- 24.105.62.146 0.0% 10 2.5 1.9 1.3 2.6 0.0
4.|-- 137.221.66.8 0.0% 10 2.3 2.4 1.9 3.4 0.5
5.|-- 137.221.69.66 0.0% 10 324.5 250.0 151.3 354.8 78.2
6.|-- 137.221.65.12 0.0% 10 650.8 92.0 19.2 650.8 198.5
7.|-- 137.221.65.15 0.0% 10 157.8 60.5 25.1 220.7 69.7
8.|-- 137.221.71.32 0.0% 10 25.4 26.2 24.5 39.7 4.7
9.|-- TELUS.com 0.0% 10 26.1 25.1 24.6 26.4 0.6
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 199.126.69.84 0.0% 10 77.2 77.3 76.8 77.7 0.0
05/06/2018 03:41:28 UTC
--------------------
WINMTR
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 309 | 309 | 0 | 0 | 6 | 1 |
| 10.145.148.1 - 0 | 309 | 309 | 4 | 8 | 32 | 5 |
| STTLWAWBCI01.bb.telus.com - 0 | 309 | 309 | 21 | 22 | 41 | 23 |
| six.blizzardonline.net - 0 | 309 | 309 | 21 | 22 | 48 | 22 |
| ae1-br01-eqse2.blizzardonline.net - 0 | 309 | 309 | 25 | 26 | 152 | 26 |
| No response from host - 100 | 63 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 63 | 0 | 0 | 0 | 0 | 0 |
| be2-pe02-eqla1.blizzardonline.net - 0 | 309 | 309 | 91 | 92 | 105 | 92 |
| 24.105.30.129 - 0 | 309 | 309 | 91 | 92 | 102 | 93 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Any help would be appreciated. For me these issues have been going on forever, and as of today my ping is over 100ms along with ping spikes of 150 plus happening in the background. Even when my ping is 55ms (which is the norm for one of my ISPs) I still get double animations happening frequently. This problem to say the least is incredibly frustrating and defeats the purpose of a competitive game.
From what I was told its some sort of routing/packet issue but I’m not clear on the details. All I know is Blizzard support told me right away that they were at fault for this one. Especially considering all my testing comes out crystal clear until hitting the blizzard hops. If you need anymore testing from me let me know and I’ll find the time to do it.