Weird connection issue

Game lags out just about every match, player characters and all abilities stop being tracked. However i am still able to access the chat and hear voice communications, the game boots me from the lobby before having me rejoin and the issue resolves.
Things I have tried:
-Flushed my dns and released/rebooted my IP
-Switched from a wired connection to a wireless connection
-Switched to a different wifi network
-Uninstalled the game on steam and reinstalled it
-Installed the game through the battlenet launcher
-Uninstalled and reinstalled my wifi drivers
-Updated all other drivers on my PC
-Switched out this motherboard for a known good one in case it was a wifi card issue
Other things to note:
This is the only game that this occurs in, I have no issues in other titles
I am actually at a loss

You are likely experiencing a problem with your route to the server. Not everything you connect to is hosted in the same place, so the pathway to the game may have outages/maintenance happening. Unfortunately, Blizzard staff (not me, I don’t work there) can’t address how you connect to the game beyond offering you troubleshooting tips. Any connection issue should be worked on with your network admin or ISP. For additional information, the game servers are hosted by Google, so your ISP can run a trace to their Las Vegas and Chicago locations.

ran a tracert on the server i get connected too and it does look a bit strange unfortunately im at a loss of whats happening here, any ideas
Tracing route to 24.105.40.0 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms TMO-G4SE lan [My IP]
2 <1 ms <1 ms <1 ms 192.0.0.1
3 21 ms 14 ms 14 ms 192.0.0.1
4 84 ms 14 ms 19 ms 192.0.0.1
5 32 ms 17 ms 20 ms 192.0.0.1
6 18 ms 14 ms 14 ms 192.0.0.1
7 17 ms 14 ms 14 ms 10.160.107.146
8 28 ms 16 ms 19 ms 10.177.57.132
9 28 ms 23 ms 24 ms 10.164.179.171
10 23 ms 27 ms 27 ms 10.180.64.9
11 55 ms 42 ms 49 ms 10.164.179.192
12 37 ms 45 ms 23 ms 10.177.9.196
13 28 ms 28 ms 24 ms 10.164.162.255
14 25 ms 24 ms 34 ms 10.177.5.203
15 25 ms * * 10.164.178.193
16 29 ms 29 ms 53 ms eqix-dc2.blizzard com [206.126.237.174]
17 47 ms 49 ms 49 ms ae1-br01-eqdc2.as57976 net [137.221.72.33]
18 * * * Request timed out.
19 51 ms 46 ms 49 ms et-0-0-0-pe01-evch1.as57976 net [137.221.69.81]
20 49 ms 57 ms 49 ms 137.221.67.63
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.

Trace complete.

That test looks quite normal, those timeouts are nodes that ignore ICMP requests (what Traceroute is using).

You’re better off with an app like WinMTR or PingPlotter.

From what im able to discern its pretty standard other than some minor packetloss up until the 10.164.178.193 interchange where it kinda just goes kaput, guessing this is a private server before routing through to blizzard. My best guess is theres a possibility that the backbone on that server is just not the best, not sure if a VPN would be able to bypass that specific node

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

Host - % Sent Recv Best Avrg Wrst Last
TMO-G4SE.lan - 0 152 152 0 0 17 0
192.0.0.1 - 0 152 152 0 0 13 0
192.0.0.1 - 2 145 143 13 17 36 13
192.0.0.1 - 3 137 133 13 20 49 13
192.0.0.1 - 3 137 133 13 21 52 15
192.0.0.1 - 0 152 152 13 21 99 15
10.160.107.146 - 0 152 152 15 22 95 19
10.177.57.132 - 0 152 152 15 23 99 23
10.164.179.171 - 0 152 152 25 32 94 30
10.180.64.9 - 0 152 152 23 31 100 26
10.164.179.192 - 0 152 152 24 32 103 30
10.177.9.196 - 0 152 152 25 33 99 28
10.164.162.255 - 2 144 142 23 31 205 26
10.177.5.203 - 0 152 152 24 33 95 29
10.164.178.193 - 56 47 21 0 30 40 35
eqix-dc2.blizzard com - 0 152 152 28 38 101 32
ae1-br01-eqdc2.as57976 net - 0 152 152 46 55 110 66
No response from host - 100 30 0 0 0 0 0
et-0-0-0-pe01-evch1.as57976 net - 0 152 152 47 55 89 48
137.221.67.63 - 0 152 152 48 55 96 52
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
No response from host - 100 30 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Unfortunately, a lot of latency is coming from T-Mobile’s network. I forgot to mention that a 5G connection doesn’t meet the system requirements for Overwatch because it relies on line-of-sight technology. You may be either wired in or wirelessly connected to T-Mo’s device, but the device itself relies on bouncing between communication towers to reach the internet. Additionally, this type of internet is optimized for users browsing the web, social media, and videos. T-Mobile often deprioritizes gaming traffic on their network in favor of saving bandwidth for their other customers partaking in those activities. If you’re wondering how I know this, I worked in telecom for over a decade — and still work in an adjacent field.

Yeah i figured as much after looking into it, its a shame because the best standard internet connection in my area offers 12mbps for 100/mo while TMOBILE gets me 800+ mbps for 50/mo. Thinking ill see what i can do about getting a standard connection for gaming while keeping the TMOBILE line for downloading purposes. Appreciate all the help

1 Like

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