---
title: "Discussion on \"STUN vs TURN: Why Every WebRTC Call in TinyFloor Goes Through a TURN Server\" | Hashnode"
description: "Discussion on \"STUN vs TURN: Why Every WebRTC Call in TinyFloor Goes Through a TURN Server\". Peer-to-peer almost never connected for us, so our calls are relay-only: UDP first, on Cloudflare's managed TURN, with voice sent twice."
url: "https://hashnode.com/posts/stun-vs-turn-webrtc-turn-server/6ae24079cfb50b3e84f39aa9"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [STUN vs TURN: Why Every WebRTC Call in TinyFloor Goes Through a TURN Server](https://tinyfloor.hashnode.dev/stun-vs-turn-webrtc-turn-server?utm_source=hashnode&utm_medium=feed)

Peer-to-peer almost never connected for us, so our calls are relay-only: UDP first, on Cloudflare's managed TURN, with voice sent twice.

Oct 28 · 8 min read · tinyfloor.hashnode.dev  
Read the article

-   [#webrtc](https://hashnode.com/tag/webrtc)
-   [#cloudflare](https://hashnode.com/tag/cloudflare)
-   [#networking](https://hashnode.com/tag/networking)
-   [#javascript](https://hashnode.com/tag/javascript)

## Written by

[Jitto Joseph](https://hashnode.com/@jittojoseph)

@jittojoseph

  
[View profile](https://hashnode.com/@jittojoseph)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
