[Oceanic] AUS/NZ connecting to PSE1/LAX1 instead of SYD

Technical Support
171

here are mine,

got some SYD2 ones(excluded them), never got SYD1

all PSE1, Quickplay, Sydney, Telstra.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                               mygateway -    0 |  268 |  268 |    0 |    0 |    1 |    0 |
|     gateway.nb06.sydney.asp.telstra.net -    0 |  268 |  268 |    7 |   12 |   42 |   10 |
|     ae256.ken-ice301.sydney.telstra.net -    0 |  268 |  268 |    8 |   13 |   55 |   12 |
|bundle-ether25.ken-core10.sydney.telstra.net -    0 |  268 |  268 |    8 |   12 |   22 |   12 |
|bundle-ether1.oxf-gw10.sydney.telstra.net -    0 |  268 |  268 |    9 |   13 |   25 |   12 |
|bundle-ether1.sydo-core04.sydney.reach.com -    0 |  268 |  268 |    9 |   13 |   23 |   14 |
|           i-91.sydo10.telstraglobal.net -    0 |  268 |  268 |    9 |   12 |   21 |   10 |
|               unknown.telstraglobal.net -    0 |  268 |  268 |   10 |   16 |   73 |   11 |
|        et-0-0-48-br01-eqsy4.as57976.net -    0 |  268 |  268 |   10 |   18 |  103 |   12 |
|         et-0-0-0-pe01-eqsy4.as57976.net -    0 |  268 |  268 |    9 |   15 |  112 |   13 |
|                             37.244.40.1 -    0 |  268 |  268 |   10 |   13 |   27 |   18 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


PSE1
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                               mygateway -    0 |  560 |  560 |    0 |    0 |    3 |    0 |
|     gateway.nb06.sydney.asp.telstra.net -    0 |  560 |  560 |    7 |   11 |   39 |    9 |
|     ae256.ken-ice301.sydney.telstra.net -    0 |  560 |  560 |    8 |   12 |   52 |   17 |
|bundle-ether25.ken-core10.sydney.telstra.net -    0 |  560 |  560 |    8 |   12 |   20 |   11 |
|bundle-ether1.oxf-gw10.sydney.telstra.net -    0 |  560 |  560 |    9 |   13 |   24 |   12 |
|bundle-ether1.sydo-core04.sydney.reach.com -    0 |  560 |  560 |    9 |   13 |   24 |    9 |
|           i-91.sydo10.telstraglobal.net -    0 |  560 |  560 |    8 |   12 |   66 |    9 |
|               unknown.telstraglobal.net -    0 |  560 |  560 |    9 |   16 |   82 |   12 |
|        et-0-0-48-br01-eqsy4.as57976.net -    0 |  560 |  560 |   10 |   18 |  149 |   15 |
|         et-0-0-0-pe01-eqsy4.as57976.net -    0 |  560 |  560 |    9 |   16 |  131 |   10 |
|                             37.244.40.1 -    0 |  560 |  560 |   10 |   13 |   23 |   12 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

will add more as they come along

172

Adding my frustration as an Australian player of getting periodically connected to the Singapore / SEA servers. Not only for me, this occurs often in groups with players from all over Australia. This typically results in people leaving either straight away or after first poor round of bad pings. Can we please get a fix to this problem?

2 Likes
173

This has been a recurring issue for over a year, the only reason I can think for that is blizzard don’t care. It’s OCE after all, as long as it doesn’t happen for the Americans and Koreans

2 Likes
174

I think it’s more because the huge majority of us simply can’t be bothered posting anymore on here so it’s not seen as a major widespread issue.

Every bad ping server I’ve been popped into tonight has been full of au/nz peeps in the chat, and yet letting people know this thread is alive and could use more posts, very little people have bothered contributing.

175

Another observation I made tonight while watching the WinMTR window.

There was 0 big spikes in latency or lost packets on any of the hops for a good minute or so before my queue popped and I still got placed on LAX1 along with a lobby full of au/nz peeps.

I’m becoming more than convinced now this has nothing to do with congestion or pre-match server ping tests.

1 Like
176

got one more, here ya go, added to the pile,

