I’m on an iiNet Hybrid Fibre Coaxial connection and have always (without fail) been connected to PSE1 for more than a month now. It’s taken me 3 or 4 days to even find this thread to post on. Tech support has pleasant and useless, in equal measures. No point in providing pathpings to US servers for an issue like this!
Hey there Nerkeley,
I ran a report on the ISP and was unable to verify any issues. Most of their users range between 50-60 latency in Overwatch. Though I do notice the account’s connection is averaging between 100-150. This is very abnormal for the ISP / local area so I’m thinking we should try the following:
- Power Cycle the network by leaving any network devices unplugged for 15 minutes before rebooting them.
- Contact the ISP and ask about “firmware” updates.
- Check the computer for the quoted software:
Hope the info helps. Cheers!
Shut down my router and all devices over Christmas, so off for a number of days.
No firmware for the cable modem I run and absolutely no “network optimisation” crap on my machines.
The problem is that I always, without fail, 100% only ever connect to SEA1, and I’m in Victoria, less than 1000 km from Sydney. Happy to try anything else - 20 years IT desktop, network and server support, so go your hardest!
Hello Kaldraydis,
How can I sort this issue, if Im experiencing that exact same issue as Nerkeley, but on PS4?
I live in Victoria also, and for around 1.5 months, Ive been put on Euro / Indian servers EVERY game! My ping has always been 20 for the last 3 years, but now I average between 150-200. Every game! It only happens on Overwatch, my internet runs around 300Mbps. Constant.
What can I do??
Hey there Jester,
Troubleshooting for Console is a bit more limited. I’d start by power cycling both the PS4 device as well as the home network. I’d also ensure the connection is wired directly to the router/modem (depending on your network setup).
I have also seen some console users change their DNS but that’s not something we can technically suggest doing since that can cause other issues depending on how it’s done and to what DNS it’s changed to. Users I see doing this typically use Google’s public one.
5 reboots, still always connected to SEA1 in practice, skirmish, QP and all arcade modes. Any chance I can get the IP addresses used for the Sydney server so I can troubleshoot with my ISP?
Righteo - I’m done. Gunna go play a game where lousey connectivity stops determining if you are good or bad.
Tech support told me they cant help (read not empowered to give a toss) and forums are just a sop to try and make people feel better. Blizzard is the perfect example of too big to give a poop anymore as customers no longer matter.
It should be 103.4.115.248
When you asked for this info, their forum staff (for Americas & Oceania) was off the clock for a few hours already.
Tried three different IP geolocation tools and they all tell me that IP address is located in Singapore. Any other suggestions?
That IP is 100% located in Australia. Sydney to be precise.
The “geolocation” information you are looking up is often wrong. It simply shows you where the IP block (in this case 103.4.114.0 - 103.4.115.255) is registered. There’s no fool proof way of reliably telling where an IP is located based on that. The best way is to do a traceroute to it. I can tell you for sure that IP address is in Sydney. When I traceroute it from home I go through a bunch of Sydney servers to get there and the latency is low enough that I can deduce its location.
My trace route goes a bit funny as soon as it hits the Blizzard servers:
Tracing route to 103.4.115.248 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 24 ms 172.23.0.1
3 12 ms 12 ms 12 ms nme-sot-dry-wgw1-be-80-455.tpgi.com.au [203.219.106.201]
4 12 ms 14 ms 12 ms bu300.mflinbrdr11.aapt.ne*.au [203.219.107.202]
5 13 ms 25 ms 11 ms Bundle-Ether19.lon-edge901.melbourne.telstra.ne* [139.130.41.105]
6 12 ms 12 ms 14 ms bundle-ether10.exi-core10.melbourne.telstra.ne* [203.50.11.109]
7 24 ms 24 ms 52 ms bundle-ether12.chw-core10.sydney.telstra.ne* [203.50.11.124]
8 32 ms 24 ms 23 ms bundle-ether1.oxf-gw11.sydney.telstra.ne* [203.50.6.93]
9 23 ms 31 ms 22 ms bundle-ether2.oxf-gw10.sydney.telstra.ne* [203.50.6.94]
10 24 ms 34 ms 24 ms bundle-ether1.sydo-core04.sydney.reach.c* [203.50.13.94]
11 23 ms 22 ms 21 ms i-91.sydo10.telstraglobal.ne* [202.84.222.198]
12 25 ms 24 ms 25 ms unknown.telstraglobal.ne* [210.176.152.33]
13 26 ms 23 ms 25 ms et-0-0-48-br01-eqsy4.as57976.ne* [137.221.85.33]
14 259 ms 168 ms 157 ms et-0-0-0-pe01-eqsy4.as57976.ne* [137.221.85.67]
15 156 ms 157 ms 168 ms 137.221.66.145
16 159 ms 159 ms 169 ms 103.4.115.248
Trace complete.
Hi Kaldrayis,
I have power cycled both the PS4 and the Modem. I bought a brand new modem and router 2 weeks ago ($500), in an attempt to fix this issue. Which began nearly 2 months ago now…
I average around 300Mbps download, but yet my ping is always 200, and all my other games run perfectly on my console. I have attempted multiple DNS options as well, all to no avail.
Overwatch is literally the only thing thats left to fix with this issue, I assure you I have tried everything I can. I’m still being put in Indian server games 100% of the time, without fail. I am from Melbourne for the record.
Please advise on next steps, and I’ll happily look in to it.
Until then, could someone from Blizzard maybe get in touch with me via email to sort this issue out further.
Kind Regards.
Playing with an Aussie friend, connected to SYD1 and getting 180 pings. WTF?
JesteR,
You’re also near Nerkeley. Can you run a similar test for us? We’ll need you to grab winMTR and run it using this IP address when things are bad:
103.4.115.248
Nerkeley,
About how long have you been having this latency increase? If you can have your friend run a test as well and post the results here it’ll help us see if you’re both having the same issue. The previous things we were looking into primarily related to a known bad cable. In your case, we’ve got new behavior. This is the first test in this thread with this likely throttling, but it definitely seems to be close by us. We’ll need to see if anybody else is having similar issues to see why it seems normal from our telemetry for most, but not you.
Hi Drak,
Not sure exactly how long the issue has been occurring. Definitely since at least a week before Christmas, but maybe 2 or 3 weeks prior?
Last night, when my ping was 180, my (Aussie) mate was sitting at his usual latency of ~35ms. I suspect I only got into the game on that server because he was there. Server IP address was 37.244.42.91. I left at that point and ran some tests. I could neither ping nor complete a trace route to that address. Nor can I this morning.
C:\Users\Joe>tracert 37.244.42.91
Tracing route to 37.244.42.91 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 9 ms 6 ms 172.23.0.1
3 12 ms 12 ms 12 ms nme-sot-dry-wgw1-be-80-455.tpgi.c0#.au [203.219.106.201]
4 12 ms 11 ms 12 ms bu300.mflinbrdr11.aapt.n37.au [203.219.107.202]
5 11 ms 12 ms 12 ms Bundle-Ether19.lon-edge901.melbourne.telstra.n37 [139.130.41.105]
6 13 ms 12 ms 12 ms bundle-ether10.exi-core10.melbourne.telstra.n37 [203.50.11.109]
7 22 ms 24 ms 22 ms bundle-ether12.chw-core10.sydney.telstra.n37 [203.50.11.124]
8 24 ms 23 ms 23 ms bundle-ether1.oxf-gw11.sydney.telstra.n37 [203.50.6.93]
9 24 ms 22 ms 36 ms bundle-ether2.oxf-gw10.sydney.telstra.n37 [203.50.6.94]
10 26 ms 29 ms 23 ms bundle-ether1.sydo-core04.sydney.reach.c0# [203.50.13.94]
11 21 ms 23 ms 22 ms i-91.sydo10.telstraglobal.n37 [202.84.222.198]
12 47 ms 24 ms 29 ms unknown.telstraglobal.n37 [210.176.152.33]
13 22 ms 21 ms 21 ms 137.221.85.35
14 154 ms 154 ms 156 ms et-0-0-0-pe04-eqsy4.as57976.n37 [137.221.85.73]
15 * * * Request timed out.
and they all time out from there.
Nerkeley,
Based on the fact that both tests run aground of issues at nearly the same location, you’re probably going to be able to work around this by running a VPN client. It may not be as low latency as you’re used to, but it should get you closer to normal. There are free options out there if you don’t already have a paid VPN you subscribe to and trust.
I’ll keep an eye out for more contacts of this nature in your area, but for the time being I strongly suspect we’re looking at a totally different issue than the scope of what this thread was covering earlier. If that turns out to be the case, we’ll splinter y’all off into your own thread and get you a new title for it to see if we can get more reports in.
Hello Drakuloth,
Im running on a PS4 so I’m not sure I am able to run those tests you were after?
I have been having this Ping issue for about 1 - 2 months now.
Please let me know if there’s anything else I can do to help speed this process up. I haven’t even had anyone that can speak English in my games for a while now, so even the comms in game are ruined as well. The whole experience is frustrating. My PS4 thinks its in Asia/Euro region for some reason, with OW…
For the record Im not sure I can use a VPN client like suggested above.
Can we please have a new thread then? using a VPN as a work around simply ignores the actual issue of a network routing fail.
Nope - i’m done. The unplayability of the game, the lack of support from support and the hoops to jump through (seriously? run a vpn just to play a game???) mean I’m now uninstalling the game. Been a good year or so …
Nerkeley,
If that’s how you’d prefer to handle the issue, I entirely understand. I know you want to be able to hop in game and play and this makes that a frustrating process. Given everything we’ve seen in the thread lately, I’ve moved Jester and yourself to your own thread to see if we can find more insight. Feel free to follow if you’d like to keep an eye on things instead of working around the issue with a VPN.
Jester,
With you being on a console (Sorry I missed that tidbit earlier) it’d be difficult for you to run the test unless you also have a PC you can run it on. If you happen to have a PC in your house and can run the test, the info may be helpful for us.