Help Center
Pairio connects two Macs directly when it can. Some company networks block that, and then the call goes through a relay instead. If calls don’t connect at work, send this page to your IT team.
pairio.app on TCP 443.turn.cloudflare.com on UDP 3478 and 443, and TCP 3478, 80, 5349 and 443.turn.cloudflare.com.pairio.appstun.l.google.comstun1.l.google.comstun.cloudflare.comstun.services.mozilla.com
turn.cloudflare.com*.ingest.de.sentry.io
Allow turn.cloudflare.com by its name if your firewall can.
If it only takes addresses, allow all four that Cloudflare uses for it:
141.101.90.1,
162.159.207.1,
2a06:98c1:3200::1 and
2606:4700:48::1.
Cloudflare may change them. It changes the name first, and asks you to update a list of addresses within 14 days. See Cloudflare’s questions and answers on its relay.
Calls are end-to-end encrypted between the two Macs. The relay passes the encrypted packets on and cannot read them. It runs on Cloudflare’s network, at the Cloudflare location closest to each Mac.
A firewall that decrypts and re-encrypts TLS traffic breaks the relay on ports 5349 and 443, because Pairio accepts only the relay’s own certificate. Add turn.cloudflare.com to the exceptions.
Pairio connects to the relay directly, never through a web proxy. If traffic can leave your network only through a proxy, let turn.cloudflare.com bypass it.
Start a call from inside your network. If it connects, you’re done.
If Pairio says it couldn’t connect, email us with roughly when you tried. We can see how the call tried to connect, and we’ll tell you what was blocked.
Choose which cookies you'd like to accept. Your preferences are saved for one year.
Essential for the website to function. Includes session cookies for authentication and security.
Help us understand how visitors interact with our website. No advertising or remarketing.