Well basically the Title. I just started to play during the Even a bit again and figured that i get put on LA Servers (LAX1) while i’m from Germany. I always played NA (because i mostly play night time and EU is meh anyway) and 99% of the time it worked (~100 Ping).
But recently no matter what i get put onto West Coast which gives me like a Ping of 200ms.
Yes I tried flushing DNS, restarting Modem/Router yada yada.
So any other Tips or ideas?
Choosing the North America region can place you on either server based on player availability for the mode or rank you’re queuing for in game. All players in North America can land on either, as well.
i get that but i doubt that during peak hours in NA there are no Players on East/Central Region for Ranked for at least 3 weeks now.
And with Peak i mean literally 6-7-8-9 in the Evening/Afternoon Eastern Time.
It is more likely this is a routing issue. When you log onto Overwatch for a specific global region, the game takes time to ping the datacenters for that region and that helps determine which datacenter you will typically connect to. This gets awfully complicated to troubleshoot when you are deliberately playing out of region, however the typical workaround is usually using a VPN service. (Please note, Blizzard does not provide direct support for VPNs so be prepared for other possible technical issues if you choose to use one).
yea not going to pay for VPN, I rather stop playing then (at least for now). Today the Ping is also 330ms instead of like 200. Well…
I’m a player living in Europe who often plays on NA servers as most of my friends who play are from the US. Recently (roughly since a month or so ago) I noticed that every time I play, I only ever get placed on the west coast server and never on central. I tried to ping the central server through both cmd.exe and WinMTR - on cmd.exe I simply get repeating lines of “Request timed out.” and on WinMTR I get “no response from host” somewhere in the process. I asked a few of my friends from the US if they were able to ping the central server IP and they were able to without issue, while my EU friends ran into the same issue I was having with the “Request timed out.” error. I was wondering, has something recently been changed that means players from outside the US are no longer able to connect to Overwatch’s central NA server anymore?
Another player reported this recently, and it’s likely some sort of routing issue as the connection hops across the ocean. Unfortunately, when selecting the Americas, it’s acceptable and normal to land on either server (players in Florida can land on the Los Angeles server frequently). While I understand that isn’t the desired result when connecting from so far away, it doesn’t seem like an issue tech support can help with since both Americas servers are working, and it’s a routing issue (outside Blizzard’s control) causing you to land on the other server.
Hey you two,
I merged your threads together since you were both reporting the same thing and it sounds like a routing issue. I can’t guarantee I can help with it, and technically WyomingMyst is right, you’ll likely need a VPN to work around it, but usually this is a problem only if your connection to the central server would be worse than the connection to the LA server
If you’re still having this problem, please create a WinMTR test while you are unable to play on the central server. Here’s the IP you want to use for central for the host.
24.105.41.50
Run the test for about 5 minutes like this. Then make another test using the IP of the server you are actually on. To get that, in game press Ctrl+Shift+N and use the IP in the top right to run the test. More information on how to format this is in the winMTR link above.
Once you have both tests, post them here and I’ll see if I can see why this is happening. If you have problems with posting them 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
~~~~Hi there. So after more testing it looks like I am actually able to connect to the central servers, but I’m getting the same ping on them as I do on the west coast servers, which wasn’t the case until a few weeks ago. My west coast ping hasn’t changed (still getting 160ms), but now I also get 160ms on central when I used to get 110-120.
WinMTR test for the IP you provided:
WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| OPENWRT - 46 | 116 | 63 | 0 | 1 | 15 | 1 |
| 90.246.0.1 - 46 | 116 | 63 | 4 | 6 | 15 | 5 |
| 63.130.104.202 - 46 | 116 | 63 | 6 | 7 | 15 | 6 |
| ae5-100-xcr1.man.cw.net - 27 | 159 | 117 | 5 | 6 | 15 | 7 |
| ae21-xcr1.ltw.cw.net - 44 | 120 | 68 | 11 | 12 | 23 | 14 |
| ae32-xcr2.nyk.cw.net - 24 | 167 | 127 | 79 | 81 | 122 | 80 |
| eqix-ix-ny8.blizzard.com - 44 | 120 | 68 | 79 | 84 | 168 | 80 |
| ae1-br01-eqny8.as57976.net - 26 | 159 | 118 | 148 | 328 | 2740 | 328 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-1-pe02-eqch2.as57976.net - 23 | 171 | 132 | 148 | 151 | 245 | 149 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 66 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR test for the server I connected to in game:
WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| OPENWRT - 18 | 174 | 144 | 0 | 1 | 15 | 1 |
| 90.246.0.1 - 32 | 131 | 90 | 4 | 6 | 15 | 7 |
| 63.130.104.202 - 32 | 131 | 90 | 6 | 7 | 15 | 7 |
| ae5-100-xcr1.man.cw.net - 29 | 137 | 98 | 5 | 7 | 15 | 6 |
| ae21-xcr1.ltw.cw.net - 17 | 178 | 149 | 11 | 12 | 28 | 11 |
| ae32-xcr2.nyk.cw.net - 32 | 131 | 90 | 79 | 81 | 97 | 92 |
| eqix-ix-ny8.blizzard.com - 32 | 131 | 90 | 79 | 84 | 134 | 92 |
| ae1-br01-eqny8.as57976.net - 32 | 131 | 90 | 148 | 238 | 753 | 148 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-1-pe02-eqch2.as57976.net - 32 | 131 | 90 | 148 | 152 | 201 | 150 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 59 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
IP provided by Drakuloth:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| fritz.box - 0 | 169 | 169 | 0 | 0 | 6 | 0 |
| ip5b41aafe.dynamic.kabel-deutschland.de - 0 | 169 | 169 | 8 | 12 | 82 | 10 |
| ip53a9b42e.static.kabel-deutschland.de - 0 | 169 | 169 | 8 | 11 | 35 | 10 |
| 83-169-156-149.static.superkabel.de - 0 | 169 | 169 | 8 | 10 | 22 | 22 |
| 145.254.3.66 - 0 | 169 | 169 | 8 | 11 | 19 | 13 |
| 145.254.2.215 - 0 | 169 | 169 | 13 | 17 | 84 | 17 |
| 145.254.2.215 - 1 | 165 | 164 | 0 | 16 | 76 | 16 |
| ae9-100-xcr1.hac.cw.net - 0 | 169 | 169 | 12 | 16 | 84 | 15 |
| ae9.pcr1.aet.cw.net - 1 | 165 | 164 | 0 | 23 | 47 | 21 |
| ae20-xcr2.nyk.cw.net - 0 | 169 | 169 | 97 | 101 | 123 | 111 |
| eqix-ix-ny8.blizzard.com - 0 | 169 | 169 | 98 | 104 | 157 | 101 |
| ae1-br01-eqny8.as57976.net - 0 | 161 | 161 | 166 | 368 | 2740 | 282 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-1-pe04-eqch2.as57976.net - 0 | 169 | 169 | 164 | 169 | 274 | 166 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 34 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Ingame
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| fritz.box - 0 | 195 | 195 | 0 | 0 | 4 | 0 |
| ip5b41aafe.dynamic.kabel-deutschland.de - 0 | 195 | 195 | 7 | 12 | 52 | 11 |
| ip53a9b42e.static.kabel-deutschland.de - 0 | 195 | 195 | 7 | 11 | 26 | 10 |
| 83-169-156-149.static.superkabel.de - 0 | 195 | 195 | 7 | 10 | 17 | 10 |
| 145.254.3.66 - 1 | 191 | 190 | 0 | 12 | 65 | 10 |
| 145.254.2.215 - 0 | 195 | 195 | 12 | 16 | 24 | 16 |
| 145.254.2.215 - 1 | 191 | 190 | 0 | 16 | 22 | 13 |
| ae9-100-xcr1.hac.cw.net - 1 | 191 | 190 | 0 | 16 | 42 | 14 |
| ae9.pcr1.aet.cw.net - 1 | 191 | 190 | 0 | 24 | 50 | 20 |
| ae20-xcr2.nyk.cw.net - 0 | 195 | 195 | 97 | 102 | 136 | 100 |
| eqix-ix-ny8.blizzard.com - 1 | 191 | 190 | 0 | 106 | 198 | 98 |
| ae1-br01-eqny8.as57976.net - 0 | 188 | 188 | 158 | 351 | 3061 | 2610 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-3-br02-eqla1.as57976.net - 0 | 195 | 195 | 160 | 176 | 380 | 243 |
| be3-pe02-eqla3.as57976.net - 0 | 195 | 195 | 157 | 163 | 260 | 160 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 39 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hey there,
Thanks for following up with us and for providing these tests! It does help us greatly in identifying the source of things like this. The test you have listed as in-game is showing slightly faster connection times than the IP drak gave you so it makes sense why the game is putting you on that server.
The biggest thing to keep in mind here is that the connection is having to cross the ocean. In order to get to the Americas servers the connection has to go through these Equnix nodes in New York. By that time it’s already at 100+ latency so almost all of the trip time is through that under sea cable. The journey to the individual game servers is only adding 50-60 ms on top of that which is relatively inconsequential. 50-60 connecting from NY to LA or Chicago is fairly normal.
Overall there may be no way to bypass the issue since the root issue is the jump under oceans/seas. Most internet service provider will not have alternate ways to route players between countries since options are limited.
Hope the info helps. Cheers!
So in the last Weeks the under sea cable changed their mind in regards of speed (or whatever) and suddenly gives me a 70ms higher Ping than in the past 4 years?
Like i said there is a difference playing with 220+ms or 120ms.
Unlikely it’s the cable, more likely to be the Equinix nodes that Kaldraydis mentioned above.
But in the end, Blizzard has no control over that portion of your connection, so any issues with it would need to be worked out with the ISP and the routing peers they have contracts with for service. Routes are often changed and/or optimized (not always for the best), so that may be the cause of the new ping.