OCE Server Lag and Routing Issues

List of RECURRING issues over WEEKS

  • I sometimes get local servers like SYD2 (Sydney) but still have high ping (~300ms)

  • I get put on very far-away US servers like LA but have lower ping than on local (~200ms)

  • I get put on random GBR servers in training range

  • I get put on Singapore servers (this is a long standing routing issue for years)

  • Other times, WITHOUT changing anything else - I just get my regular SYD servers at <20ms

Its clearly random and something to do with some server routing. Please HELP

EDIT: I downloaded ExitLag to try and see what’s going on. The SYD2 server is has the JP Tokyo IP???

EDIT2: I’ve had success with ExitLag in the last 2 days. I can get the app to route me more reliably and not connect to any weird regions.

6 Likes

I’ve had the same issue for weeks now. I’m on Aussie Broadband. I’ve posted twice on these forums now but haven’t gotten any help at all or suggestions. It’s so frustrating!

Thanks - hopefully more people will speak up and they’ll finally notice…

Same thing happening to me as well for the past month or so.

Same issue here, its a SYD server but 200-300ms

1 Like

This has been happening on and off since release of OW1. Support will tell you it’s your ISP or to use a VPN, in reality it’s THEIR issue.

2 Likes

Also been getting random 280-300 ping on SYD2 server for last few weeks. I’m in New Zealand so unlikely to be ISP issue unless AU and NZ ISPs have the same routing problem. Normally get 35-40ms.

2 Likes

I wonder if we’ll ever get an official response to this issue. It’s been close to a month now since I’ve started experiencing this.

1 Like

Been experiencing similar server routing issues.

Performing route -f and then ipconfig /flushdns in Window’s command window in admin mode brings pings down from 400 back to a normal 25 on the same server. By that time you’re suspended from the match though when you can connect again and ruined 9 other people’s game.

Means Overwatch is doing something silly with their dynamic server allocations.

Doesn’t happen in literally any other game.

2 Likes

Also experiencing this. Usually 70ms (WA based), randomly jumps to approx. 330ms between games during the same gaming period.

The Singapore issue is different altogether, IMO.
That’s just what it does when it cant find enough players in our region so it puts us on Singapore. That’s just tough.

That aside, I’m in New Zealand and can comfortably play on Singapore or NA servers (west coast) at 130-150ms, and have zero problems.

When I am put onto a Sydney server, I have zero issues. My ping is usually 30-40ms and I am not having any issues.

Ultimately I put this down to broadband / ISPs in Australia being bad :smiley:

1 Like

Same thing is happening to me and my roomie. We’ll both get placed on SYD2, but one of us will have 28ms and the other will spike to 300ms. It makes no sense, same server name, same house, same ISP, completely different routing paths. It’s like one of the games decides to take a world tour before landing on SYD2. This has been happening for weeks. Can Blizzard please look into this? Clearly something’s broken with the way traffic is routed.

Not an issue with Aussie broadband / ISPs - I am in NZ and suffer the same issues mentioned in this thread.

Stadium switching servers between maps, going to either GSG1 or GTK1 generally. Even when the lobby is full OCE.

I also have huge issues with SYD2 for some reason, connection is unstable - even when on “normal ping” it will fluctuate between 57ms-64ms which theoretically would be fine but it is so unstable for some reason, genuinely is more playable on 160ms on LAX. Additionally, I get the routing issues with SYD2 - just played a stadium game where I had 320ms and was horrific.

It is worth noting I have switched ISPs and moved house several times, I have had the SYD2 issues for genuine years. It only affects myself, my roommate has no issues despite being on the same network.

Unfortunately it looks like I can’t attach images so will type the data from the network menu of that 320ms game:
SIM 9.2/ 12.4/ 21.9 ms
IND 24.2/ 24.8/ 25.3 ms
LAT 0.0/ 2.4/ 22.8 ms
PNG 305.1/315.4/324.5 ms
RTT 318.5/319.4/320.7 ms
green line = 16ms
CMDQ 20.0/21.4/23.0
PPS IN ~65.1
PPS OUT ~6.1
LOSS IN ~0.4%
LOSS OUT ~0.0%

Overwatch is the only game I have any connection issues with.

2 Likes

Your network stats look similar to mine when this issue is present. Everything transmitting to them quickly but takes long receiving information back, RTT is always in hundreds while the others are in 10-20ms

Can confirm it is ALWAYS Syd2 with the dramas…

It’s not just OCE. I live in Taipei, Taiwan. This happens on the ICN1 server in Korea too.

I am using ExitLag and can see the game is connecting me to say, an LA, Boston, Chicago, or Seattle game-server, then routing me back all the way to Asia.

I opened a ticket, and basically, they said my only recourse is to post here.

The game may be hosted in Sydney, for example, but you’re connecting to a Blizzard server elsewhere first, as if they are trying to optimize your connection. This is most definitely not a your settings or ISP issue. No connections are 100% stable.

I usually live in the US, and this never happens there. I’m guessing it’s more stable than multi-country connections here.

This is something that requires actual developer intervention is what I’m guessing, given that it’s happening in multiple regions.

This also never happened when I was here a year ago in Taipei. It also didn’t happen 3 years ago when I was here. This is new.

This also doesn’t change in real time. For example: I can play the same stadium game, on the same server, with nearly identical people, and one game, I’ll have 300-400ms, the other, I’ll have 70ms to the KR server. No matter how many times I disconnect, use VPN, change VPNs and reconnect, I’m at the same 300ms. So once Blizzard has determined what is the best route, it sets it for the game.

I’ve often quit games due to this issue before it starts so my team doesn’t have to suffer with my 2-3k per round Soldier 76 damage, but it started happening in ranked games yesterday too. My next suspension time is probably 8 hours. And since we are all from different countries, I can’t communicate that to my teammates. I suspect if this keeps up, I’ll eventually get banned by reports for something like gameplay sabotage.