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

[Hippie-1713]

Hey all, My ping has come down from the original 170-180ms mark, however, it seems to fluctuate from its normal 16-18ms all the way up to 90ms. This seems intermittent and doesn’t have a pattern from what I can see. I have lodged a ticket with iiNet in the hopes they can find something. Below are the WinMTR results for tonight.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |  679 |  679 |    0 |    0 |    5 |    0 |
|                          150.101.42.200 -    0 |  679 |  679 |    1 |    1 |    9 |    1 |
|                 ae10.cr1.cbr2.on.ii.net -    0 |  679 |  679 |    1 |    2 |   38 |    1 |
|                 be12.cr3.syd7.on.ii.net -    0 |  679 |  679 |    5 |    5 |   13 |    6 |
|                be-50.cr2.syd7.on.ii.net -    0 |  679 |  679 |    5 |    5 |   15 |    6 |
|                  ae6.cr2.syd4.on.ii.net -    0 |  679 |  679 |    5 |    7 |   90 |    6 |
|                   57976.syd.equinix.com -    0 |  679 |  679 |    6 |    9 |  117 |    6 |
|        et-0-0-49-br01-eqsy4.as57976.net -    0 |  679 |  679 |    6 |   12 |  142 |    6 |
|         et-0-0-0-pe02-eqsy4.as57976.net -    0 |  679 |  679 |    5 |    8 |   84 |   10 |
|                          137.221.66.135 -    0 |  679 |  679 |    6 |    6 |   15 |    7 |
|                             37.244.40.1 -    0 |  679 |  679 |    6 |    6 |   17 |    7 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[DivideByZero-11756]

I mean a simple ping test on their end and matches us to a low ping server would fix all this but it doesn’t seem like Blizzard would even entertain that thought

That’s how it works already. It looks at the last hop where your ping came from. So let’s say your ISP routed you into the Netherlands, it would connect you to Europe because the last hop is close to the European server.

I’m really confused why it’s implemented in this way and I feel the point I was making is somewhat confused.

A few packets can be sent to a player and if that takes .5 seconds (or whatever the threshold may be) to return because I’m connecting to some overseas server then just don’t put me in a game. It’s pointless playing the game with pings that high, no one has fun, often I can’t even communicate with teammates because of a language barrier and it seriously degrades the competitive nature of the game.

This can be achieved in a client as simple as a web browser why can blizzard not implement this simple check? rather than just running with the ping to whatever hop was last used which seems like a pretty poor implementation and doesn’t always give any true representation of the ping the player might experience. Services should be predictable and going of the last hops ping is just not predictable if you cannot be sure what the end users real ping might be.

Furthermore a simple oceanic Region option would help with this and allow further matchmaking diagnostics on Blizzards end if we’re being put in overseas servers.

[GiantEgg-1494]

This is true. even in a game connected to syd where you ping seems fine it can go ll the way up to 120 and back down again from one second to the next. I’ll try to capture this at some point.
This is from 5min ago, pretty much constant high ping.
iinet, geelong GMT+10

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  618 |  618 |    0 |    0 |    2 |    0 |
|                              172.22.0.1 -    0 |  618 |  618 |    3 |    7 |   19 |    7 |
|            be21-450.cr2.mel10.on.ii.net -    0 |  618 |  618 |    5 |    8 |   22 |    8 |
|                be51.cr2.mel11.on.ii.net -    0 |  618 |  618 |   14 |   18 |   35 |   19 |
|                 be55.cr3.syd2.on.ii.net -    0 |  618 |  618 |   14 |   18 |   33 |   18 |
|                 ae15.cr1.syd4.on.ii.net -    0 |  618 |  618 |   14 |   18 |   34 |   21 |
|                  ae3.cr2.syd4.on.ii.net -    0 |  618 |  618 |   15 |   18 |   32 |   17 |
|                   57976.syd.equinix.com -    0 |  618 |  618 |   14 |   22 |  108 |   17 |
|        et-0-0-49-br02-eqsy4.as57976.net -    2 |  579 |  569 |   45 |  132 |  254 |  161 |
|         et-0-0-0-pe02-eqsy4.as57976.net -    1 |  611 |  609 |   21 |  129 |  234 |  115 |
|                          137.221.66.135 -    0 |  618 |  618 |   14 |   18 |   30 |   18 |
|                             37.244.40.1 -    0 |  618 |  618 |   13 |   18 |   35 |   21 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[Airbag-1353]

