I’ve been unable to connect to the Aus servers since the start of the season, I keep being placed in US West (assumed) as I have around 160-200ms. I was able to connect normally the day before the season started.
Is there an ongoing issue with the servers in Australia?
Hi,
I was able to connect and start a game using the Australia servers… the ping for me was around 250 ms (I am in Eastern Canada) but it did work.
You can bypass the automatic server pool allocation by modifying the Settings of the Battle.Net Desktop App. Click on the blue Battle.Net logo on the launcher and select Settings… then Game Settings, and Diablo III. Ensure that « Additional command line arguments » is selected and that « OnlineService.Matchmaking.ServerPool=AU1 » appears… as shown below:
I forgot to mention it in the original post but I’ve already tried the command line and it still doesn’t work. Either I am connecting to the server but the ping is high for unknown reason or I’m connecting the US west.
OK – you should be connecting to the Australia server if you are using the ServerPool argument.
There is some troubleshooting that you can try here:
If the high latency is still present, the next step would be some connection test and seeing if there are issues.
Follow the steps here:
and use the Australia IP Address.
Start the WinMTR, launch the game, play for 5 to 10 minutes… then import the WinMTR.txt file in your reply. You will likely need to put the WinMTR data between 2 lines of 4 tildes, as in:
~~~~
Paste the contents of your WinMTR.txt file here.
~~~~An alternative is to submit a ticket… use this link https://us.battle.net/support/en/help/contact/1397/ticket and fill the ticket with as much information is available. Attach the WinMTR.txt file to your ticket.
I’ve done some general speed tests and the results all come back normal; low ping and normal speeds. All my other games seem to running normally as well.
Another odd thing I noticed is even though the ping display for D3 shows ~160-230ping the game plays and runs as if the ping is low.
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 635 | 635 | 1 | 3 | 43 | 4 |
| 101.113.144.1 - 1 | 632 | 631 | 2 | 9 | 121 | 6 |
| 10.246.69.250 - 1 | 632 | 631 | 2 | 9 | 125 | 14 |
| 203-220-16-133.tpgi.com.au - 1 | 632 | 631 | 2 | 10 | 111 | 6 |
| syd-apt-ros-wgw2-be90.tpgi.com.au - 11 | 448 | 400 | 2 | 10 | 110 | 7 |
| syd-apt-ros-int1-hu0-3-0-2.tpgi.com.au - 1 | 632 | 631 | 3 | 15 | 111 | 9 |
I’m also in the process of reinstalling the game. Originally, around 5hrs ago, the high ping was noticeable thus the reason I made the post BUT when playing just recently the displayed ingame ping didn’t really match the ping of the gameplay.
Did you find a fix for this. I am having the same issue
Nothing at the moment, I’m currently talking with support and will update you if I find any fixes.
Thanks, i am also talking to support but they haven’t spoken back to me since yesterday
Just got an update saying that it could be related to Vodafone which is part of the TPG network. If you’re part of either, then that might explain why it’s not connecting. Still no word on a fix yet though.
Howdy y’all,
We have received similar reports from other players using Vodafone and we have been investigating these reports. Unfortunately since this appears to be due to something on the route before the game servers, there isn’t much we can do from our side. However, we are collecting data to send to Vodafone which may help them resolve these issues.
In the mean time, you could try testing another ISP network such as a cellular hotspot or a free VPN which may help route you around the problem.
Just chiming in to say I’m having the same issues on Vodafone.
Approx 160ms pretty constant (never below that) the game noticeably runs at the higher latency so it’s not just an incorrect reading.
Switched to a hotspot (Aldi/Telstra) and Ping was down around 30 and inputs felt instant.
Glad that im not the only one having this issue. I noticed this last weekend and im surprised that it hasnt been fixed yet. Its starting to get annoying.
Has there been any further updates form Voda/TPG?