Thanks Lukey, appreciate you adding the test data.
2 Likes
I’m not being toxic, I’m providing information and feedback related to the thread and the issue at hand. Just because I have a strong opinion of the issue doesn’t make it polluting.
Because it’s not the answer you are after does not make it or me toxic, by the same token perhaps Blizzard is toxic because they fundamentally fail to provide a basic service during peak periods by allowing me to game on the lowest reasonable latency.
1 Like
Yes, but the usual action for multi region matchmaking services to figure out where their users are connecting from, is to use a GeoIP list provider. This provider may have out of date lists from APNIC / ARIN around what’s in use in Australia.
Or it could be a billion other things. What we as players know is:
- It’s not working correctly and we’re getting put onto incorrect region’s servers
- It feels like it is being treated like an end user’s issue when it really looks like it’s a problem with the matchmaking service
5 Likes
Just wanting to add my two cents to this situation…I find it very frustrating, and to a lesser degree insulting that yet again this region of the world gets zero official support or love. Do not get me wrong, we all appreciate what you’ve been doing and will continue to do Nicole (and anybody who doesn’t appreciate you can bugger off ;p) but at the end of the day, the ANZ/OCE community deserve more than a green post, we deserve a blue post to even acknowledge that there is an issue and that they’re looking into it. A simple acknowledgement from Blizzard would go so far to both resolve the issue, and to calm us down. At the end of the day our frustrations stem from the fact that we love this game, we want to see it do well, and we want to play the absolute crap out of it - but the lack of blue does nothing but alienate the community, grow resentment and anger, and ultimately will turn advocates of the game into detractors.
4 Likes
Just to add to the picture, WinMTR output to 37.244.42.122. 15-20 ping on Sydney servers, 110+ on Singapore.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| *ROUTER* - 0 | 1342 | 1342 | 0 | 0 | 6 | 0 |
| 100.96.128.1 - 0 | 1342 | 1342 | 1 | 4 | 66 | 2 |
| Request timed out. - 100 | 271 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 271 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 271 | 0 | 0 | 0 | 0 | 0 |
| 180.150.0.235 - 0 | 1342 | 1342 | 1 | 1 | 19 | 2 |
|be50-3999.cfl3.nextdc-s2.syd.aussiebb.net3 - 1 | 1334 | 1332 | 1 | 2 | 17 | 2 |
| 10.241.12.216 - 21 | 741 | 588 | 2 | 4 | 20 | 4 |
| 10.241.13.109 - 2 | 1290 | 1276 | 2 | 2 | 17 | 2 |
| be3.core5.nextdc-s1.syd.aussiebb.net3 - 1 | 1337 | 1336 | 2 | 2 | 40 | 2 |
| be4.core1.equinix-sy3.syd.aussiebb.net3 - 0 | 1341 | 1341 | 2 | 2 | 25 | 2 |
| 119-18-32-193.cust.aussiebb.net3 - 0 | 1341 | 1341 | 2 | 6 | 114 | 3 |
| 137.221.85.35 - 0 | 1341 | 1341 | 2 | 27 | 255 | 3 |
| et-0-0-0-pe02-eqsy4.as57976.net3 - 0 | 1341 | 1341 | 2 | 2 | 35 | 3 |
| Request timed out. - 100 | 271 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 271 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 271 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 271 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
1 Like
Hi Nicole, thanks for forwarding our tests to the team 
Played with a few different friends and they’ve all experienced the same issue.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| cloudmesh.home - 0 | 717 | 717 | 1 | 3 | 48 | 3 |
| 100...1 - 1 | 713 | 712 | 15 | 21 | 242 | 16 |
| No response from host - 100 | 145 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 145 | 0 | 0 | 0 | 0 | 0 |
| gi0-0-0-1 .bng1.vdc01.syd.aussiebb.net - 0 | 717 | 717 | 12 | 18 | 70 | 19 |
| be10-3999 .core1.nextdc-b1.bne.aussiebb.net - 0 | 717 | 717 | 15 | 18 | 62 | 19 |
| be1.core2 .nextdc-b1.bne.aussiebb.net - 0 | 717 | 717 | 29 | 33 | 122 | 33 |
| be3.core1 .equinix-sy3.syd.aussiebb.net - 0 | 717 | 717 | 28 | 33 | 255 | 31 |
| 119-18-32-193 .cust.aussiebb.net - 0 | 717 | 717 | 29 | 37 | 115 | 32 |
| et-0-0-48-br01-eqsy4. as57976. net - 0 | 717 | 717 | 29 | 51 | 313 | 33 |
| et-0-0-0-pe01-eqsy4 .as57976.net - 0 | 717 | 717 | 27 | 33 | 122 | 32 |
| No response from host - 100 | 145 | 0 | 0 | 0 | 0 | 0 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like
This is the worst part about this game, no other game has this issue. How can I play competitive if its a coinflip whether or not I have 120ms or 16ms? It’s frustratingly inconsistent
4 Likes
Ok thank you and fair enough, yes thats what im 99% sure is happening as its the exact same thing that was happening with valorant, going from perth to sydney and then sydney to singapore, hency why i was pretty adamant that it was a routing issue because the problem was instantly resolved when switching isp. Again in valorant it was 50 ping to sydney and 150 to singapore with eastern states players getting a little over 100, after seeing ABB’s network map showing a direct perth to singapore pathing i switched and the problem was gone with me now getting the expected ~50 ping. Also when i said that you don’t know what you’re talking about was in reference to your insistence that there was in fact a large difference in ping on games for SG vs SYD “I’m not quite sure where you got those latencies from or the ping-times showed to you in-game are incorrect.” Regardless thanks for looking into this.
ips of the singapore servers or something else? If the server ip’s are what u need I already have them
I agree 10000%
The fact they dont even acknowledge that theres an issue, is just pissing me off. Look how many people are on this thread with the problem, clearly its our internet issue not the potato servers… SMH
Every other multiplayer game works fine. Whats different in OW2, internet or the game? I wonder… I cant even anymore…
2 Likes
yes im pretty sure it is actually that it’s the reverse and the syd servers are being overloaded as im still getting long q times when being put in these SEA servers and when trying to select Australia on the custom game server selector it sometimes says this server is unavliable during peak hours. Regardless its stupid that they only let u pick a server on custom games.
Moreso just asking when you’re in a match with 150ms ping, what’s the IP of the server? Just would like to see if the IP’s geolocation is Singapore or Syd. It would be incredibly helpful in determining the problem.
Edit: I found some old Glasswire logs and Overwatch 1 used the SAME IPs at Overwatch 2, ISP routing between myself and the Sydney servers has not changed. This, as you said, indicated over-loaded servers.
1 Like
Friends and I just had a match on syd02 against a group, and then again on gsg1 against the same group for the 3 matches after. Doesnt look related to a random short term misrouting issue from a random isp as its effecting everyone and for almost a week now.
This definitely feels like deja vu of an old issue that bliz patched almost 3 years ago. We had an identical 7-8 month term wide spread issue to this in the past during peak hours to the same pse1 server, which turned out to be a bliz side problem. (gsg1 was formly known as pse1, its the same server were currently being placed on in singapore, bliz renamed it when they converted the singapore DC from aws to google 2 years back).
We had to prove to bliz for 6 months last time with pointless winmtr’s before they eventually caved and changed how they monitor syd02 with their ‘internal tool’. It reduced the frequency of being placed onto pse1 during peak hours down to pretty much 0 immediately the moment they tweaked it.
Fix post: (Old thread links further below).
This honestly feels 1:1 with this, which became just as bad (3 out of 4 games were all pse1) as it is now during peak around halloween 2019. Most thought bliz was cheaping out on servers and simply wasnt renting enough capacity as it was happening all the time during peak times, but it was finally patched on blizzards end 6 months after (which honestly, only happened because of how persistant we were at the time).
From what I can tell this has started happening to literally every person I know (that is still interested in the game) more or less after that emergency maintenance that bliz had to address the extreme login queue issues last week. Was fine on OW2 launch and the 2 odd days prior to that maintenance, so it looks like they may have wiped or broke the fix in some way.
We never got told exactly what they patched all those years ago, but it was something to do with tweaking sensitivity in their server-side internal tool they use for monitoring so that syd02 was made to ignore/become less sensitive to light congestion. Thats all I remember.
TLDR: The game checks on startup the quality of your connection to the game servers (and again internally inbetween every match), our oceania data center is located in sydney which has constant issues with congestion. Although the congestion and packet loss is pretty minimal, the matchmaker was (and apparently now is again) extremely sensitive and still considers syd02 as a worse option even when weighted against higher latency. This is obviously designed for the states in mind as they have better infrastructure and multiple data centers, where the congestion isnt as bad to begin with, and the next preferred servers jump in ping is minimal. However for us as we only have the one the next best thing was always singapore (and rarely sometimes an even worse server if that also pinged badly).
One of the many older threads, this one is what ultimately led to the fix:
Follow-up thread to check after fix was deployed:
.
Tried raising this through the ticketing system but there isn’t an OW category anymore, and the new OW2 button just goes to the category homepage. Raised a generic case tuesday night and was waiting for a response before posting, but it got closed this afternoon and I was directed to this dreaded support forum.
Based on previous experience, getting this resolved through this forum is going to take a very long time. So strap in because its mostly likely not going to be acknowledged for a few more weeks, then its going to take several months of pointless isp accusations and having our threads cycled/closed to hide its severity before blues take ownership and actually engage an internal team again to re-fix it.
If your still around OP, can you update the title to ‘Oct 7th’? Its been happening to people for a week, not 2 days (Might help convince a mod to click the thread sooner).
11 Likes
the ip ranges would do wouldnt they, here is one specific one tho
34.124.187.82
34.87.0.0-34.87.255.255
34.126.0.0-34.126.255.255
35.187.0.0-35.187.255.255
35.198.0.0-35.198.255.255
34.124.0.0-34.124.255.255
1 Like
https//imgur.com/a/DZ4sV0e
Yeah, its Google’s IP ranges for their datacentre in Singapore
https//imgur.com/a/clOvVSA
For me its only Google servers sending me to Sydney then to Singapore.
This is just an ISP problem, right? There’s not much Blizzard can do besides using different data server, right?
1 Like
That’s a good thought, I may be able to ask someone if that’s a possibility in this case.
I agree!
Not sure, but could be the case. I think most of the issues started when they left Amazon and went to Google.
2 Likes
Having the same issue here also. Perth, Australia. Being placed on 160ms servers often, sometimes I get the correct 70ms servers.
4 Likes
This clearly seems like a capacity thing. It’s worst at peak time and fine non-peak. Kinda unacceptable imo to be getting competitive games with 100+ ms.
4 Likes
Same issue for me. In Perth. The majority of games are 160+ every now and then (maybe 25% of time) I will get a game with the same ping I used to get on OW1. At least I have something to blame my bad aim on now 
2 Likes