If that can help… I’m from Mauritius. Usually I connect to EU (~200ms) (US ~300ms) (asia - forget about it)
For the past 24hrs I’ve been getting EU (~310ms), US (~250ms)
That’s how I found out for EU I’m connecting to Amsterdam server instead of CDG Paris and on US I’m on Singapore instead of US east.
Don’t care so much about US but how can I force connect to CDG? That’s all I ask. I have very little time (Dad of 2 babies/ 2 jobs) and now I’m having to trouble shoot in my little spare time…

[Whisper-11285]

Can someone explain this to me as I’m not tech savy but it seems way too much of a coincidence so I just need an explanation. I don’t have problems with any other games, at all, at any time. No ping spikes, no anything.

Then 11 or so days ago, I can’t connect to HotS games. Game is ready, can’t connect, error. At the same time OW players also start having issues. Blizz solve this problem, but I continue to have ping issues. They say it’s about traffic, but I get it 3am on a weekday.

Can someone explain how this possible and somehow just a coincidence? Wouldn’t it affect me in more ways than to just one game?

[Drakuloth]

There’s a couple good questions here I wanted to address, although we’re going to need more of the information I requested to dig into this more deeply for you all. It sounds like for at least some of you, the behavior changed.

The reason this is only affecting Overwatch for you all is that you’ll be taking a different route to our servers than most any other service or game you play. The internet is kind of like a system of highways, and we expect there’s a traffic jam on the information highway to us. Meanwhile the roads to say, google, or other games, are clear. There’s more information in our common issues sticky for this - under the FAQs.

The reason you’ll sometimes end up on the wrong server is that while you’re queuing for a match of whatever type, the game will ping your computer to see what your latency is. It does this from multiple different servers, and the pings will happen at different times. So what you can end up with in a situation where a part of the internet is getting clogged is this.

The Sydney server pings you, and there’s a problem with the internet between you and us. Say it’s 300 ms or so because of that problem at that point in time.
Los Angeles pings you and sees you have a ping of 180 ms. Better, but not quite what we’re after.
Now the Singapore server pings you, and it sees about 130 ms because the problem with the internet wasn’t flaring up when that ping happened.

130 MS is less than 300, so you end up on Singapore servers (or whichever server has the lowest ping test at the time.) It’s a bit more complicated than this, but that’s the simplified version of how it works.

It’s designed this way intentionally to get you the best connection it can at any given time without insane queue times. Obviously if you end up on the Sydney servers it doesn’t particularly matter while this problem is happening - the latency problem will still be coming and going so you’ll get spikes of latency there too. This is why we’re focusing on trying to find the cause of the issue. As long as it’s happening, there’s a likelihood that no matter what server you end up on, you’re going to have a bad experience, and that’s what we want to try to diagnose and avoid.

If you have suggestions for other ways to handle this, we welcome that feedback, but that’s better for the general forums. Here, we’re focusing on the tech aspect of things so that we can try to help you all resolve the underlying issue in whatever form that takes.

We still need more tests to narrow this down. For those of you having the high latency, or ebbing and flowing latency, please continue following the steps here and posting tests. Remember: when you run the test the problem needs to be actively happening so we can see the issue in the test! The more info we get to compare the more likely we can narrow down the cause.

[G4L3XY-1711]

Previously Australian servers were on PSE2 (AWS Server) now theyre on SYD2 (Equinix Server) My thoughts are that maybe Equinix’s infrastructure in australia isnt quite as good as the AWS servers I have included a WinMTR for both PSE2 (AWS) and SYD2 (Equinix) below as you will see the routing to the AWS is much cleaner and doesnt appear to be triggering hops to telstraglobal which as far as I know is telstras international links.

PSE2

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

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

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

|                             192.168.1.1 -    0 |   18 |   18 |    0 |    0 |    2 |    0 |

| gateway.qb51.townsville.asp.telstra.net -    0 |   18 |   18 |    5 |    7 |   29 |    5 |

