Keep getting connected to either LAX or mainly PSE1. This is the first time this has happened to me and my latency is over 200+. Pretty much unplayable. Was hoping to farm the lootboxes last minute but, unless I force myself to play at such a high latency, I can’t get them now.
29 posts were merged into an existing topic: [Oceanic] AUS/NZ connecting to PSE1/LAX1 instead of SYD
Keep getting connected to either LAX or mainly PSE1. This is the first time this has happened to me and my latency is over 200+. Pretty much unplayable. Was hoping to farm the lootboxes last minute but, unless I force myself to play at such a high latency, I can’t get them now.
Australian getting connected to PSE1 servers. game is unplayable. Please fix.
In quick play, competitive, deathmatch, the practice range, and even skirmishes, heaps of AUS players are currently almost always getting put into american or singapore servers, and I know this because either lax or sel is shown when I press ctrl+shift+n. The ping is so high (275+) that the game is barely playable at all. only upside is that everybody else is playing at high ping, but I’m frustrated, because this issue has been a problem many times over the last few years, and it seems like every patch reintroduces it even if it was previously fixed. And I know the sydney servers are still up because custom games are fine, and show the correct server id (syd1 or syd2).
Happening to me as well. Every game mode I’ve tried so far is giving me a US (mainly lax) or Singapore server. This includes deathmatch, skirmish, competitive, and some custom games. Yesterday some aus custom games were showing up as having good ping, but actually were also on the wrong server.
I keep getting into 300 ping servers. Hello, Blizzard???
Any chance we could get an update please? We’re still experiencing the issue and it’s been a few weeks since we’ve had a response. I’m located near Sydney AU, on PC, getting connected to PSE1 servers, not SYD, causing huge lag issues.
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
router.asus.com | 0 | 1364 | 1364 | 0 | 0 | 2 | 0 |
gateway.nb01.sydney.asp.telstra.net | 0 | 1364 | 1364 | 3 | 5 | 39 | 4 |
ae251.ken-ice301.sydney.telstra.net | 0 | 1364 | 1364 | 3 | 5 | 60 | 4 |
bundle-ether25.ken-core10.sydney.telstra.net | 0 | 1364 | 1364 | 4 | 5 | 24 | 5 |
bundle-ether1.oxf-gw10.sydney.telstra.net | 0 | 1364 | 1364 | 4 | 6 | 24 | 5 |
bundle-ether1.sydo-core04.sydney.reach.com | 0 | 1364 | 1364 | 4 | 6 | 22 | 6 |
i-91.sydo10.telstraglobal.net | 0 | 1364 | 1364 | 4 | 5 | 105 | 4 |
unknown.telstraglobal.net | 0 | 1364 | 1364 | 5 | 9 | 89 | 9 |
et-0-0-48-br01-eqsy4.as57976.net | 0 | 1364 | 1364 | 5 | 9 | 170 | 5 |
et-0-0-0-pe01-eqsy4.as57976.net | 0 | 1364 | 1364 | 5 | 8 | 132 | 5 |
37.244.40.1 | 0 | 1364 | 1364 | 5 | 6 | 23 | 6 |
I am getting the same issues, from brisbane Australia
Another WinMTR, if it helps… if support is actually reading…
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
router.asus.com | 0 | 1192 | 1192 | 0 | 0 | 7 | 0 |
gateway.nb01.sydney.asp.telstra.net | 0 | 1188 | 1188 | 3 | 6 | 44 | 21 |
ae251.ken-ice301.sydney.telstra.net | 1 | 1184 | 1183 | 4 | 6 | 53 | 29 |
bundle-ether25.ken-core10.sydney.telstra.net | 0 | 1187 | 1187 | 4 | 6 | 23 | 10 |
bundle-ether1.oxf-gw10.sydney.telstra.net | 0 | 1186 | 1186 | 4 | 6 | 23 | 6 |
bundle-ether1.sydo-core04.sydney.reach.com | 0 | 1185 | 1185 | 4 | 6 | 24 | 12 |
i-91.sydo10.telstraglobal.net | 0 | 1189 | 1189 | 4 | 5 | 68 | 6 |
unknown.telstraglobal.net | 0 | 1185 | 1185 | 5 | 9 | 128 | 10 |
et-0-0-48-br01-eqsy4.as57976.net | 0 | 1187 | 1187 | 5 | 9 | 146 | 5 |
et-0-0-0-pe01-eqsy4.as57976.net | 0 | 1185 | 1185 | 5 | 9 | 126 | 8 |
37.244.40.1 | 0 | 1185 | 1185 | 5 | 7 | 42 | 13 |
Same issue, 4/5 games im getting placed on LAX or PSE1.
2Degrees - Gigabit fibre, Wellington NZ.
not sure what else to say
90% of games are being put on SEA
sick of this bs response
so many ppl are having the same problem
How many WinMTR’s are needed for diagnosis?
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
router.asus.com | 0 | 773 | 773 | 0 | 0 | 2 | 0 |
gateway.nb01.sydney.asp.telstra.net | 0 | 771 | 771 | 3 | 5 | 39 | 4 |
ae251.ken-ice301.sydney.telstra.net | 0 | 772 | 772 | 4 | 7 | 55 | 4 |
bundle-ether25.ken-core10.sydney.telstra.net | 0 | 770 | 770 | 4 | 5 | 11 | 6 |
bundle-ether1.oxf-gw10.sydney.telstra.net | 0 | 771 | 771 | 4 | 6 | 15 | 5 |
bundle-ether1.sydo-core04.sydney.reach.com | 0 | 771 | 771 | 4 | 6 | 10 | 7 |
i-91.sydo10.telstraglobal.net | 0 | 771 | 771 | 4 | 5 | 56 | 5 |
unknown.telstraglobal.net | 0 | 770 | 770 | 5 | 9 | 104 | 62 |
et-0-0-48-br01-eqsy4.as57976.net | 0 | 771 | 771 | 5 | 9 | 99 | 5 |
et-0-0-0-pe01-eqsy4.as57976.net | 0 | 771 | 771 | 5 | 8 | 115 | 6 |
37.244.40.1 | 0 | 772 | 772 | 5 | 6 | 21 | 6 |
WinMTR aint gunna provide any useful information, it’s their stock standard response
All of AUS is being affected
This happens every 6-9 months
I’m not convinced WinMTR results to these random servers actually help our issue.
With my experience with different ISP’s I’ve been with over the years across both AU and now NZ, our ping to these foreign servers are as good as they can be.
The issue is we are being placed on the wrong servers by the blizzard matchmaker.
more like every second week lately
WinMTR just shows them the route your computer is taking to their server
i.e. could be a problem with that user or their ISP
If EVERYONE is having the problem, it’s something on their end
Maybe they havent provisioned enough servers, match making is stuffing up, unknown bug etc
What annoys me is when i leave a bunch of high ping matches in a row, I’m told i will (and have) received a penalty because of it
I was experiencing the same issue in July / August last year. Doesn’t look like anything was done, it just… went away… it seems…
I figure the same thing has been occurring since then, but I probably haven’t been playing enough to notice it.