I’ve played Overwatch since 2016 and have had a constant ping (ms) of 35-40 since then. Until about a month ago I’ve had nothing but 90-120ms every game. I live in South Australia and I’ve asked many other South Australian PC and Console players if theyve had the same issue. They all confirmed that they have the exact same problem and that it must be Blizzard’s fault (all our internet speeds are fine n fast n dandy). Overwatch Team, there has to be a fault on your end in regards to networking because this game is frustratingly unplayable to me and this needs to be fixed and acknowledged. Thank you. Here is a WinTMR.
same, TPG fibre here. I left OW for a few weeks to play division 2, came back a few days ago, i’ve gone from my old ping which was always 40-50 constant, to now pinging 80-90 constant.
If there’s still issues once maintenance starts we’d like to start gathering some info on this. Once we have enough we’ll be able to have it sent up to be looked into. I’ve listed what we’ll want below!
What server are you being placed on? This can be found in the netgraph by pressing Ctrl + Shift + N.
What ISP are you on?
A WinMTR test ran using the IP address in the netgraph. We’ll want to run this for a full match before exporting the results. When posting results, please encase them in a set of ``` (on the tilde key) like so:
```
Link
```
Wow and i thought i was the only one. Ive just spent a week with tpg doing tests from their end and my end and doing all the blizzard tests and apparently everything is normal… but i know that aint right. I was getting 38-48 ms and now 70-90 all the time. South Australian here also. Tpg tells me that up to the 7th hop which they say they control is all fine. My issue is on the 12th hop every time. I believe thats the sydney ip? Anyway here is one of many test results.
I’m being placed on this server: [pse2] 13.211.236.227
My ISP in South Australia is called Internode (iiNet is the Parent Organization).
These are the WinMTR results from a Quickplay Match with previously stated 13.211.236.227
Yeah ive been having this issue for 2 weeks or so now i contacted my isp they did tests etc like u guys said and there was nothing wrong on there end apparently im also with TPG in Adelaide. Trying to play ranked with 90-115 ping is really hard especially on hitscan which is frustrating. I use to get constant 45-50 ping forever now its 90-115 only on overwatch aswell. Couldnt post this earlier some forum bug made it so i couldn’t login and had to remove parental controls. Did all the blizzard article network issues troubleshooting its still the same its something on there end with the server etc please look into a fix i want to play but there’s no point with the high latency.
Cheers
This issue also still occurring after the maintenance update it did nothing to fix it, its exactly the same as the last 2 weeks or so for me. I’m on pse2 13.236.208
Ye most people had the 2 week holiday break and overwatch has been high latency for the full time i wanted to play a bit before i go back to study annoying can u guys please look into this its making the game unplayable for some TPG users at least before the season ends or something cheers.
[Zhyxen] can u guys look into this problem i made a support ticket and he said contact the provider again with overwatch server tracert WinMTR im gonna do that soon can u look in more depth into the problem aswell please
All day today i have had 100 extra ping and through all my attempts it hasn’t gone back to normal. Overwatch is the only game that is doing this for me.
I WANT AN EXPLANATION ON WHY I COULDN’T EVEN GO INTO THE GAME BUT THE BLIZZARD IS WORKING FINE.
TRACEROUTE:
traceroute to 14.192.208.152 (14.192.208.152), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.719 ms 2.716 ms 2.714 ms Blizzard(24.105.18.3) 40.271 ms 40.292 ms 40.363 ms
3 137.221.105.16 (137.221.105.16) 3.392 ms 3.394 ms 3.419 ms
4 137.221.66.22 (137.221.66.22) 3.355 ms 3.384 ms 3.387 ms
5 137.221.83.68 (137.221.83.68) 191.064 ms 191.079 ms 191.252 ms
6 137.221.65.68 (137.221.65.68) 187.527 ms 185.011 ms 184.998 ms
7 137.221.65.57 (137.221.65.57) 185.072 ms 185.062 ms 185.060 ms
8 137.221.65.127 (137.221.65.127) 185.375 ms 185.395 ms 185.379 ms
9 137.221.87.32 (137.221.87.32) 184.812 ms 184.922 ms 184.897 ms
10 * * *
11 * * *
12 * * *
13 58.71.241.106 (58.71.241.106) 197.722 ms 197.740 ms 196.769 ms
14 * * *
15 * * *
TRACEROUTE:
traceroute to 14.192.208.152 (14.192.208.152), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.268 ms 0.256 ms 0.256 ms Blizzard(24.105.18.3) 0.588 ms 0.705 ms 0.850 ms
3 137.221.105.16 (137.221.105.16) 0.516 ms 0.608 ms 0.719 ms
4 137.221.66.22 (137.221.66.22) 0.615 ms 0.638 ms 0.645 ms
5 137.221.83.68 (137.221.83.68) 185.008 ms 185.033 ms 185.045 ms
6 137.221.65.68 (137.221.65.68) 184.836 ms 184.996 ms 184.992 ms
7 137.221.65.57 (137.221.65.57) 185.133 ms 185.158 ms 184.833 ms
8 137.221.65.127 (137.221.65.127) 251.276 ms 251.348 ms 251.710 ms
9 137.221.87.32 (137.221.87.32) 184.924 ms 184.953 ms 184.957 ms
10 * * *
11 * * *
12 * * *
13 58.71.241.106 (58.71.241.106) 195.136 ms 195.047 ms 195.115 ms
14 * * *
15 * * *
27/04/2019 17:36:19 UTC
TRACEROUTE:
traceroute to 14.192.208.152 (14.192.208.152), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.606 ms 0.623 ms 0.628 ms Blizzard(24.105.18.3) 1.186 ms 1.233 ms 1.242 ms
3 137.221.105.16 (137.221.105.16) 0.996 ms 1.044 ms 1.199 ms
4 137.221.66.22 (137.221.66.22) 1.016 ms 1.040 ms 1.050 ms
5 137.221.83.68 (137.221.83.68) 185.571 ms 185.614 ms 185.623 ms
6 137.221.65.68 (137.221.65.68) 217.375 ms 214.338 ms 214.315 ms
7 137.221.65.57 (137.221.65.57) 250.104 ms 250.106 ms 250.112 ms
8 137.221.65.127 (137.221.65.127) 185.001 ms 185.038 ms 185.045 ms
9 137.221.87.32 (137.221.87.32) 184.842 ms 184.866 ms 184.998 ms
10 * * *
11 * * *
12 * * *
13 58.71.241.106 (58.71.241.106) 221.552 ms 195.115 ms 195.274 ms
14 * * *
15 * * *
27/04/2019 17:36:19 UTC
PING:
PING 14.192.208.152 (14.192.208.152) 56(84) bytes of data.
For folks on iiNet/Internode, can you check out this thread for me? We need some information there. I’m checking some of your other ISPs to see if you’re also impacted, but for the smaller ISPs I may not be able to see enough data to confirm it.
after 2 weeks of trouble shooting with tpg and what felt like their whole technical support team from support reps to engineers, they were unsuccessful in identifying the issue. i told them a friend of mine had no issue over at Aussie Broadband and then terminated my account with TPG and switched providers. i only wish i did it sooner, also im back to my normal latency (44ms) again with no issues.