|                         144.130.213.209 -    0 |   18 |   18 |   20 |   20 |   23 |   20 |

|bundle-ether6.cha-core4.brisbane.telstra.net -    0 |   18 |   18 |   21 |   22 |   24 |   22 |

|bundle-ether20.ken-core10.sydney.telstra.net -    0 |   18 |   18 |   35 |   35 |   38 |   36 |

|bundle-ether1.ken-edge901.sydney.telstra.net -    0 |   18 |   18 |   34 |   35 |   37 |   35 |

|              ama1663225.lnk.telstra.net -    0 |   18 |   18 |   34 |   35 |   38 |   34 |

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

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

|                            52.95.37.199 -    0 |   18 |   18 |   35 |   36 |   42 |   36 |

|                             52.95.36.43 -    0 |   18 |   18 |   34 |   37 |   51 |   43 |

|                          54.240.192.239 -    0 |   18 |   18 |   35 |   37 |   68 |   35 |

SYD2

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

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

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

|                             192.168.1.1 -    0 |  321 |  321 |    0 |    0 |    2 |    0 |

| gateway.qb51.townsville.asp.telstra.net -    0 |  321 |  321 |    4 |    6 |   37 |    5 |

|                         144.130.213.209 -    0 |  321 |  321 |   20 |   20 |   35 |   21 |

|bundle-ether6.cha-core4.brisbane.telstra.net -    0 |  321 |  321 |   20 |   22 |   36 |   21 |

|bundle-ether20.ken-core10.sydney.telstra.net -    0 |  321 |  321 |   34 |   35 |   41 |   36 |

|bundle-ether1.oxf-gw10.sydney.telstra.net -    0 |  321 |  321 |   35 |   36 |   46 |   37 |

|bundle-ether1.sydo-core04.sydney.reach.com -    0 |  321 |  321 |   35 |   36 |   42 |   36 |

|           i-91.sydo10.telstraglobal.net -    0 |  321 |  321 |   35 |   35 |   41 |   35 |

|               unknown.telstraglobal.net -    0 |  321 |  321 |   36 |   40 |  118 |   38 |

|        et-0-0-48-br01-eqsy4.as57976.net -    0 |  321 |  321 |   35 |   40 |  161 |   38 |

|         et-0-0-0-pe02-eqsy4.as57976.net -    0 |  321 |  321 |   36 |   38 |  107 |   37 |

|                          137.221.66.135 -    0 |  321 |  321 |   36 |   36 |   44 |   37 |

|                             37.244.40.1 -    0 |  321 |  321 |   35 |   36 |   44 |   36 |

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

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

As you can see the “ama1663225” route seems to have a more stable latency than the TelstraGlobal hops.

If you do a search for “sydo10.telstraglobal” youll notice that the first page of google results are latency issues with World of Warcraft and Black Ops yet there are no other games mentioned.

So I dont exactly think this is a Blizzard or and ISP issue but a data centre issue within Equinix which I think would be up to blizzard to resolve as Blizzard is their customer.

[Whisper-11285]

The internet is kind of like a system of highways, and we expect there’s a traffic jam on the information highway to us.

But why is there a traffic jam at 3am? I can understand during prime time, but not late at night. Another question. I had traffic jam related issues with my ISP a few years back, during prime time, couldn’t play any games cause it would just spike, but the thing is, it always spiked. No matter what, the entire game was up and down, up and down. Start at 26, spike to 150, go down for a few seconds, spike up, spike down, nothing like what’s happening now.

Why does it spike in some HotS games I play and not others? How can I be in a 25 min game, where my ping doesn’t go below 150 (showing an OCE server with ctrl alt f), then the moment game ends, I requeue, and in under 5 mins I’m in a new game and my ping doesn’t go over 30? How did the traffic clear in that small amount of time but not the 25 min game? It isn’t a case of like, oh it just happened to disappear in that time. It’s a case of. The moment I get in the game, I’ll see myself go up to 150, play the 20 mins, play another, see I go to 25, stay there the entire game, play another, see myself go up to 150 and stay there.

This is for HotS and not OW. I’d ask in the HotS forums but here gets more responses.

Edit: On a good note, not a single bad game all night, 8 games, so thats nice.

[Arkfox-1270]

