Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.streampixel.io/llms.txt

Use this file to discover all available pages before exploring further.

If a viewer’s stream is laggy, blurry, or won’t connect at all, the network is the most common culprit. This page lists exactly what needs to be reachable for Streampixel to work well — share it with your IT team or network admin when you need firewall changes.

​
Required ports

Open the following ports outbound from the viewer’s network:
PortProtocolPurposeTLSRequired
3478UDPTURN — primary media pathNoYes
3478TCPTURN fallbackNoYes
443TCPTURN over TLSYesYes
5349TCPTURN over TLSYesYes
10000 – 60000UDPDirect peer connection to rendering nodesNoOptional
UDP 3478 is the most important port. If it’s blocked, WebRTC media falls back to TCP, which adds head-of-line blocking and significantly degrades stream quality — expect blurriness, frame drops, and higher latency. Always open UDP 3478 first.

​
About the optional UDP 10000–60000 range

This range is not required for streaming to work — it’s an optimization. When these ports are open, the viewer can establish a direct peer-to-peer connection to the rendering node instead of routing media through a TURN relay server. The result is lower latency, since media takes one fewer hop. If the range is blocked, the connection still completes — it just goes through the TURN relay (UDP 3478). For latency-sensitive use cases (interactive games, simulations, VR), opening this range is worth the effort. For most other workloads, the relay path is fine.

​
Why UDP matters

WebRTC is designed around UDP. Video frames are time-sensitive — a packet that arrives late is worse than a packet that’s dropped, because TCP will retransmit the late packet and stall every frame behind it. UDP just keeps moving. When UDP is blocked, the SDK falls back to TURN-over-TCP (port 3478 TCP, then 443/5349 over TLS). Connections still complete, but you’ll see:
  • Increased latency — typically +50 to +200 ms
  • Pixelation and motion blur during congestion
  • Dropped frames instead of graceful bitrate adaptation
  • Choppy audio under load
If your audience includes corporate, hospital, or hotel networks, ask their IT team to allow UDP 3478 outbound.

​
STUN / TURN IP ranges

Streampixel uses Twilio’s global STUN/TURN infrastructure. To allow these IPs through restrictive firewalls, or to apply Quality of Service routing, allow the ranges below.
Whitelist all Twilio regions, not just the one closest to you. Twilio routes connections to the nearest healthy edge dynamically — if the closest region is unavailable or congested, your traffic may be served from another region. Limiting the allow-list to a single region causes connections to fail when failover happens.
CIDR blockIP lower boundIP upper boundAddresses
3.25.42.128/253.25.42.1283.25.42.255128
13.210.2.128/2713.210.2.12813.210.2.15932
54.252.254.64/2654.252.254.6454.252.254.12764
CIDR blockIP lower boundIP upper boundAddresses
18.230.125.0/2518.230.125.018.230.125.127128
18.231.105.32/2718.231.105.3218.231.105.6332
177.71.206.192/26177.71.206.192177.71.206.25564
CIDR blockIP lower boundIP upper boundAddresses
18.156.18.128/2518.156.18.12818.156.18.255128
18.195.48.224/2718.195.48.22418.195.48.25532
52.59.186.0/2752.59.186.052.59.186.3132
CIDR blockIP lower boundIP upper boundAddresses
3.7.35.128/253.7.35.1283.7.35.255128
52.66.193.96/2752.66.193.9652.66.193.12732
52.66.194.0/2652.66.194.052.66.194.6364
CIDR blockIP lower boundIP upper boundAddresses
3.249.63.128/253.249.63.1283.249.63.255128
54.171.127.192/2654.171.127.19254.171.127.25564
52.215.127.0/2452.215.127.052.215.127.255256
52.215.253.0/2652.215.253.052.215.253.6364
CIDR blockIP lower boundIP upper boundAddresses
13.115.244.0/2713.115.244.013.115.244.3132
18.180.220.128/2518.180.220.12818.180.220.255128
54.65.63.192/2654.65.63.19254.65.63.25564
CIDR blockIP lower boundIP upper boundAddresses
13.229.255.0/2713.229.255.013.229.255.3132
18.141.157.128/2518.141.157.12818.141.157.255128
54.169.127.128/2654.169.127.12854.169.127.19164
CIDR blockIP lower boundIP upper boundAddresses
3.235.111.128/253.235.111.1283.235.111.255128
34.203.250.0/2334.203.250.034.203.251.255512
34.203.254.0/2434.203.254.034.203.254.255256
54.172.60.0/2354.172.60.054.172.61.255512
CIDR blockIP lower boundIP upper boundAddresses
34.216.110.128/2734.216.110.12834.216.110.15932
44.234.69.0/2544.234.69.044.234.69.127128
54.244.51.0/2454.244.51.054.244.51.255256
These ranges are managed by Twilio and may change. If you maintain a strict allow-list, re-check the official Twilio documentation periodically.

​
Quick checklist for IT teams

If a stream isn’t working from a corporate or restricted network, ask the network admin to confirm:
  • UDP port 3478 outbound is allowed (most important)
  • TCP ports 443, 3478, and 5349 outbound are allowed
  • The Twilio IP ranges for all regions are not blocked (Twilio fails over between regions, so a single-region allow-list is not enough)
  • WebRTC is not disabled at the browser policy level (some enterprise browsers disable it)
  • The dashboard domain (dashboard.streampixel.io) and your project’s stream URL are reachable
  • (Optional, for lower latency) UDP ports 10000–60000 outbound are allowed — enables direct peer connection to the rendering node instead of relaying through TURN
If all of the above are open and streams are still degraded, contact support with a stream-stats sample (see Diagnosing stream quality).

​
Next

Troubleshooting

Diagnose blurry streams, connection failures, and audio issues.

Performance tuning

Hit your latency, FPS, and bitrate targets.