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

So it’s back again…and again sadly.
WinMTR does show some congestion in telstra but surely not enough to reroute overseas. The winMTR shows the usual route to the SYD2 servers too.

PC - Mystery Heroes usual server SYD2

54.169.131.205 (PSE1)
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 78 133 30 1 1 1 1
n49-198-0-1.mrk1.qld.optusnet.com.au - 0 540 540 1 2 3 2
No response from host - 100 109 0 0 0 0 0
No response from host - 100 109 0 0 0 0 0
No response from host - 100 109 0 0 0 0 0
mas1-hu0-4-0.ig.optusnet.com.au - 0 540 540 15 18 26 22
No response from host - 100 109 0 0 0 0 0
mas2-hu0-4-0.ig.optusnet.com.au - 0 540 540 16 18 58 25
203.208.148.185 - 1 536 535 176 202 306 202
203.208.168.18 - 0 540 540 177 204 255 205
No response from host - 100 109 0 0 0 0 0
No response from host - 100 109 0 0 0 0 0
No response from host - 100 109 0 0 0 0 0
No response from host - 100 109 0 0 0 0 0
No response from host - 100 109 0 0 0 0 0
No response from host - 100 109 0 0 0 0 0
203.83.223.194 - 1 536 535 175 201 232 219

SYD2 (37.244.42.xx)
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
MYGATEWAY - 1 531 526 1 1 1 1
n49-198-0-1.mrk1.qld.optusnet.com.au - 0 551 551 1 2 3 1
No response from host - 100 111 0 0 0 0 0
hu0-6-0-0.o4mopr01.optus net au - 0 551 551 3 5 7 3
bundle-ether18.cha-edge902.brisbane.telstra net - 0 551 551 3 6 10 4
bundle-ether7.cha-core4.brisbane.telstra net - 0 551 551 3 7 15 7
bundle-ether20.ken-core10.sydney.telstra net - 1 547 546 17 21 43 18
bundle-ether1.oxf-gw10.sydney.telstra net - 1 547 546 18 22 51 22
bundle-ether1.sydo-core04.sydney.reach com - 0 551 551 18 22 110 20
i-91.sydo10.telstraglobal net - 0 551 551 18 21 96 18
unknown.telstraglobal net - 0 551 551 19 25 101 23
137.221.85.35 - 0 551 551 18 24 224 19
et-0-0-0-pe04-eqsy4.as57976 net - 0 551 551 18 24 140 29
1 Like

These last hubs are showing “spikes” of latency (based on the average and worst ping rates), most likely bundle-ether1.sydo-core04.sydney.reach com is the focal point.

I have a winMTR for 37.244.42.67 just underneath the singapore one

Sorry about that, trying to triage with all of the reports coming in and missed it. I updated my response.

All good :slight_smile:
Yea I see it too but the AVG is still in the 20’s so it doesn’t really make sense for Overwatch to reroute to a min of at least 175 and avg of 201 to Singapore

Overwatch does a steady ping test to all datacenters for the region (in this case “Americas”) when you first log on (and every time you return to the lobby after a game), if it can’t verify the connection stability, it will move to a more stable one I believe.

I get the design idea and it probably works better in other areas where the closest alternative doesn’t give 200+ latency in game. I bet most AUS/NZ players would prefer to be able to be locked to the SYD servers even if it means slightly less stable. It would make so many players happy, but I get that’s not something you can change :slight_smile:

2 Likes

You end up connecting all over the place, people are falling out of games constantly - it is super bad out here.

You may want to provide them a winMTR test so they can assist further.

Running winMTR
  1. Download WinMTR
  2. Extract the contents of the .zip file to your desktop.
  3. Open the WinMTR folder, then open the folder that matches your version of Windows (32-bit or 64-bit) and run WinMTR.exe.
  4. Enter the IP address you want to test in the Host field. Select a game from the dropdown below for a list of IP addresses.
    Note : If multiple IPs are listed, run a WinMTR test for each IP address.
  5. Click Start , then launch the game you’re testing. If no connection issue is found in the first 5 minutes, restart the test.
  6. When a connection error occurs, play for at least 5 more minutes, then click Stop in WinMTR.
  7. Click " Export Text " and save the .txt file to your desktop. Name this file WinMTR.
  8. Reply to your ticket and attach the text file with your results to your reply.

Or you know, this is a reoccurring issue for the last 12 months. They fix it for a couple weeks, it goes to crap again, they fix it, goes to crap. Its super fun.

6 Likes

I think the servers are just problematic and to make everyone happy in the OCE community, to implement their own servers. Although I know that would cost millions.

winmtr plz lol bbq rofl copter

1 Like

They run out of aws in Sydney, there are oce servers.

Hey everyone, I do believe there is a consistant problem for Australian players attempting to connect to the SYD2 datacenter. If any of you have time a WinMTR test may help me find out more answers to this. You may need to use the preprovided IP address listed below:

WinMTR instructions:

  1. Download WinMTR from Download WinMTR-v092.zip (WinMTR) (Console players need a Windows Desktop Computer connected to the same network as their console to do this.)
  2. Unzip the WinMTR.zip file to the Desktop.
  3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
  4. Run the WinMTR.exe
  5. Type the IP address you want to trace in the “Host” field. To get the correct IP you will actually need to open up the game and go Practice Vs AI or Quick Play and if you are on PC hit Ctrl+Shift+N and it will bring up the ingame network diagnostic graph, or go to Video > Options > Display Network Performance Graph if you are on any platform including Console. In the top left corner is the IP address you want to run WinMTR to.
    Network Graph
    note When looking at the IP it will show up ingame as something like 12.34.56.78:12345. You will want to leave the last 5 digits and the colon at the end off and the IP you want to use is just the 12.34.56.78
  6. Once you notice the connection issue while playing, play for about 6 more minutes, minimize the game and click on “Stop”.
  7. Click on “Copy text to clipboard”, then return to this forum thread.
  8. Type two sets of four squiggly lines and then paste the contents of the WinMTR test between: ~~~~ Paste WinMTR Test Results Here ~~~~

If in the event you can’t even connect to Overwatch and get into any game mode at all, please use one of the following IP addresses based on your geographical region:

  • US West - 24.105.30.129
  • US Central - 24.105.62.129
  • Brazil - 54.207.107.12
  • Europe - 185.60.114.159
  • Europe - 185.60.112.157
  • Korea - 211.234.110.1
  • Taiwan - 203.66.81.98
    *** Australia - 37.244.42.56**

as the title says…

1 Like

Yes we are.
Tonight in comp has been horrible.

I aint touching comp at all until we get an aswer because this is garbage.

winmtr now or no help

How do we do this?

Also, multiple people reporting this or no help? Legit?
All comp matches tonight everyone complained their ping was high.

For AUS/NZ 37.244.42.67 would be the closest geographically

1 Like

25 posts were merged into an existing topic: [Oceanic] High Latency or Connecting from AU to NA (2/16)