I thought my issue was resolved on the weekend but first chance to play this week and it’s back. I appear to be getting correctly matched to the SYD servers repeatedly but the lag issue has returned (170 - 300+ ms)

I Winmtr’d the server details from the server that it occurred on.

Is that still correct? i.e. 37.244.10.1 details at start of thread

iinet - Australia 8:30pm AEST

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 | 1356 | 1356 |    0 |    0 |    7 |    0 |
|                              172.22.0.1 -    1 | 1333 | 1327 |    3 |   25 |  441 |    5 |
|            be21-450.cr2.mel10.on.ii.net -    1 | 1333 | 1327 |    5 |   26 |  430 |    7 |
|                be51.cr2.mel11.on.ii.net -    1 | 1333 | 1327 |   14 |   37 |  446 |   18 |
|                 be55.cr3.syd2.on.ii.net -    1 | 1333 | 1327 |   15 |   37 |  443 |   19 |
|                 be50.cr2.syd2.on.ii.net -    1 | 1333 | 1327 |   14 |   36 |  445 |   16 |
|                 be51.cr2.syd7.on.ii.net -    1 | 1333 | 1327 |   15 |   37 |  445 |   18 |
|      syd-gls-har-wgw1-be-40.tpgi.com.au -    1 | 1333 | 1327 |   16 |   37 |  450 |   19 |
|  syd-gls-har-int1-hu0-3-0-3.tpgi.com.au -    1 | 1333 | 1327 |   16 |   41 |  454 |   18 |
|                  las-b24-link.telia.net -    1 | 1329 | 1322 |  159 |  184 |  591 |  160 |
|                  ash-bb4-link.telia.net -    1 | 1333 | 1327 |  214 |  237 |  642 |  219 |
|                  prs-bb3-link.telia.net -    1 | 1332 | 1326 |  303 |  324 |  735 |  307 |
|                   prs-b8-link.telia.net -    1 | 1333 | 1327 |  297 |  319 |  725 |  300 |
|   blizzard-ic-348624-prs-b8.c.telia.net -    1 | 1333 | 1327 |  299 |  323 |  730 |  302 |
|              ae1-br02-eqpa4.as57976.net -    1 | 1328 | 1321 |  304 |  344 |  849 |  308 |
|         et-0-0-3-br02-eqam1.as57976.net -    1 | 1330 | 1324 |  312 |  346 | 2520 |  317 |
|        et-0-0-67-pe01-eqam1.as57976.net -    1 | 1328 | 1321 |  334 |  359 |  761 |  338 |
|                           137.221.66.43 -    1 | 1332 | 1326 |  334 |  356 |  762 |  340 |
|                          185.60.114.151 -    1 | 1333 | 1327 |  305 |  327 |  734 |  308 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  271 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[G4L3XY-1711]

eqam1

Looking at this your routing is running through Telia which is a European ISP!!! also EQAM1 sounds alot like Equinix AM1 which is an Equinix data centre in Amsterdam!!! i swear these issues are caused by the new IP ranges we connect to for SYD2 are IP addresses registered in the netherlands. Blizz needs to just give us back Amazon Web Servers atleast those kinda worked.

[FLEXGOD-11722]

I have this issue aswell.
I lives in NZ and get 200-250 ms ping. Useless OW.

[Arkfox-1270]

Tonight’s games have been heavily affected. Strange thing is my ping has never gone over 100ms and for the most part and approx 60% of the match is playable. The other 40% is a rubberbanding mess.

This match was creeping up to 70ms and then would return to 40ish. The match prior stayed within the 40ish range the entire time however rubber banding still occurred halfway through the match with a massive spike that stopped the game dead in its tracks but did not kick me.

Usual data
ISP iinet
Australia
8-9pm AEST
All matched played in QP mode

