Been having this issue as well for a few hours. I have just changed my region to Singapore (same latency for me in Perth) and worked right away. Would prefer to play with others from Australia though.
I’m getting absolutely horrendous groups in the singapore region… no idea why, but people who literally have no idea. Need to be back on oz servers.
I switched to WUS to get my daily done. Lag was pretty appalling - 260ms or so as I recall. Full teams which made for a change - I often find myself playing solo AI, but little communication and a single lane rush focus. Have to see how things are tomorrow.
Every time I attempt to find a quick match and queue to search, it starts searching, then pops up with an error. I’ve tried everything I can possibly think of on my end to check for issues, and nothing has worked. Turns out a bunch of other people are experiencing the same issue. When can we expect any form of update on the issue?
1 Like
Does the error say “a problem occurred while connecting to the game”?
That’s what’s happening to me.
Are y’all still running into issues trying to connect? If so we’d like to grab a traceroute test as well as the service provider y’all are on. When posting the traceroute, please format it by encasing it in a set of ~~~ like so:
~~~
Tracert
~~~
While the latency isn’t going to be optimal, see if y’all can connect after changing the Preferred Game Server setting in the Language and Region section in-game.
I can confirm that changing region to anything but australia can find a game its just super laggy.
Thanks for the update! Looks like this is something that we’re currently looking into. We’ll post updates once we get more information!
Sounds good. I am going to sleep then and hopefully its back to working normally tomorrow. Goodluck
The problem isn’t happening to everyone, just when the effected people que for a match and find 9 normal players, they dc and cause all 9 others to be booted from the lobby as well. Most (I dare say, I’m unsure how widespread the problem is) of us has just keep re-queing till we find 9 opponents that don’t have the issue. But for those with the issue I assume you have to wait for Blizzard to do something.
Still an issue today, can’t connect/play on Oceanic server.
Day three of “Error connecting to the game”
Sorry to everyone who gets their queue reset due to me trying to play the game
2 Likes
Here’s a tracert output for you:
C:\Users\New User>tracert 103.4.114.233
Tracing route to 103.4.114.233 over a maximum of 30 hops
1 3 ms 2 ms 3 ms router.asus.com [192.168.1.1]
2 2 ms 2 ms 2 ms HOME_NETWORK_GA [10.1.1.1]
3 18 ms 15 ms 17 ms lo0.bras1.syd7.on.ii.net [150.101.32.14]
4 17 ms 15 ms 17 ms be11.cr2.syd2.on.ii.net [150.101.197.204]
5 16 ms 15 ms 15 ms be-50.cr2.syd7.on.ii.net [150.101.37.12]
6 16 ms 16 ms 16 ms ae6.cr2.syd4.on.ii.net [150.101.41.124]
7 17 ms 17 ms 64 ms 57976.syd.equinix.com [45.127.173.41]
8 17 ms 16 ms 16 ms et-0-0-49-br01-eqsy4.as57976.net [137.221.85.47]
9 18 ms 17 ms 18 ms et-0-0-0-pe01-eqsy4.as57976.net [137.221.85.67]
10 15 ms 16 ms 19 ms 137.221.66.145
11 * * * Request timed out.
12 * * * Request timed out.
That should help.
Tracing route to 103.4.114.233 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 4 ms 3 ms 3 ms 219-88-96-1-vdsl.sparkbb.co.nz [219.88.96.1]
3 * 8 ms 7 ms mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
4 5 ms 7 ms 7 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 5 ms 7 ms 7 ms ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
6 28 ms 27 ms 27 ms xe0-0-8.sebr3.global-gateway.net.nz [122.56.119.126]
7 29 ms 27 ms 27 ms 122.56.119.86
8 30 ms 27 ms 27 ms 57976.syd.equinix.com [45.127.173.41]
9 28 ms 31 ms 31 ms et-0-0-49-br02-eqsy4.as57976.net [137.221.85.49]
10 29 ms 31 ms 31 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.73]
11 29 ms 31 ms 31 ms 137.221.66.147
12 * * * Request timed out.
13 * * * Request timed out.
Game works when on any region that isn’t Oceanic but enduring 180+ latency isn’t worth it…
“Error connecting to the game”
Never seen this error before yesterday, now its all I see when trying to join a game in Oceania.
Can confirm when I went to try a different region, it worked perfectly. Obviously had latency issues but queue worked first time. Also, here’s a trace route to the HoTS Aus Server.
Tracing route to 103.4.114.233 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 3 ms 3 ms 125-239-12-1.jetstream.xtra.co.nz [125.239.12.1]
3 * * * Request timed out.
4 6 ms 7 ms 7 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 4 ms 7 ms 7 ms ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
6 30 ms 31 ms 31 ms xe7-0-2.sgbr3.global-gateway.net.nz [202.50.232.10]
7 30 ms 31 ms 31 ms ae7-10.sebr4.global-gateway.net.nz
[122.56.127.214]
8 29 ms 41 ms 42 ms 57976.syd.equinix.com [45.127.173.41]
9 50 ms 31 ms 31 ms et-0-0-49-br02-eqsy4.as57976.net [137.221.85.49]
10 30 ms 31 ms 27 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.73]
11 29 ms 31 ms 31 ms 137.221.66.147
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.Thanks all. Seems we’re all failing at the same hop. Server down perhaps?
Still waiting to play, was really hoping the server resets would help… why are we getting 0 communication other than the bluepost asking for a traceroute still?
1 Like
Full reinstall didn’t fix anything
Who said a reinstall would? This is on blizzard’s side.