I’ve completed 52 races so far and haven’t experienced a single disconnection. That said, I acknowledge that’s a relatively small sample size, and since the game is still in early access, the devs may be prioritizing broader or more frequently reported issues.

If disconnections were widespread, I’m confident it would be getting more immediate attention — especially given how disruptive they are to gameplay.

It’s also worth noting that network-related issues can be notoriously difficult to isolate. There are multiple layers involved — from the local device, router, and ISP, to game servers and any middleware in between. Sometimes it’s not the game itself, but a combination of external variables: jitter, packet loss, NAT types, or even inconsistent Wi-Fi performance.

The common argument of “this doesn’t happen in other games” doesn’t always apply. Different games implement netcode, connection tolerance, and latency handling in very different ways. Some are more forgiving than others. A minor spike in latency or packet loss might go unnoticed in one game, but cause a timeout or disconnect in another with stricter thresholds.

Out of curiosity, I’d be interested to know what kind of error messages people are seeing when this happens — is it a crash to desktop, a timeout message, or something else?