Australia/New Zealand - High Latency or Connecting to Wrong Servers since 2/Jul/2019

Whisper-11285 · July 3, 2019, 3:06am

anon98253746 · July 3, 2019, 10:32pm

Thanks Nathardrick - game connected normally this morning

InfamousFTW-11960 · July 3, 2019, 11:23pm

Can confirm, I also had no issues connecting today. Would have been nice to have had more communication overall, but glad it’s finally fixed.

elcarter-6843 · July 4, 2019, 1:04pm

C:\WINDOWS\system32>tracert 103.4.114.233

Tracing route to 103.4.114.233 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms NF18ACV.Home [192.168.1.1]
2 19 ms 6 ms 6 ms lo1.bng01-a1-adl.home.superloop.com [122.199.18.1]
3 7 ms 7 ms 7 ms TenGigE0-0-0-6.100.bdr01-ipt-274hindl-adl.au.superloop.com [203.153.17.25]
4 15 ms 15 ms 15 ms FortyGigE0-0-1-2.110.bdr01-ipt-826lorim-mel.au.superloop.com [103.200.13.116]
5 26 ms 26 ms 27 ms as58580.vic.ix.asn.au [218.100.78.37]
6 26 ms 26 ms 26 ms 137.221.85.35
7 36 ms 36 ms 36 ms et-0-0-1-pe01-eqsy4.as57976.net [137.221.85.71]
8 50 ms 50 ms 51 ms 137.221.66.145
9 55 ms 52 ms 52 ms 10.106.67.70
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

Whisper-11285 · July 5, 2019, 11:50am

Tracing route to 103.4.114.233 over a maximum of 30 hops

The 180 game
1 <1 ms <1 ms <1 ms HOME_NETWORK_GA [10.1.1.1]
2 8 ms 9 ms 8 ms 172.22.0.1
3 8 ms 10 ms 9 ms [150.101.34.1]
4 19 ms 20 ms 18 ms [150.101.34.41]
5 18 ms 21 ms 19 ms [150.101.33.36]
6 20 ms 25 ms 19 ms [150.101.41.121]
7 19 ms 26 ms 18 ms [150.101.41.123]
8 19 ms 19 ms 19 ms [45.127.173.41]
9 140 ms 154 ms 196 ms [137.221.85.47]
10 18 ms 22 ms 22 ms [137.221.85.67]
11 19 ms 23 ms 20 ms 137.221.66.145
12 * * * Request timed out.
13 * * * Request timed out.

The 120 game.
1 <1 ms <1 ms <1 ms HOME_NETWORK_GA [10.1.1.1]
2 9 ms 8 ms 7 ms 172.22.0.1
3 9 ms 11 ms 12 ms [150.101.34.1]
4 18 ms 19 ms 19 ms [150.101.34.41]
5 20 ms 19 ms 20 ms [150.101.33.36]
6 18 ms 19 ms 21 ms [150.101.41.121]
7 20 ms 19 ms 22 ms [150.101.41.123]
8 20 ms 20 ms 18 ms [45.127.173.41]
9 96 ms 64 ms 55 ms [137.221.85.47]
10 19 ms 26 ms 18 ms [137.221.85.67]
11 20 ms 20 ms 20 ms 137.221.66.145
12 * * * Request timed out.
13 * * * Request timed out.

Getting 180ms on oce server randomly since the fix. One game it’ll be my usual 20-30, the next right after wont go under 180.

Literally just did the brawl. First game, 180 ping, 2nd game, 30 ping, 3rd game, 120 ping.

Also lol “can’t post links” so have to edit the tracert lol bnet forums.

Set-11284 · July 6, 2019, 3:35am

no you don’t. lol, read the instructions when you go to paste it

There’s something wrong here, as Whisper pointed out. We’re seeing some games with up to 200ms pings, meaning it’s either not hosted in Australia, or is going via some weird routing.

Can we get this fixed once and for all?!

