STATUS
Control Server Status
The control server coordinates remote peer discovery. It exchanges encrypted endpoint cards between MeshTalk clients and embeds a DERP relay for fallback connectivity. It never sees your messages or room secrets.
Server-Side Check
Checking…
- Status
- —
- Rooms
- —
- Connections
- —
- Endpoint
- —
Requested through this website: works even when the control server blocks cross-origin requests.
Client-Side Check
Checking…
- Status
- —
- Rooms
- —
- Connections
- —
- Endpoint
- —
Directly from your browser: fetches the control server's /health route.
What does the control server do?
Peer Discovery
When two MeshTalk clients are on different networks, they need a rendezvous point to exchange connection details. The control server facilitates this by holding encrypted endpoint cards — it never sees the plaintext contents.
DERP Relay
When direct UDP hole-punching fails (symmetric NATs, firewalls), the control server relays already-encrypted MeshTalk datagrams over its WebSocket connection. The server cannot decrypt this traffic.
Room Coordination
Named group chats use the control server to discover members. Only opaque room IDs and HMAC-derived capabilities are stored — room secrets never leave your device.
No Message Storage
All chat messages travel peer-to-peer. The control server is a signaling and relay layer only — it has no access to message content, file transfers, or encryption keys.