Hi folks,
While reading this guide on launching WebRTC services from BlogGeek, I noticed it recommends using a third-party commercial TURN service. While that may feel a bit disappointing, it's probably a practical choice for many who just want to launch their product without getting bogged down in infrastructure details.
That got me thinking—what are these commercial TURN providers actually using? I did a bit of digging and here’s what I found:
Twilio NAT Traversal: Clearly based on coturn. It's not even hidden—you can see it in the STUN responses via the SOFTWARE tag.
Cloudflare TURN: Appears not to use coturn. Error messages and nonce sizes differ from typical coturn behavior.
Based on this, here are a couple of action items I'd like to explore in the coming months:
Improve our documentation so fewer developers feel forced to rely on third-party TURN services.
Learn from what others are doing. For example, I just noticed that Cloudflare doesn’t send a response phrase in certain cases—a good mitigation against amplification attacks we’ve discussed on the issue tracker.
Curious to hear your thoughts:
What are other providers doing? Any best practices we should adopt? Feedback is welcome!
And if you're working on WebRTC products, that free guide from BlogGeek is worth a look—some solid insights in there.
Best regards,