One of the first results when googling for recent posts about Overwatch having latency issues.
I’ve been playing a lot lately and it was fine until a few days ago (maybe the recent event and a patch?).
Like Nagah, all other software so far confirms no problem with network. Both hardwired and wireless. Even used my phone as a hotspot which had 50/30, and still was horribly lagging.
I’m in Europe and connecting to the EU servers, but my account is US (and obviously speak English) so figured I would post here as well.
The looking-glass tool (with Europe region selected, and Overwatch as the service) showed the same 100% packet loss when trying to ping me etc, and traceroutes failed on hop 10.
Hmm, I think there might be a routing issue somewhere in the EU. I am connecting from the US, and confirmed that I can connect/authenticate/play on the US servers, EU servers, and Asia servers. Was there any info on the EU forum? We don’t generally see news about that region posted here.
I"ll hit up the EU forum as well, but the NA forum had the same issue for me (I think in relation to the recent patch). Other players on the EU in general chat agreed with me, but maybe I have to start a post there, as there isn’t much there, but people in chat all tend to agree.
I do see a long post about ‘ME Server hell’ and people putting in literal IP blocks to avoid those servers. It could also explain why sometimes I’m fine, and other times I’m not (even after checking my router logs, monitoring system performance etc).
Can you add a WinMTR here? Just because I’m curious.
Sure. I will state I blocked the same IP range at my router and my performance has been amazing (i.e. normal). Earlier I played 1 QP game and it had the same rubber banding etc. No computer shutdown or anything, just blocked the IP range for ‘ME Servers’. I do not normally take random ‘internet’ advice, but I know blocking IP ranges won’t matter (though these are owned by AWS and I wasn’t aware Blizzard hosts on their datacenters but it would make sense I guess, has to be one of the big providers.)
TRACEROUTE:
traceroute to 217.224.80.125 (217.224.80.125), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.321 ms 0.317 ms 0.317 ms
2 37.244.24.131 (37.244.24.131) 3.529 ms 3.574 ms 3.634 ms
3 Blizzard Blizzard 1.434 ms 1.442 ms 1.482 ms
4 137.221.66.46 (137.221.66.46) 0.882 ms 0.900 ms 0.901 ms
5 * * *
6 137.221.78.34 (137.221.78.34) 1.092 ms 1.116 ms 1.095 ms
7 80.156.162.85 (80.156.162.85) 1.320 ms 1.327 ms 1.325 ms
8 87.137.245.245 (87.137.245.245) 10.188 ms 10.194 ms 10.223 ms
9 87.137.245.245 (87.137.245.245) 9.974 ms 9.981 ms 9.934 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
19/09/2020 17:39:57 UTC
PING:
PING 217.224.80.125 (217.224.80.125) 56(84) bytes of data.
— 217.224.80.125 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
19/09/2020 17:39:57 UTC
MTR:
Start: Sat Sep 19 17:39:58 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19/09/2020 17:39:57 UTC
Same 100% packet loss which I mean, if your MTR tool from looking glass tries to ping me, that makes sense as my home system won’t respond to pings. Did you want me to MTR with the 3rd party tool?
Yeah, follow the instructions on the page I linked.