Failed to connect to server

Hi, I can’t connect to any overwatch in game server. I can log in to game server and I can see main menu. I can search for games but it never connects with error of “Failed to connect to server”. I tried two different PC its same. However I can connect with “vpn service (cloudflare WARP)”. I contacted my ISP and they said following

"Hello;

When checked, access to the server is provided with ideal values. After server access, the management of security rules belongs to the company that manages the server, there is no blocking or restriction by us, access to the server is provided.

Regards."

So here I am asking for any help.

Also here is my winmtr report of “185.60.114.159” I couldn’t find ingame server ip to trace only found this ip and I believe it is log in server. It might be irrelevent but here I am pasting the results anyway :slight_smile:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
HGW.LOCAL - 0 232 232 0 0 1 0
100.64.0.1 - 0 232 232 1 1 3 1
10.9.8.1 - 0 232 232 1 1 3 2
10.0.254.17 - 0 232 232 1 3 65 2
reverse.comnetnetwork - 0 232 232 2 44 274 75
No response from host - 100 47 0 0 0 0 0
00-atakoy-sr14s-t2-2—00-yenibosna-t3-2.statik.turktelekom - 0 232 232 1 2 3 2
00-gayrettepe-sr14s-t2-2—00-atakoy-sr14s-t2-2.statik.turktelekom - 5 197 188 2 2 4 2
No response from host - 100 47 0 0 0 0 0
302-ams-col-2—00-ebgp-gayrettepe-k.statik.turktelekom - 98 48 1 0 61 61 61
80.249.208.83 - 0 232 232 49 53 110 50
ae1-br02-eqam1.as57976 - 2 197 194 58 433 4479 173
et-0-0-3-br02-eqpa4.as57976 - 0 232 232 55 66 219 62
et-0-0-1-pe02-eqpa4.as57976 - 1 228 227 55 56 77 55
137.221.66.35 - 0 232 232 56 56 58 57
185.60.114.159 - 0 232 232 55 56 58 56
________________________________________________ ______ ______ ______ ______ ______ ______
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

What should I do in order to fix this?

1 Like

If you can connect with a VPN and not your standard home internet, then the problem is either with the ISP or the routing they use to reach the server. The routing can be controlled by a third party internet company they pay for service.

In the test, I don’t see any obvious errors, but I’m not familiar with that IP. This doesn’t mean it’s the wrong IP. I don’t work at Blizzard so my knowledge comes from the IPs listed on the support documentation. Which region server do you normally connect to?

Are you from usa? It’s happening to me too.

Doubtful, as they are connecting through Turktelekom in their network test.

If you’re having issues, start your own thread and include test data.

I am from Turkey but problem persist on every region. Including America. Previous tracert was with login server I believe. I got training game server via vpn and did tracert with my normal connection. Here is the result.

C:\Users\QuantetOSH2>tracert 34.151.239.19

Tracing route to 19.239.151.34.bc.googleusercontent [34.151.239.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms KEENETIC-2584 [192.168.1.1]
2 2 ms 1 ms 1 ms 100.64.0.1
3 2 ms 1 ms 1 ms 10.0.254.17
4 60 ms 298 ms 24 ms mx960_a1–i533–q10k2_1–mx1_a2.comnet[46.31.76.87]
5 12 ms 9 ms 9 ms sofia_mx1_a0–i522–q10k2_2–yenibosna_mx960_a2.comnet [46.31.76.199]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
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 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I am playing in the USA and not experiencing any connection problems, so I don’t think that’s true.

Those hops are timing out before the connection leaves the country, so it does seem like there is an ISP problem occurring.

Thank you for response. I did another tracert and it seems connection can get away from country at hop nr:14

ISP doesn’t help me at all and they insist that it is not in their hands. What should I do?

Tracing route to 64.224.27.25 over a maximum of 30 hops

1 4 ms 3 ms 3 ms 104.28.0.0
2 * * 4 ms 8.25.249.1
3 38 ms 38 ms 40 ms 86.106.122.125
4 25 ms 71 ms 26 ms trktelekomintat-ic-371936.ip.twelve99-cust[213.248.86.99]
5 29 ms 26 ms 25 ms win-b2-link.ip.twelve99 [213.248.86.98]
6 25 ms 27 ms 25 ms win-bb2-link.ip.twelve99 [62.115.114.182]
7 * * 40 ms ffm-bb2-link.ip.twelve99t [62.115.138.22]
8 44 ms 46 ms 46 ms prs-bb2-link.ip.twelve99 [62.115.122.138]
9 44 ms 45 ms 44 ms prs-b1-link.ip.twelve99 [62.115.125.167]
10 45 ms 47 ms 83 ms blizzard-ic-348624.ip.twelve99-cust [62.115.178.205]
11 143 ms 86 ms 92 ms ae1-br02-eqpa4.as57976 [137.221.77.35]
12 * * * Request timed out.
13 * * * Request timed out.
14 51 ms 56 ms 49 ms 137.221.78.51
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.