a lot of people would have given up at this point and left the game, I know some who have, your losing people because of this…

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                               mygateway -    0 |  450 |  450 |    0 |    0 |    4 |    0 |
|     gateway.nb06.sydney.asp.telstra.net -    0 |  450 |  450 |    8 |   12 |   49 |   12 |
|     ae256.ken-ice301.sydney.telstra.net -    0 |  450 |  450 |    8 |   12 |   53 |   11 |
|bundle-ether25.ken-core10.sydney.telstra.net -    0 |  450 |  450 |    9 |   12 |   24 |   14 |
|bundle-ether1.oxf-gw10.sydney.telstra.net -    0 |  450 |  450 |    9 |   13 |   20 |   13 |
|bundle-ether1.sydo-core04.sydney.reach.com -    0 |  450 |  450 |    7 |   13 |   22 |   11 |
|           i-91.sydo10.telstraglobal.net -    0 |  450 |  450 |    9 |   12 |   23 |   13 |
|               unknown.telstraglobal.net -    0 |  450 |  450 |   10 |   16 |   79 |   45 |
|        et-0-0-48-br01-eqsy4.as57976.net -    0 |  450 |  450 |   10 |   17 |  138 |   14 |
|         et-0-0-0-pe01-eqsy4.as57976.net -    0 |  450 |  450 |    8 |   14 |  136 |   17 |
|                             37.244.40.1 -    0 |  450 |  450 |    8 |   13 |   22 |   14 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like
177

Adding another to the pile.
Got more PSE/LAX games last night. Ran WinMTR all night as LewdBerry did - no big ping spikes, it was stable the whole time.

Here’s an MTR I ran for a couple of minutes.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                      10.62.4.1 -    0 |  154 |  154 |    0 |    0 |    0 |    0 |
|          41.7.69.111.static.snap.net.nz -    0 |  154 |  154 |    2 |    6 |   43 |    4 |
|                   No response from host -  100 |   31 |    0 |    0 |    0 |    0 |    0 |
|          4.56.69.111.static.snap.net.nz -    0 |  154 |  154 |   24 |   25 |   29 |   26 |
|          5.56.69.111.static.snap.net.nz -    0 |  154 |  154 |   25 |   29 |  101 |   26 |
|     BE-108.cor02.syd04.nsw.VOCUS.net.au -    0 |  154 |  154 |   25 |   26 |   28 |   25 |
| bundle-101.bdr01.syd11.nsw.vocus.net.au -    0 |  154 |  154 |   25 |   28 |   97 |   27 |
|Bundle-Ether12.ken-edge903.sydney.telstra.net -    0 |  154 |  154 |   25 |   26 |   28 |   27 |
|bundle-ether17.ken-core10.sydney.telstra.net -    0 |  154 |  154 |   25 |   27 |   30 |   29 |
|bundle-ether1.oxf-gw10.sydney.telstra.net -    0 |  154 |  154 |   26 |   27 |   30 |   28 |
|bundle-ether1.sydo-core04.sydney.reach.com -    0 |  154 |  154 |   26 |   27 |   30 |   27 |
|           i-91.sydo10.telstraglobal.net -    0 |  154 |  154 |   26 |   26 |   29 |   26 |
|               unknown.telstraglobal.net -    0 |  154 |  154 |   26 |   30 |   91 |   26 |
|        et-0-0-48-br01-eqsy4.as57976.net -    0 |  154 |  154 |   26 |   31 |  164 |   26 |
|         et-0-0-0-pe01-eqsy4.as57976.net -    0 |  154 |  154 |   25 |   29 |  138 |   27 |
|                             37.244.40.1 -    0 |  154 |  154 |   26 |   27 |   29 |   28 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~~
1 Like
178

Caterpepi, just touching on Lewdberry’s comments on people not commenting and providing test results…I honestly thought this was Blizzards Job to maintain their game & servers?.. Expecting people to pay for your game and then fix it for you is not a sustainable business model. I can confirm that all of my friends and I, who are with various different ISPs, are experiencing server issues. Ping is 250ms+. If im lucky I get a 50ms server. My current experience and opinion of Blizzard does not promote my desire to purchase products from them again. I think its time for your Network engineers to start probing the servers themselves to find out why we are getting connected to servers overseas… Unless there is something you arent telling us?.. #WeShutdownAU/NZServers…

4 Likes
179

This post was created 5 days ago.

We understand it has something to do with the ISP’s, and we know it’s not exactly the easiest thing to solve. But surely 5 days is enough for these people to suffer

Today’s Update:

It obviously has brought quite a lot of bugs, but now this issue has transferred over to console. And I feared this would happen when the video yesterday got put out about the update coming out. We haven’t had our daily update yet, and now this is getting very tedious and concerning, not only for me but everyone else in this thread.

2 Likes
180

Made a booking with my ISP tonight for some indepth tests during the usual time. Will post results later tonight.

3 Likes
181

Please fix Aus server issue

