I usually get put on to the syd2 server but ever since the patch i am getting put on pse1 and getting 100+ ms.
not sure why
2 Likes
Yeah last 4 games I played i kept getting sent to either LAX1 or PSE1. It can’t or won’t connect to PSE2.
Driving me crazy.
1 Like
Maybe someone tripped over a power cable.
1 Like
Hi, since the 1.37.0.1 patch me and a bunch of other oceanic players are connecting to the NA servers, I don’t know if this has been brought to your attention yet so here I am posting.
I’ve contacted 12 different people and they are all having the same problem.
*Edit; Most NA users don’t know that the Americas region has a subserver or whatever for oceanic players which we connect to so we aren’t 150-300MS
1 Like
Thanks for the reports, everyone! Merged another topic and updated the title here to keep reports on one thread since they were similar reports of getting connected to Singapore(PSE1) or US West(LAX1).
We’re currently looking into these reports, but would be grateful for the following information to help us with our investigation!
- Current Server (LAX1, PSE1):
- Normal Server (ie. PSE2, SYD2):
- WinMTR test - One to the SYD2 server (IP: 37.244.42.35) and another while running the game through a Co-op match to the the current server it’s matching to.
Same problem for me.
Normal server: SYD2
Current servers: LAX1 or PSE1. I’ve been on both so far. Never on SYD2.
I have gotten a few server errors though.
I can’t do a WinMTR test right now, will do later if you still need one.
I gotta say, there are so many issues with this patch. What were you guys thinking? This was on the PTR for I don’t know how long. What the hell happened to QA? What do you do on the PTR? Why is it there? How the hell could this many numerous bugs get through QA?
ok so i have no idea if i did this right.
Current Server: LAX1
Normal Server: I always thought I was PSE2 but not 100% sure. Im east coast Australia if that helps.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192-168-1-1.tpgi.com.au - 0 | 601 | 601 | 1 | 1 | 122 | 2 |
| 10-20-25-79.tpgi.com.au - 0 | 601 | 601 | 12 | 14 | 135 | 14 |
| 203-219-166-66.static.tpgi.com.au - 0 | 601 | 601 | 13 | 17 | 265 | 14 |
| 203-219-107-102.static.tpgi.com.au - 0 | 601 | 601 | 12 | 16 | 136 | 13 |
| bri-pow-que-wgw1-be-10.tpgi.com.au - 0 | 601 | 601 | 13 | 14 | 137 | 14 |
| be300.bqueebrdr11.aapt.net.au - 0 | 601 | 601 | 13 | 14 | 141 | 15 |
| Bundle-Ether16.cha-edge902.brisbane.telstra. net - 0 | 601 | 601 | 13 | 15 | 139 | 14 |
| bundle-ether7.cha-core4.brisbane.telstra. net - 0 | 601 | 601 | 13 | 16 | 137 | 14 |
| bundle-ether20.ken-core10.sydney.telstra. net - 0 | 601 | 601 | 27 | 30 | 265 | 30 |
| bundle-ether1.oxf-gw10.sydney.telstra. net - 0 | 601 | 601 | 28 | 30 | 264 | 29 |
| bundle-ether1.sydo-core04.sydney.reach. com - 0 | 601 | 601 | 27 | 30 | 263 | 30 |
| i-0-0-0-3.sydo10.bi.telstraglobal. net - 0 | 601 | 601 | 27 | 30 | 257 | 28 |
| unknown.telstraglobal. net - 0 | 601 | 601 | 27 | 29 | 260 | 29 |
| 137.221.85.35 - 0 | 601 | 601 | 28 | 33 | 261 | 29 |
| et-0-0-1-pe01-eqsy4.as57976. net - 0 | 601 | 601 | 27 | 32 | 258 | 29 |
| 137.221.66.133 - 0 | 601 | 601 | 29 | 30 | 264 | 30 |
| 37.244.40.21 - 0 | 601 | 601 | 28 | 29 | 258 | 28 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192-168-1-1.tpgi.com.au - 0 | 551 | 551 | 1 | 1 | 80 | 1 |
| 10-20-25-79.tpgi.com.au - 0 | 551 | 551 | 12 | 14 | 98 | 13 |
| 203-219-166-66.static.tpgi.com.au - 0 | 551 | 551 | 13 | 16 | 182 | 14 |
| 203-219-107-102.static.tpgi.com.au - 0 | 551 | 551 | 13 | 16 | 270 | 14 |
| bri-pow-que-wgw1-be-10.tpgi.com.au - 0 | 551 | 551 | 13 | 14 | 101 | 14 |
| be300.bqueebrdr11.aapt.net.au - 0 | 551 | 551 | 13 | 14 | 107 | 14 |
|Bundle-Ether16.cha-edge902.brisbane.telstra. net - 0 | 551 | 551 | 13 | 14 | 95 | 14 |
|bundle-ether7.cha-core4.brisbane.telstra. net - 0 | 551 | 551 | 14 | 16 | 86 | 16 |
|bundle-ether20.ken-core10.sydney.telstra. net - 0 | 551 | 551 | 27 | 29 | 125 | 29 |
|bundle-ether1.oxf-gw10.sydney.telstra. net - 0 | 551 | 551 | 28 | 30 | 144 | 29 |
|bundle-ether1.sydo-core04.sydney.reach. com - 0 | 551 | 551 | 28 | 30 | 104 | 29 |
| i-0-0-0-3.sydo10.bi.telstraglobal. net - 0 | 551 | 551 | 27 | 29 | 99 | 29 |
| unknown.telstraglobal. net - 0 | 551 | 551 | 27 | 28 | 103 | 28 |
| 137.221.85.35 - 0 | 551 | 551 | 28 | 33 | 152 | 29 |
| et-0-0-1-pe01-eqsy4.as57976(.)net - 0 | 551 | 551 | 28 | 31 | 121 | 28 |
| 137.221.66.133 - 0 | 551 | 551 | 29 | 30 | 124 | 30 |
| 37.244.40.21 - 0 | 551 | 551 | 28 | 29 | 107 | 29 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|`
Yours would be SYD. PSE is the Singapore server.
I thought PSE1 was the singapore server and PSE2 was the Sydney server?
While I haven’t checked lately I used to normally be connected to the PSE2 servers with a 30ish RTT (<20ms ping). For that I’d assume it would be Sydney.
Wonder if the PSE2 servers moved?
My issue has been resolved… i just waited it out and i went back to syd2
same problem,guess the syd server is under maintenance?
Current Server : PSE1
Normal Server : Thought it was PSE2 but could be SYD2 (would have said the closest datacenter would be Sydney
WinMTR fails on both PSE1 and SYD2, no idea why as it works on other IP addresses including 8.8.8.8
Training room now puts me into SAC1 with a 374ms latency
Last 2 MH games were in SYD2 so guessing it could be getting fixed 
But here is a tracert to SYD2
Tracing route to 37.244.42.35 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 5 ms 3 ms 4 ms ************************** [106.70.0.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 5 ms 5 ms 5 ms ************************[124.19.61.76]
6 5 ms 6 ms 7 ms ****************************[139.130.61.73]
7 6 ms 7 ms 8 ms *********************** [203.50.11.142]
8 22 ms 20 ms 21 ms ************************ [203.50.11.178]
9 39 ms 20 ms 20 ms ***********************[203.50.6.97]
10 22 ms 19 ms 20 ms **************** [203.50.13.94]
11 19 ms 20 ms 20 ms ****************[202.84.222.198]
12 21 ms 21 ms 20 ms **************** [210.176.152.33]
13 58 ms 27 ms 29 ms 137.221.85.35
14 21 ms 20 ms 22 ms ******************* [137.221.85.73]
15 47 ms 25 ms 31 ms 137.221.66.135
16 21 ms 21 ms 20 ms 37.244.40.37
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
And to PSE1
Tracing route to*********************** [13.250.30.198]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 4 ms 6 ms 4 ms **************** [106.70.0.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 18 ms 18 ms 24 ms 198.142.249.242
6 * * * Request timed out.
7 15 ms 15 ms 16 ms 198.142.249.250
8 109 ms 110 ms 110 ms 203.208.174.197
9 132 ms 157 ms 111 ms 203.208.158.209
10 112 ms 111 ms 111 ms 203.208.175.70
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 113 ms 114 ms 120 ms 203.83.223.23
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
PSE2 was the Sydney servers, there were some changes made which switched it over to SYD2, we started seeing this a few weeks ago. Thanks for the reports and WinMTR tests. Is anyone else still experiencing the mismatched to PSE1/LAX1 servers?
1 Like
Im still currently seeing the same issue i avg around 20 to 30 even in trainning room and since this update it wont go any lower than 200ms
Thanks, S4TAN! We’re continuing to gather information in the mean time and hopefully have an update on this issue soon!
Please continue to run the WinMTR tests! Please do this in something like Co-op vs AI. Training mode puts you in any random server room rather than the normal mechanics.
It appears to have subsided when playing comp (20-30ms) , however in training still high latency above 250
does this post have any updates?
It sounds/looks like it’s all good again for normal matches however the practice range is still picking SAE1 which is a crazy high ping
Ive also noticed sound studdering during some games even after several restarts doesnt happen in comp only in trainning and qp
So the training room/practice range is actually “de-prioritized”. What this means is that while you’re in that game mode, you’ll get connected to whatever server is available. If the main game servers are busy, you’ll end up on the wrong server group, because everything is being processed on your client so your connection speed doesn’t really matter. If you’re only put on the incorrect server in training, that’s normal. We only need to worry if it’s happening in normal game modes like Quick Play/Competitive.
With the sound stuttering, on the other hand, that could be something else entirely. Are you getting latency spikes or FPS drops when the stuttering happens? Is there any other odd game behavior, like temporary screen freezeups or players running in place?