Check the connection and look back at it later
See which route is checked before sending and which one was actually used afterwards.
You need
A pending or finished transfer in the web app.
The info icon in Your connection opens the details of the pre-check. If direct is not confirmed yet, keep the receiver open and use Check connection again. A failed check does not mean that the server route has already been used.
After a transfer, look at the connection details in the history. What matters is the method actually used, the attempts and any switch. Direct can mean WebRTC or, for native clients, another named method. Sharing a Wi-Fi network alone does not prove the route.
Under Settings → Transfer routes you can set Allow automatic switch through pipeit for new transfers. With Connect directly only, pipeit never switches to the server route. If direct is not possible, the transfer stays pending or fails, and the history says so.
Related guides
Direct, server route and routed networks: which way works?
What “direct” really means, when pipeit routes through its servers and what you can check.
Solve transfer problems
Check the specific problem instead of starting over: a quick decision list and the common symptoms with their next step.
- Command line and servers
Check the direct route and set the fallback
Probe a direct route, choose a route per transfer and control the account-wide fallback.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.