After the 14th of April Overwatch update I have high ping when playing in the morning.
I live in the Netherlands and when I play in the morning(CET) I sometimes get games where I have 140ms ping instead of my usual 18ms. Also all the players then speak Arabian instead of English which leads me to believe I play via the middle eastern data center.
Is there any way of me disabling this? It has lost me games since I’m not used to playing with that ping not even talking about the language issues. Even when I play on NA servers my ping is lower!
EDIT: Could you guys with the same issue respond here? So we have everything at one place and not all over the places. Thanks!
Same issue here. And I’m also from The Netherlands and Tech Support is nowhere, I lost so much SR due lags they caused to me.
I’m not used to play with 200ms, It’s like we have no servers in UK, Netherlands, France & Germany, NO they just decided to say “ga de pot op” enjoy the lags and deal with it.
I reported it here and multiple peole. (I guess this is not evidence enough to start working on a fix.)
Blizzard has history of shooting themselves in the foot .how many times will you torture us with your stupidities ? In future nobody will touch your games .
I had this happen to me just now. Find the requested information below.
When this occurs are you in a pre-made party? Are any of them from ME?
-Solo queue
Date & Time of Problem
-1st of june @ 14:15-14:30 CET
Your ISP Name
-XS4ALL
Your Connection Type
-fiber optic 500Mbit
Your Looking Glass report
Looking Glass report
-TRACEROUTE:
traceroute to x.x.x.x (x.x.x.x), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.350 ms 0.340 ms 0.339 ms
2 37.244.24.3 (37.244.24.3) 1.506 ms 1.609 ms 1.673 ms
3 Blizzard Blizzard 1.167 ms 1.233 ms 1.291 ms
4 137.221.66.40 (137.221.66.40) 0.615 ms 0.645 ms 0.649 ms
5 * * *
6 137.221.78.34 (137.221.78.34) 1.049 ms 1.290 ms 1.256 ms
7 ams-ix.tc2.xs4all. net (80.249.208.166) 28.359 ms 28.376 ms 28.376 ms
8 0.et-8-1-0.xr4.1d12.xs4all. net (194.109.5.4) 1.480 ms 1.488 ms 1.533 ms
9 0.ae0.dr16.d12.xs4all. net (194.109.7.142) 1.374 ms 1.391 ms 1.342 ms
10 x-x-x-x.ip.xs4all.nl (x.x.x.x) 3.304 ms 3.443 ms 3.444 ms
01/06/2020 12:27:55 UTC
PING:
PING x.x.x.x (x.x.x.x) 56(84) bytes of data.
64 bytes from x.x.x.x: icmp_seq=1 ttl=55 time=3.33 ms
64 bytes from x.x.x.x: icmp_seq=2 ttl=55 time=3.29 ms
— x.x.x.x ping statistics —
4 packets transmitted, 2 received, 50% packet loss, time 3000ms
rtt min/avg/max/mdev = 3.292/3.313/3.335/0.061 ms
Your Traceroute
This is the tracerout for the IP adress I found I was playing on in Overwatch via ctrl+shift+n
Traceroute
Tracing route to ec2-157-175-68-244.me-south-1.compute.amazonaws. com [157.175.68.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms XXXXXX
2 <1 ms <1 ms <1 ms XXXXXX
3 2 ms 2 ms 2 ms x.x.x.xs4all. net [x.x.x.x]
4 2 ms 2 ms 2 ms 0.ae26.xr4.3d12.xs4all. net [194.109.7.141]
5 3 ms 2 ms 2 ms 0.et-7-1-0.xr1.tc2.xs4all. net [194.109.5.5]
6 5 ms 3 ms 2 ms amazon.xs4all. net [194.109.7.242]
7 4 ms 3 ms 3 ms 54.239.114.182
8 3 ms 4 ms 3 ms 54.239.114.55
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 131 ms 130 ms 131 ms 150.222.240.213
15 136 ms 130 ms 131 ms 54.239.43.248
16 * * * Request timed out.
17 * * * Request timed out.
18 132 ms 131 ms 132 ms 54.239.46.152
19 131 ms 130 ms 131 ms 52.93.68.153
20 131 ms 131 ms 131 ms 52.93.130.190
21 * * * Request timed out.
22 130 ms 130 ms 130 ms 52.93.225.126
23 131 ms 131 ms 130 ms 52.93.225.137
24 130 ms 133 ms 131 ms 52.93.225.136
25 131 ms 131 ms 130 ms 52.93.225.133
26 131 ms 131 ms 130 ms 52.93.227.50
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
It still happens to me 1 in 10 games aprox. And I usually soloqueue.
Hope this helps and please let me know if you find something.