The particular error is likely related to bad connections, during the connection with a server we pass a few bits of information back and forth during the handshake phase. During the handshake we’re also determining if a player has a good enough latency to play on a given server (our system can support latencies up to 500ms which is actually very high for a networked game). If your latency is above our maximum you’d get a message saying that the connection isn’t good enough.
In this case I think your latency is likely spiking quite a bit (maybe just contended routing from your isp to our servers, maybe some amount of dropped packets). The initial timing thinks you have an acceptable latency but then during connection the latency spikes very high or there’s a sequence of dropped packets meaning a particular part of the handshake takes a lot longer than expected (in this case I think it’s taking your client more than 4 secs to send a single packet of data to the server, i.e. more than 8x longer than we measured your latency to be). In those situations we just drop the connection with an error and let the client attempt a reconnect.
Now I think this error can only occur during the handshake which means it shouldn’t really be able to happen to a world your actually stood on, this means it shouldn’t be a hard error pulling you out to the error screen but just an error on the portal. We’ll have to try and take a look at why it could happen like this and kick you out the game vs just not opening the portal.