|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   86 |   86 |    0 |   27 |  374 |   69 |
|                              172.22.0.1 -    0 |   86 |   86 |    3 |   36 |  375 |   68 |
|            be21.450.cr2.mel10.on.ii.net -    0 |   86 |   86 |    6 |   42 |  379 |   90 |
|                be51.cr2.mel11.on.ii.net -    0 |   86 |   86 |   16 |   58 |  392 |  123 |
|                 be55.cr3.syd2.on.ii.net -    0 |   86 |   86 |   16 |   58 |  391 |  122 |
|                 ae15.cr1.syd4.on.ii.net -    0 |   86 |   86 |   16 |   58 |  387 |  121 |
|                  ae3.cr2.syd4.on.ii.net -    0 |   86 |   86 |   15 |   58 |  387 |  140 |
|                   57976.syd.equinix.com -    0 |   86 |   86 |   16 |   61 |  387 |  117 |
|        et-0-0-49-br01-eqsy4.as57976.net -    0 |   86 |   86 |   16 |   63 |  393 |  122 |
|         et-0-0-0-pe02-eqsy4.as57976.net -    0 |   86 |   86 |   16 |   62 |  390 |  121 |
|                          137.221.66.135 -    0 |   86 |   86 |   16 |   59 |  388 |  119 |
|                            37.244.40.37 -    0 |   86 |   86 |   16 |   59 |  394 |  124 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   86 |   86 |    0 |   27 |  374 |   69 |
|                              172.22.0.1 -    0 |   86 |   86 |    3 |   36 |  375 |   68 |
|            be21.450.cr2.mel10.on.ii.net -    0 |   86 |   86 |    6 |   42 |  379 |   90 |
|                be51.cr2.mel11.on.ii.net -    0 |   86 |   86 |   16 |   58 |  392 |  123 |
|                 be55.cr3.syd2.on.ii.net -    0 |   86 |   86 |   16 |   58 |  391 |  122 |
|                 ae15.cr1.syd4.on.ii.net -    0 |   86 |   86 |   16 |   58 |  387 |  121 |
|                  ae3.cr2.syd4.on.ii.net -    0 |   86 |   86 |   15 |   58 |  387 |  140 |
|                   57976.syd.equinix.com -    0 |   86 |   86 |   16 |   61 |  387 |  117 |
|        et-0-0-49-br01-eqsy4.as57976.net -    0 |   86 |   86 |   16 |   63 |  393 |  122 |
|         et-0-0-0-pe02-eqsy4.as57976.net -    0 |   86 |   86 |   16 |   62 |  390 |  121 |
|                          137.221.66.135 -    0 |   86 |   86 |   16 |   59 |  388 |  119 |
|                            37.244.40.37 -    0 |   86 |   86 |   16 |   59 |  394 |  124 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[Zzzz-11629]

bump post. fix. there’s a lot of people with this issue. we do not care if the company thinks of you as some gaming company. just fix it.

[Zzzz-11629]

CAN WE GET A FIX THIS IS Bs. 3 days now. and no one seems to reply or even actually care about this.

[anon7402987]

A Force Server option is needed.

If you have this mechanic where it detects a high ping on a local server and so it goes to a distant server, that’s a silly mechanic. Going to a distant server guarantees a bad gaming experience. Being on a local server with a bad temporary connection is still temporary. So the better idea is to go to the local server ALWAYS.

So implement a Force Local Server option. This would put you to the local server (or the server of your choice) no matter the ping. THEN we can judge what the real problem is. As it is now, your method of selecting a server based on the ping here and now, regardless of location obfuscates the issue, making it difficult to get to the root cause of the problem.

[Zzzz-11629]

they won’t do it. apparently not enough people to care about this situation xd… my isp reset everything from their end for me and everything. nothing helped. Blizzard also said theyve been in contact with my isp which is a lie. considering i’ve asked. My isp said they have their priority set to low.

[Goop-11897]

Haven’t had any issues (like the ones we have all been experiencing) since the Summer games update… fingers crossed it’s back to normal now - for me at least!

[Zzzz-11629]

it’s fixed? or what …

[Boohda-1784]

Its obvious what Overwatch did, read the patch notes for the summer event. They did some server optimization and tracking in the patch, they obviously messed up the server route optimization. So even though you select NA server, it thinks for what ever reason you should be on the SA server, and nothing you do is going to change that. So your ISP routes you to that server which gives you insane lag and cuts you off of LFG. Bliz needs to at least acknowledge that this is their problem and that they are working on it. Because right now the only thing I have seen them say about it is “we think its a traffic jam with your ISP”. If your network/server team truly thinks that then fire them all, I can do much better by myself.