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.
what does the netgraph look like if you let it run?
I too am having problems. I’m connecting to pse2 also. ~160 ping 
1 Like
also having the same random issue
1 Like
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 * * *
27/04/2019 17:31:39 UTC
MTR:
Start: Sat Apr 27 17:31:40 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 0.6 0.5 0.8 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.6 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.5 0.6 0.5 0.7 0.0
5.|-- 137.221.83.68 0.0% 10 184.9 193.6 184.9 269.7 26.7
6.|-- 137.221.65.68 0.0% 10 184.7 191.3 184.7 221.4 13.4
7.|-- 137.221.65.57 0.0% 10 184.9 188.7 184.9 221.1 11.4
8.|-- 137.221.65.127 0.0% 10 184.9 185.3 184.9 187.3 0.5
9.|-- 137.221.87.32 0.0% 10 184.7 184.9 184.7 185.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- 58.71.241.106 0.0% 10 195.5 195.9 194.9 202.6 2.2
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27/04/2019 17:31:39 UTC
REPLY ASAP.
Overwatch Looking Glass RESULT
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.
— 14.192.208.152 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3006ms
27/04/2019 17:36:19 UTC
PING:
PING 14.192.208.152 (14.192.208.152) 56(84) bytes of data.
— 14.192.208.152 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
27/04/2019 17:36:20 UTC
MTR:
Start: Sat Apr 27 17:36:19 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.5 0.6 0.5 0.7 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.7 0.5 1.1 0.0
5.|-- 137.221.83.68 0.0% 10 185.0 188.0 184.9 214.5 9.3
6.|-- 137.221.65.68 0.0% 10 185.0 194.7 184.9 251.0 21.2
7.|-- 137.221.65.57 0.0% 10 185.0 186.4 184.9 198.8 4.3
8.|-- 137.221.65.127 0.0% 10 221.3 194.6 184.9 221.3 12.3
9.|-- 137.221.87.32 0.0% 10 184.9 185.0 184.7 185.9 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- 58.71.241.106 0.0% 10 195.5 195.3 195.0 195.5 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27/04/2019 17:36:19 UTC
MTR:
Start: Sat Apr 27 17:36:19 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.5 0.2 2.9 0.7 Blizzard 0.0% 10 0.7 1.3 0.5 5.6 1.5
3.|-- 137.221.105.16 0.0% 10 0.5 0.6 0.5 0.7 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.6 0.5 0.7 0.0
5.|-- 137.221.83.68 0.0% 10 185.0 188.0 185.0 200.5 5.9
6.|-- 137.221.65.68 0.0% 10 184.9 185.0 184.9 185.2 0.0
7.|-- 137.221.65.57 0.0% 10 185.0 199.3 184.9 245.2 23.8
8.|-- 137.221.65.127 0.0% 10 185.0 190.0 184.9 208.5 8.5
9.|-- 137.221.87.32 0.0% 10 184.7 184.8 184.7 184.9 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- 58.71.241.106 0.0% 10 198.1 196.2 195.2 199.6 1.5
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27/04/2019 17:36:19 UTC
I am also having this issue. Constant High ping, normally its 40-50 - Tasmania.
This is @#%%$@
Hey all,
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.
2 Likes
Are you still looking for more examples of this?
I’m with Optus and seeing the same issues as above.
1 Like
This problem is still rampant ive been in contact with tpg for a few weeks they cant find any solution doing tests etc and done a few blizzard support tickets and posted on this thread its frustrating how long it is for people to acknowledge its a problem and to help fix it people just keep hand-balling it off to isp/ game developer. I just want to be able to play the game at a normal ping level not be at a huge disadvantage trying to play ranked. I went from consistently having 45-50 ping to having 90-120 ping for the passed month or so now.
1 Like
Just got off from playing 15 minutes worth of QP and it’s so fkn unplayable. It feels much worse than 90ms, more like 150-170. This is such a joke. Fix your sheit, blizz.
The iiNet/Internode errors I mentioned previously should be resolved. For people on other ISPs (optus, TPG, etc) this information may still be useful. We don’t think there’s an oceanic wide issue anymore, so it’s possible that the problems you’re experiencing are individual ones now. If you can post this information we can check to see if there’s something affecting all of you or if we should move this back to helping you one by one.
Hello. The issue is still ongoing. Internode Customer in Adelaide.
I still have this issue on TPG in Adelaide from a month or so now
1 Like
I just rage quit the game out of frustration. I’m actually about to neck. Issue still not fixed and still not fixed after resetting my router.
1 Like
Valve,
Sorry to hear you’re still having this problem. I checked the data we used to check this last time and it looks like the constant higher than average latency is resolved in most of the regions we were checking. However, it seems more stable. Doing another check it looks like some areas of ANZ may have slight (~10ms) increases in latency during peak hours, but this is normal internet behavior.
If you’re having an individual issue and still want to troubleshoot, you should create your own thread as I mentioned previously. For now I’m locking this thread to prevent people from mixing up the problems they’re seeing with this older issue.