The latest in a string of issues, Overwatch 2 error code LS-423 is another problem that seems to be linked to the queuing system, alongside the Overwatch 2 "in queue: 0 players ahead" error. but what exactly is the error, and how can you fix it?
These are the question we'll set out to answer in this article. But within particular issue, it might not be a simple one to resolve...
How to fix the “Time out communicating with Battle.net services” error
At the time of writing, this is one error that hasn't been addressed by Blizzard in their list of known issues. So there is no official fix for it at the moment.
And to compound matters, there doesn't appear to be any viable workaround for this error either. So what does this mean in practical terms? Well, essentially, if you get error LS-423, your only options are to give up, or to keep trying and remain patient.
It's worth stating that some players seem to get past this error eventually, so a bit of perseverance may be worthwhile. Additionally, there is a suggestion that the error seems to happen more frequently around the time that updates happen, or server maintenance is taking place.
If this is correct, then it's worth following the official @PlayOverwatch Twitter feed, as they will let you know of any scheduled updates or maintenance, and you can try to avoid playing Overwatch 2 at those times.
What is Overwatch 2 error code LS-423?
Players encounter this error when they are queuing to enter a game of Overwatch 2. After being in a queue for a while, they receive the message, "Time out communicating with Battle.net services. (LS-423)”. Players are then forced to rejoin the queue and often find themselves at the back as a result.
It's unclear exactly why this issue is happening, but the best guess at the moment is that it is linked to problems with server stability and traffic levels.
With Overwatch 2 being a relatively new game, traffic spikes are much more likely, than compared to a game that has been out for a while. This can cause servers to struggle to cope with the volume of traffic, leading to errors.
If the root cause is indeed down to server capacity and stability, then we'd expect this error to become less frequent as traffic starts to stabilise. But we won't know for certain for some time.
Overwatch 2 has, unfortunately, got off to a rocky start in terms of errors and player experience. Hopefully, they will begin to get a handle on more of these problems, so that players can finally start enjoying the game without running into multiple issues.