Whisper-11285 · July 7, 2019, 6:24am

Still happening @ Nathardrick

Whisper-11285 · July 9, 2019, 11:57am

Still happening @ Nathardrick

" We have made some changes that should help with the issue for AU and NZ players. Please post back with a WinMTR if there is still a problem."

Well, here’s your WinMTR, can I get a response now?

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| HOME_NETWORK_GA - 0 | 308 | 308 | 0 | 0 | 4 | 0 |

| 172.22.0.1 - 0 | 308 | 308 | 7 | 11 | 75 | 33 |

| be21.450.cr2.mel10.on.ii.net - 0 | 308 | 308 | 8 | 12 | 79 | 40 |

| be51.cr2.mel11.on.ii.net - 0 | 308 | 308 | 18 | 22 | 79 | 23 |

| be55.cr3.syd2.on.ii.net - 0 | 308 | 308 | 18 | 22 | 79 | 27 |

| ae15.cr1.syd4.on.ii.net - 0 | 308 | 308 | 18 | 23 | 69 | 28 |

| ae3.cr2.syd4.on.ii.net - 0 | 308 | 308 | 17 | 22 | 97 | 61 |

| 57976.syd.equinix.com - 0 | 308 | 308 | 18 | 27 | 99 | 81 |

| et-0-0-49-br01-eqsy4.as57976.net - 7 | 249 | 234 | 101 | 164 | 259 | 143 |

| et-0-0-0-pe01-eqsy4.as57976.net - 0 | 308 | 308 | 17 | 24 | 102 | 28 |

| 137.221.66.145 - 0 | 308 | 308 | 17 | 22 | 95 | 61 |

| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |

|____________|||||||

Whisper-11285 · July 9, 2019, 1:20pm

Greetings,
This is Game Master Ascadalrik at your service! (￣^￣)ゞ
You can call me Asca for short and it rolls off the tongue better

I’m sorry to hear this frustrating issue I’m sure you are facing. The Blue poster is still investigating into this issue and is looking hard into this problem right now. While he may have gone silent, this issue is still on-going and being investigated by our team. I’m afraid that at this stage, we aren’t ready to announce anything; hence, the lack of replies. Please do continue posting on the forums for your findings regarding this issue to help us work through this problem;

Best, GM Ascadalrik

You know why I love GMs, because I got this response in less than 35 mins from me opening a ticket. So somehow, they were able to open my ticket, find the blue poster in this thread, contact them, get an update, then write a response all in less than 35 mins.

Man I sure do wish blue posters were that efficient

Or you know, it’s copy pasted bs.

Set-11284 · July 9, 2019, 1:39pm

Still a problem, getting some games with up to nearly 300ms pings. WTF have you done, blizzard?!

Whisper-11285 · July 10, 2019, 11:45am

Another day, another day of complete silence from Blizzard CS. Thanks for the update guys…

I know it must be difficult to take the time out of posting in other threads to tell us what’s happening to our server…

Whisper-11285 · July 12, 2019, 11:15am

9 days of still getting 200ms connections to Australian servers for no reason with no update. Can we make it to two full weeks?

Drakuloth · July 13, 2019, 10:48pm

Hey all,

We would like to get more information on this, but we still haven’t received many of the requested tests at all. If you’d like us to see if there’s anything we can do, please provide this information as earlier requested:

Whisper-11285 · July 14, 2019, 6:34am

Greetings,
This is Game Master Eciaya

Yes, I understand that players affected by this issue must be frustrated as the thread has not updated for many days,

However, customer support does not have too much information about the progress of this issue. Surely the issue will be fixed, but maybe it requires some time.
I will send some feedback to our technical team that players should at least see some updates on forums, even the issue has not fixed.

Meanwhile, from what I’ve heard, seems some AU players got the issue fixed after contacting their ISP. Looks like the issue happens when connecting through certain ISP.

Therefore, maybe you can try to contact your ISP and see if they could change the IP address of your router or make some changes. Otherwise, the current stage of this issue is still investigating and need to wait until the fix!

