Queuing for comp and the card at the top of the screen says entering game. I can talk in match and team chat but it doesn’t actually enter the game. ‘Failed to connect to server’ appears in the chat, even while I am actively talking to people in the match chat, then I get hit with a suspension and an additional loss, even though I was unable to enter the game in the first place.
Looking through the forums, every post like this gets the same reaction, either ignored completely or just sent straight through to another page about how suspensions will never be repealed for connection issues. I don’t even want a repeal, I just want to know if this will ever be fixed or if I will continue being constantly slammed day after day with suspensions and unfair losses. There is no way in hell that thousands and thousands of people can all get the same issue failing to connect to servers and have all of the issues be client side.
The voice server and match server are not the same connection. This separation is why some people can play the game but can’t connect to voice chat if their ISP is blocking VOIP.
Connection troubleshooting has always been a courtesy service, which is the common approach I’ve noticed across other AAA titles. Keeping the server online with their hosting companies is their top priority. Blizzard Customer Support (not me, I’m a volunteer) may only be able to look at basic networking data to figure out the issue each player is experiencing, since they don’t work for the ISPs and aren’t residential network technicians. If you’re lucky, a network test may show an obvious error. However, U.S. players may encounter an issue with throttling due to a lack of net neutrality (meaning any ISP can throttle any service whenever they want), and the erratic throttling makes the problem hard to spot.
Well, players don’t create posts in tech support unless they run into an issue. But in many cases, the problem is a routing issue between the ISP and the routing peer. In most countries, many ISPs rely on the same routing peers to complete their connection route. There are a handful that run into problems constantly, and there is nothing the ISP customer can do other than complain and hope the ISP will push it up the ladder and investigate.
I’m having the same issue with PS5, the problem is that sometimes it works and sometimes I get the error “failed to connect to server” just before getting into the game. This only started to happen after the new patch.
It never kicked me out once I get matched but only when matchmaking is over it loads and suddenly shows this error. In my friends screen they see me in game and leaving but for me I never get past the “game had been found” when this issue happens.
Today especially is the worst, I’m barely able to play consistently.
Edit: I forgot to mention that when this happens, I can’t even spectate. I’m from the UAE and my friends are all in Japan. This doesn’t happen when I play alone but I hope the issue will be solved.
ISP Here…
Currently having issues with Overwatch2 players getting “failed to connect to server”, but not one can provide the server IP to which the session is trying to join. The only help Blizzard (peering support) has been is to tell us that it is a GCP server and that they can’t help because they aren’t Google and have instructed to push customers back to Customer Support to be provided with the Server IP information. But, so far it’s just been a circle of finger pointing. Doing a packet capture to look for the Server IP has produced IP addresses that are registered to Blizzard but none to Google.
If someone from Blizzard Support reads this, it would be nice to get a reply with an email address or phone number of a department that can provide this information.
Around 10pm EST last night (Australia), I started getting stuck at the “Entering game” login screen thing. I’ve been playing for years with a very stable connection, no change to set-up, power-cycled my router, still happening…
All Blizzard services (including this site!) take minutes to load each page. But YouTube will buffer 4k in a few seconds.
Weirdest part (and this might be a clue) is that if I turn on Cloudflare WARP, I can technically connect albeit with a fair dose of latency. It has to be set to “1.1.1.1 with WARP” mode. Using the other mode simply called “1.1.1.1” won’t work by itself.
I flagged the issue with my ISP and they confirmed they can see the weird-ness on their end as well (a speedtest yielded 0.9 down and 0.4 up!) even though YouTube is loading big streams instantly. Something very weird is going on.
Edit: Confirmed, running Cloudflare WARP makes even this site load instantly. Bizarre routing issue?
Ok, so I used the PC version of Overwatch, as Battle.net allows to change regions there.
Asia region is disconnecting (doesn’t let me login at all) while the other regions are fine although in terms of Ping, Asia is lower than America for me.
Any idea when do they usually do server maintenance? hoping the issue is just temporary and that eventually it will be fixed
But I’m afraid that the game will be region locked in which I won’t be able to play with my friends anymore
Edit: my friend can spectate my game and join if there’s a leaver. I can’t spectate them but sometimes it seems like it matches us like usual. Also, we tried many other online games and some has options to select Asia region and all is working fine except for overwatch. I hope the server get fixed soon.
I have changed entire ISPs. The problem persists. I’ve just accepted that I have an unknown amount of time playing the game before another crazy suspension. I have no way of changing the fact that I will just be dced so I’ll just take it until I get like a month suspension.
It’s very frustrating indeed, I’m still having the issue. Btw, it’s not the first time either although it looks a bit different than last time but I’m sure it has to do with their end as I tested playing with my friends on other games and there’s no issues matching in different regions.
Last time we get some response in one of the threads and soon after the issue had been resolved. I would say it took 1 or 2 weeks max. Unfortunately now, we have no way of knowing how long it will take to fix the issue. There’s also the possibility that when next patch/ server maintenance occurs hopefully the issue will be resolved.
