Gateway
ZeroVTT's relay service. It moves session state between players when their browsers can't reach each other directly.
Regions
| Region | Location | Typical latency | Status |
|---|---|---|---|
| eu-central | Frankfurt, DE | 18–42 ms | Operational |
| us-east | Ashburn, US | 24–55 ms | Operational |
| ap-southeast | Singapore, SG | 38–90 ms | Operational |
| sa-east | São Paulo, BR | 45–110 ms | Operational |
The app picks a region from your network's location. You can change it in Settings, under Connection.
Check your connection
The gateway answers on port 443 over HTTPS. If the check below fails, something between your network and this address is blocking the request.
How the gateway is used
ZeroVTT tries a direct connection between browsers first. Most tables never touch the gateway at all.
When a direct connection isn't possible — strict NAT, a mobile network, a corporate firewall — the session falls back to the gateway, which relays messages between the participants.
The gateway keeps a short replay buffer, so a player who drops can rejoin in the middle of a scene without asking the table to repeat itself.