hey gang just popping by to say this issue is still there and nothing has changed still getting routed to PSE1 instead of SYD
aaannnndddd again, i only play every second week when i am home and it seems like at least one of those days it connects me to incorrect server.
Still running, you know how it is.
15 days ago this happened and now its back ffs
150+ ping all night - we kinda know why and we kinda don’t.
Can we get answer please?
We can’t play competitively on these pings when we connected to SEA or NA.
And if you wanna leave the servers like this, be our guest, we have other stuff to be playing but we want to play your game ultimately.
Hey everyone o/,
Thank you for the reports. Looked at some data and do see a huge spike in packet loss around the time most of you reported the issue, but seems to have died down. If you’re still having the issue please include a WinMTR so we can see what is going on with the routing. Wyoming’s guide on this has all the info nicely detailed.
Edit: the “View Blizzard Reply” button is broken on this thread, seemingly. Sorry about that! Please see This Post for the latest information.
Heya Uldrision,
Do you mind sharing more about the packet loss? Is that UDP packets lost between client/server? The winMTR I posted only has 2 lost packets in total so that would seem to mean that the packet loss was within the Blizzard network or somewhere along the network QoS is determining that OW game data is less important than pings.
Or is there another option? 
Connecting constantly to PSE server. I played late last night (3am) and it was fine. Today at 3pm when I log in, lag everywhere. Everyone in game says they are lagging as well.
What’s going on!?
same here… been like this all day
almost like they’re running out of servers for people (money? bad server scaling?)
yup, same here, every comp game at the moment. 
There might be more issues that are cropping up, again, if you have time please try running a WinMTR test and use the pre-provided IP address in my post above. Updated results will help determine if the issue is the same from yesterday or something new is cropping up.
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
| www.routerlogin .com - 0 | 392 | 392 | 0 | 0 | 2 | 0 |
| ip-103-85-38-5.syd.xi.com.au - 0 | 392 | 392 | 1 | 3 | 8 | 3 |
| ip-103-85-38-1.syd.xi.com.au - 1 | 389 | 388 | 3 | 4 | 9 | 3 |
| ip-103-85-38-3.syd.xi.com.au - 1 | 389 | 388 | 3 | 4 | 9 | 4 |
| equinixix.syd.xi.com.au - 0 | 392 | 392 | 2 | 4 | 62 | 5 |
| 57976.syd.equinix .com - 0 | 392 | 392 | 4 | 10 | 96 | 14 |
| et-0-0-49-br01-eqsy4.as57976 .net - 0 | 392 | 392 | 3 | 9 | 90 | 4 |
| et-0-0-0-pe03-eqsy4.as57976 .net - 1 | 389 | 388 | 2 | 7 | 79 | 6 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
Everything is fine before equinix. It happens for several weeks and it’s very hard to aim with these lag. Today I was been put in pse1 and even lax1 server, which has 190ms ping. Hopefully Blizzard can figure out what happened and fix them soon.
I added some spaces because links are not allowed.
Happening on and off last 3 nights from New Zealand. Getting PSE and LAX servers every 2-3 games. This is a trace to the SYD2 host during a game I in which I was connected to PSE:
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| NF18ACV.Home - 0 | 340 | 340 | 0 | 0 | 34 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| ae8-20.cpcak-mdr-r1.vocus.co.nz - 1 | 337 | 336 | 10 | 12 | 59 | 11 |
| ae9-20.cpcak-mdr-r1.vocus.co.nz - 3 | 305 | 296 | 10 | 12 | 45 | 12 |
| BE-101.bdr02.akl05.akl.VOCUS.net.nz - 0 | 340 | 340 | 11 | 18 | 573 | 13 |
| bundle-10.cor01.akl05.akl.vocus.net.nz - 0 | 340 | 340 | 34 | 35 | 69 | 35 |
| BE-202.cor01.syd11.nsw.VOCUS.net.au - 0 | 340 | 340 | 34 | 35 | 68 | 35 |
| bundle-100.bdr01.syd11.nsw.vocus.net.au - 0 | 340 | 340 | 34 | 38 | 108 | 36 |
|Bundle-Ether12.ken-edge903.sydney.telstra.net - 0 | 340 | 340 | 34 | 35 | 78 | 35 |
|bundle-ether17.ken-core10.sydney.telstra.net - 0 | 340 | 340 | 34 | 36 | 78 | 37 |
|bundle-ether1.oxf-gw10.sydney.telstra.net - 0 | 340 | 340 | 35 | 37 | 69 | 35 |
|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 340 | 340 | 35 | 37 | 76 | 36 |
| i-91.sydo10.telstraglobal.net - 0 | 340 | 340 | 35 | 37 | 85 | 36 |
| unknown.telstraglobal.net - 0 | 340 | 340 | 40 | 44 | 100 | 40 |
| 137.221.85.35 - 0 | 340 | 340 | 39 | 46 | 162 | 41 |
| et-0-0-0-pe04-eqsy4.as57976.net - 0 | 340 | 340 | 39 | 43 | 171 | 41 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 69 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~And another one for posterity:
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| NF18ACV.Home - 0 | 699 | 699 | 0 | 0 | 34 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| ae8-20.cpcak-mdr-r1.vocus.co.nz - 0 | 699 | 699 | 10 | 11 | 60 | 11 |
| ae9-20.cpcak-mdr-r1.vocus.co.nz - 0 | 699 | 699 | 10 | 11 | 62 | 11 |
| BE-101.bdr02.akl05.akl.VOCUS.net.nz - 0 | 699 | 699 | 11 | 15 | 101 | 11 |
| bundle-10.cor01.akl05.akl.vocus.net.nz - 0 | 699 | 699 | 34 | 35 | 88 | 34 |
| BE-202.cor01.syd11.nsw.VOCUS.net.au - 0 | 699 | 699 | 34 | 35 | 79 | 35 |
| bundle-100.bdr01.syd11.nsw.vocus.net.au - 0 | 699 | 699 | 34 | 37 | 98 | 36 |
|Bundle-Ether12.ken-edge903.sydney.telstra.net - 0 | 699 | 699 | 34 | 35 | 88 | 35 |
|bundle-ether17.ken-core10.sydney.telstra.net - 0 | 699 | 699 | 34 | 36 | 85 | 37 |
|bundle-ether1.oxf-gw10.sydney.telstra.net - 0 | 699 | 699 | 35 | 37 | 83 | 37 |
|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 699 | 699 | 35 | 37 | 85 | 36 |
| i-91.sydo10.telstraglobal.net - 0 | 699 | 699 | 35 | 36 | 84 | 35 |
| unknown.telstraglobal.net - 0 | 699 | 699 | 40 | 44 | 120 | 40 |
| 137.221.85.35 - 0 | 699 | 699 | 39 | 45 | 167 | 39 |
| et-0-0-0-pe04-eqsy4.as57976.net - 0 | 699 | 699 | 39 | 43 | 154 | 39 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 140 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~they really need to fix their matchmaking, getting put in singapore servers or na servers every single game
Every other game today. One game with 40 ping, the next with 250.
Asking the players, 10-11 are Aus/NZ while 1-2 are Asian countries. Which means we’re getting put on Singapore servers because there’s one Korean or similar.
1 Like
Yeah this has been an issue for me since Thursday if I can recall. The ping varies from about 150ms - 300ms, sometimes it’s a lot more stabe than others, but pretty much every time I get put into these games nearly everyone leaves / the game cancels.
Deathmatches weren’t being effected by this from what I noticed, until today where I got placed into some with much higher ping.
I’ve CTRL + SHIFT + N’d and each bad game I’ve had has been connecting to the PSE1 server, not LAX this time. But it has happened more with LAX in the past.
I find that these issues usually get resolved for a while/weeks, and then come back and last for days again.
…and it’s happening again/still.
This is inexcusable and Blizzard’s feeble attempts to pass this off as a temporary local/ISP issue are laughable.
Sure, there may be some congestion or packet loss on a single node in Australia, but there is no reason to route players to Singapore or LA servers. This is an oversight in the game’s matchmaking logic and needs to be fixed - it’s pretty obvious that anyone would prefer a 5-20ms ping with occasional lag spikes over a consistent 200ms ping.
Fix your game, Blizzard.
2 Likes
Same again for me, what this? the 3rd time now? in the last year or so. must be OW’s way of saying time to move on to another game.
350 ping when i’m normally 50 ping is the stuff that makes people do bad things.
Form NZ. with Vodafone. bah bah bah, same as last time. i change nothing at my end and this will be fixed in a week or two. In the mean time they just say it’s all because of something i did.
this is a A++ way to drive away your player base.
here New Zealand being forced to LAX1
its the same all over again.
1 Like
Those were some dark times
1 Like