Just popping in here to let y'all know I'm working with Dakoda via PM since we're doing some additional investigating and gathering network information.
I was doing some investigation earlier with a member from our IT department to see what our network path was like from our studio to one of our servers, and it's very possible that due to the way ISPs set up their paths from source to destination the connection could be timing out at a certain part of the path or have a high latency, which could result in a "failure" to reach the servers.
It's been awhile since I've done in-depth network support, so I'd like to discuss it further with our network engineer before getting too in the weeds of speculation without a proper map, and to start brainstorming possible adjustments we could make on our end that may be more forgiving in these particular cases.
As for the client update we've been working on, that shouldn't impact any player's ability to make the initial connection and is focused on improving the experience once the player is connected and actually in-game. We've already pushed out the server-side portion of that update, and hope to have the client side vetted by QA in the next day or two so we can deploy it soon! To reiterate, though, I don't think it'll have an impact on those experiencing this particular error.