Skip to main content
All Tools

TURN Server Tester

Test TURN server connectivity, latency and throughput by sending real data through a relay-only WebRTC connection. Enter your turn: URL, username and credential, or test the SpectrShare relay. Both test peers run in this browser, so the result measures the relay path from your device. It does not test connectivity between two separate networks.

Tests connectivity and throughput against the SpectrShare TURN relay. Sends up to 5 MiB in each direction, sequentially, using the same bulk channel settings as file transfers.

Slow transfers continue while data is arriving, up to five minutes per direction. The test stops after 30 seconds without data and keeps partial results. Live progress counts bytes received. You can cancel at any time.

How to test a TURN server

  1. Pick what to test. The SpectrShare TURN tab checks my relay with temporary credentials it fetches for you. The Custom Server tab is for a TURN server you run yourself, such as coturn.
  2. Enter the TURN URL, username and credential. The URL looks like turn:turn.example.com:3478, or turns:turn.example.com:5349 for TLS. Add ?transport=tcp to force TCP. A bare host:port gets turn: added for you. If your server uses coturn's use-auth-secret, the username is a timestamp and the credential is an HMAC generated from the shared secret, so paste a fresh pair.
  3. Run the test and watch the five phases: credential validation, TURN allocation, relay connectivity, round-trip latency and throughput. Both tests send up to 5 MiB per direction, sequentially, using reliable unordered 14 KiB chunks and the same flow control as file transfers.

For a wider walkthrough that covers STUN, NAT types and reading WebRTC internals, see the step-by-step guide to testing WebRTC connections.

What the results mean

Many TURN checks stop as soon as a relay ICE candidate shows up. A relay candidate proves the server is reachable, accepted your credentials and allocated an address. It doesn't prove the server will forward data. A server can hand out allocations all day while a firewall drops every packet on its relay ports.

So this tester goes further. It creates two peer connections in your browser, both forced to relay-only mode, opens a DataChannel between them through the server and pushes real data across. If the relay connectivity phase passes, your TURN server relays traffic. The latency and throughput numbers then tell you how well.

Where it fails tells you what to fix. A failure at allocation usually means a wrong URL or port, bad or expired credentials, or a server you can't reach. Allocation passing but connectivity failing points at blocked relay ports or a wrong external IP. Low throughput comes down to server bandwidth, distance to the server, coturn's max-bps cap, or transport: UDP is usually faster than TCP, while TCP and TLS can behave differently on networks that restrict UDP. The throughput average divides delivered bits by elapsed time. Each direction allows up to five minutes, stopping sooner after 30 seconds without data, with live received-byte progress, average speed and time remaining. A transfer that stops early is marked incomplete, with its received bytes, elapsed time and average speed preserved.

One limit to keep in mind: both ends of the loopback run on your machine, so the result measures the server's relay capacity from where you are, not the full path between two different clients.

TURN server FAQ

What is a TURN server?

A TURN (Traversal Using Relays around NAT) server relays data between two peers when they can't connect directly, usually because of a symmetric NAT or a firewall that blocks UDP. Without TURN, roughly 10-15% of WebRTC connections would fail outright. The cost is extra latency and lower throughput, since every byte passes through the server.

When is a TURN server needed?

Most WebRTC connections work directly or with STUN alone. TURN becomes necessary when one or both peers sit behind a symmetric NAT, a corporate firewall that blocks UDP, carrier-grade NAT on a cellular network, or a VPN that prevents direct connections.

Can I test a TURN server online without installing anything?

Yes. This tester runs entirely in your browser using RTCPeerConnection, so there's nothing to install. It works in Chrome, Edge and Brave. Firefox can't run it because two peer connections in the same tab hit a DTLS certificate collision.

Are my TURN credentials sent anywhere?

No. They're passed straight to RTCPeerConnection in your browser and aren't logged, stored, or sent to SpectrShare. The only traffic they're part of is the authentication with the TURN server you entered.

Why does my TURN server allocate but fail the relay test?

Allocation only proves the server accepted your credentials and handed out a relay address. If data then doesn't flow, the usual cause is a firewall blocking the server's relay port range (coturn uses UDP 49152-65535 by default), or an external-ip setting that advertises the wrong public address when the server runs behind NAT.

Related tools: WebRTC connection test, P2P speed test, SpectrShare connectivity check