Update 5, 4:15 pm PDT: More players survived the queues and started playing Overwatch 2, but it seems that many people are having problems. Blizzard has not provided any further updates either.
Update 4, 2:15 pm PDT: The Overwatch 2 server queues and errors don’t seem to have been fixed, but I found that if you click the globe icon on the Battle.net launcher next to the game version down and change it to Asia, you can log in immediately.
Update 3, 1:40 pm PDT: Blizzard is experiencing a DDoS attack, according to a Blizzard president Mike Ybarra (opens in a new tab)Which is probably one of many reasons the Overwatch 2 servers are struggling.
Update 2, 1:20 pm PDT: Overwatch 2 servers are still unstable. Players are kicked from games to the menu and out of the game entirely. The login screen also sometimes shows “Queued: 0 players ahead of you” and messages about connecting to the game server.
Update: The “unexpected server error” messages that some players are getting when trying to log into Overwatch 2 are being “actively processed,” according to tweet from Blizzard CS (opens in a new tab). The message appears to be an error (opens in a new tab) for people who have linked their console and PC Battle.net accounts.
Original story: Overwatch 2 servers started coming online a little earlier than the expected 12 pm PDT launch time (opens in a new tab)but if you’re having trouble logging in, you’re not alone.
If you preloaded Overwatch 2 and downloaded a small update today, you can press the play button and try to enter. I’ve watched livestreamers on Twitch successfully get to the Quick Play menus and queue, but there are quite a few who haven’t. ‘t, including me.
There are thousands of people in line—I’ve seen the number climb to 40,000 (yes, really)—and the login page spits out messages like “unexpected error” sending you to the back of the line or “lost connection to game.” server.”
There is currently no workaround for this error. The Blizzard Twitter customer support (opens in a new tab) account hasn’t mentioned it yet. This seems a likely result of the servers running early and having issues with how many people are trying to log on. All you can do now is keep trying to log in or wait patiently for the right launch.
We will update this story as this issue continues.