I hope this clears everything up for you! Sorry for any inconvenience made by this. If you still have any other issue, please feel free to contact us again.

Best Regards,
Game Master Eciaya

Can you confirm if what this GM is saying is true @Drakuloth? Is this an ISP issue that I can solve or is this on your end? And if this is an ISP issue, can you find out which ISPs it affects? From what I read earlier in this thread, the people who the original issue also affected are on different ISPs than I am.

I can do more winmtr tests if it happens again tonight, but honestly, going into a game and flipping a coin on whether I’ll have 20ms or 200ms and then having to play said game while being degraded by a team because im lagging isn’t a fun experience.

Whisper-11285 · July 14, 2019, 7:14am

Oh look, first game of the day, 150ms

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| HOME_NETWORK_GA - 0 | 398 | 398 | 0 | 0 | 3 | 0 |

| 172.22.0.1 - 0 | 398 | 398 | 7 | 9 | 22 | 10 |

| be21.450.cr2.mel10.on.ii.net - 0 | 398 | 398 | 8 | 10 | 24 | 9 |

| be51.cr2.mel11.on.ii.net - 0 | 398 | 398 | 18 | 21 | 35 | 24 |

| be55.cr3.syd2.on.ii.net - 0 | 398 | 398 | 17 | 21 | 36 | 19 |

| ae15.cr1.syd4.on.ii.net - 0 | 398 | 398 | 17 | 21 | 39 | 24 |

| ae3.cr2.syd4.on.ii.net - 0 | 398 | 398 | 17 | 20 | 35 | 20 |

| 57976.syd.equinix.com - 0 | 398 | 398 | 18 | 24 | 146 | 55 |

| et-0-0-49-br01-eqsy4.as57976.net - 1 | 390 | 388 | 20 | 136 | 284 | 92 |

| et-0-0-0-pe01-eqsy4.as57976.net - 0 | 398 | 398 | 17 | 22 | 83 | 20 |

| 137.221.66.145 - 0 | 398 | 398 | 17 | 21 | 36 | 19 |

| No response from host - 100 | 80 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

And it’s the exact same that my previous winMTR and traceRT showed 10 days ago.

Whisper-11285 · July 14, 2019, 7:30am

Also sure feels good that blues were posting in the Overwatch forums about this same issue multiple times in the 10 days we had complete silence even though, again, it’s the same issue.

Hmmmm, does this look similar at all?

Me
| 57976.syd.equinix.com - 0 | 398 | 398 | 18 | 24 | 146 | 55 |
| et-0-0-49-br01-eqsy4.as57976.net - 1 | 390 | 388 | 20 | 136 | 284 | 92
| et-0-0-0-pe01-eqsy4.as57976.net - 0 | 398 | 398 | 17 | 22 | 83 | 20 |

OW posts

57976.syd.equinix com - 0	15	15	155	188	232	177
et-0-0-49-br01-eqsy4.as57976 net - 10	11	10	161	178	193	187
et-0-0-0-pe02-eqsy4.as57976 net - 0	15	15	20	22	34	21

Maybe you guys can get your winMTRs from the OW forums?

Here are the posts.

https://forums.whirlpool.net.au/thread/31wl8zv3?p=4

3 games tonight, all 3 120+ ping or higher.

Drakuloth · July 15, 2019, 11:32pm

We are, they aren’t particularly helpful thus far, since most are super short, but we just updated the testing request over there. I’m repeating it here.

For those of you who are still having this problem, please create a WinMTR test during a time when you’re having latency problems on Sydney servers, or if you are getting routed to the wrong server outside of the Practice Range. (The Practice Range will often put you on the wrong server group anyway, so it’s pointless to test here.)

For the “Host” blank, we need you to use this IP address specifically so we can see what’s going on with your test:
37.244.40.1
You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this.

If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.
~~~~
WinMTR goes here
~~~~