PSE1 server
|WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
mymodem.modem 0 184 184 0 0 2 0
gateway.vb12.melbourne.asp.telstra.ne 0 184 184 1 3 53 1
203.50.62.234 0 184 184 1 6 64 1
bundle-ether25.exi-core10.melbourne.telstra.ne 0 184 184 1 3 48 3
bundle-ether2.way-core10.adelaide.telstra.ne 0 184 184 14 16 50 15
bundle-ether3.pie-core10.perth.telstra.ne 0 184 184 41 43 83 43
203.50.9.2 0 184 184 41 43 81 44
i-15453.pthw-core02.telstraglobal.nt 0 184 184 39 42 74 40
i-25154.sgcn-core01.telstraglobal.ne 0 184 184 86 88 116 87
202.84.219.173 1 180 179 97 98 134 98
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
203.83.223.19 0 184 184 241 243 280 245
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
No response from host 100 37 0 0 0 0 0
182

I can’t even log into Overwatch, because the battle.net launcher thinks the game is up to date but it hasn’t updated to the Ashe patch yet. So, when I try to launch the game it can’t connect to a game server at all.

Which also means I can’t run any tests in game. :confused:

183

You may want to start a new thread or contact support. But try this here Overwatch Won’t Launch

184

I don’t know if this is a coincidence or not but i got the PSE server IPs from the in game netrgraph and blocked them in Windows Firewall with an inbound and outbound rule.

Was getting PSE servers every second game now i haven’t had one in over 20 games. Like i said i may just be getting realllllly lucky atm though.

2 Likes
185

Alrighty, we did alot different tests and monitored the connection for the past hour.

Out of the 390k packets total sent, only 6 were ever dropped (4 were by et-0-0-48-br01-eqsy4.as57976. net, 2 by unknown.telstraglobal. net).

No other issues or big spikes seen anywhere over my ISP’s network or my route to the Sydney AWS (SYD2 data center).

For what it’s worth I’m told my connection to PSE1/LAX1 servers are also as good as they can be, with suprisingly 0 packet loss despite being on the other side of the planet.

He then remoted in and installed wireshark and did some more tests.

On game startup the client connected to 11 total IP addresses and chatted/pinged with them over 5ish seconds.
These included the SYD2 data center IP 37.244.42.0/24 and US Central 24.105.62.0/24.

It’s highly likely this is the ping test for the matchmaker to see what server best suits.

And then? Nothing.

My client never once talks to the SYD2 data center or any instance/‘subnet’ of it ever again, not until actually entering the server when a match pops (The actual loading screen).

Pre-joining PSE1 or LAX1, no packets are sent or recieved over any protocol to test my connection against SYD2 beforehand.

We tried: Entering/exiting queue, creating custom lobby, joining/leaving a group, return to lobby after game end, left game at main menu for over an hour and repeated.

I would love someone to explain to me why tests like WinMTR to see personal connection stabilty are at all relevant to this issue when the game client itself isn’t even testing against the actual data center it intends to connect too? Stable connection or not, it’s irrelevant to where its putting me if it’s using a snapshot from when game first launched and has put me on several SYD2 sessions beforehand?

An interesting fact he also brought up was that when placed on a foreign server, it’s always a full lobby of au/nz people.

This actually suggests the matchmaker is infact working correctly, as it’s finding and grouping people from the same region correctly without issues before match start.

However for whatever reason it’s not starting the match with the group it’s made on SYD2, instead it looks like it’s using whatever else is available.

Further suggesting the fault actually lies with the SYD2 data center itself.

1 Like
186

Heyo, do we have an update on whats going on???
would be good to see how things are progressing

187

Worked for me aswell.

188

That is a lot of testing, very interesting.
If I understand correctly from one of the reps, the SYD2 servers actually do the stability checking hence why you don’t see any connections in wireshark.

One complex part of the internet is that just because my route to 37.244.4X.X is a particular route doesn’t mean the route from 37.244.4X.X is the same. This means the stability issue isn’t necessarily a fault with the datacenters, instead it’s likely a fault of a third party peer.

In saying that although in general it’s not a problem but I would personally say it is a flawed system for the same problem we are having now. I’d be happy to be corrected if any of this is wrong though.

189

Hmm, as in it health checks itself and tells the matchmaker ‘I have a problem, go away’?

If it were to ping or test against someones game client shouldn’t that show up on the persons end under source?

190

Honestly not sure and I could be completely wrong about it, just from your information and a few things said it seems to be the logical conclusion.
It’s possible that parts of the routes are tested for multiple players to reduce the bandwidth in checking instead of the game client itself.

Or maybe it just does the check as OW starts and after each game like WyomingMyst suggested