# Connection information

The paired controller shows its route and measured round-trip ping. Open **Connection information** for the pairing method, transport, peer address and controller identity.

| Route | What it means |
| --- | --- |
| Local network | The phone connects to a reachable game or companion on the local network. This label does not assume the link is Wi-Fi; wired and tethered paths can also be local. |
| Game server | The phone connects straight to the game's own server. Our relay is not involved. |
| Peer to peer | An explicitly negotiated direct peer connection. The SDK has a WebRTC adapter; it requires the developer's signaling implementation and is not the default native-app transport. |
| Relay | A configured service forwards a session when permitted direct routes cannot be used. It must be allowed by the game policy. |
| Premium relay | A verified Pro participant sponsors an eligible session on the vendor's premium service. A label alone is not evidence that migration or routing has happened. |

The ordinary native and browser clients currently pair over JSON v1 WebSockets. The SDK's route registry supports additional adapters; a route is usable only when that client actually implements it.

## What ping measures

The client sends a timestamped message and measures the elapsed time when its reply arrives. The timestamp comes from a monotonic clock. The displayed value is a smoothed round trip to the connected endpoint, including its response time.

It does not measure the entire delay from touching the phone to seeing a game frame. A dash means no current sample is available. Reconnecting and degraded states replace the normal connected display; no latency number is invented.

The desktop companion also measures each phone from its side. The two readings can differ slightly because they are sampled at different times.

## Pairing method

An in-app camera scan is recorded as a QR scan. A pasted link or a link opened by another app is recorded as a join link. A browser cannot reliably tell whether an external link originally came from a camera.

## Route selection

Developers supply ordered routes and policy. A working developer/local path stays in use. Relay fallback is attempted only when allowed and when the earlier usable routes fail. Pro must not move a working direct session onto a relay.

An HTTPS browser page cannot open an insecure `ws://` connection to a local computer. Use a compatible secure endpoint, a native client, or the local HTTP browser path for base controls. Do not disable browser security checks.