Global MoQ Relay Network for Low Latency CMAF
GeoDNS routing via relay.moqcdn.net — Cloudflare geo-steers to the nearest pool
| SLC | Salt Lake City | US Central |
| LAX | Los Angeles | US West |
| VIR | Virginia | US East |
| PAR | Paris | Europe |
| NCR | Delhi | Asia South |
| SNG | Singapore | SE Asia |
| TOK | Tokyo | Asia East |
| SPA | São Paulo | South America |
| ORD | Chicago | US Central |
| LAX | Los Angeles | US West |
| NWJ | Newark | US East |
| PAR | Paris | Europe |
| MAA | Chennai | Asia South |
| SNG | Singapore | SE Asia |
| TOK | Tokyo | Asia East |
| SPA | São Paulo | South America |
Go to the Dashboard and sign in with Google or Discord. Create a broadcast namespace.
moqpush is the open-source MoQ publisher. It takes CMAF via DASH-IF Ingest input from your encoder and publishes to any MoQ relay.
# Clone and build
git clone https://github.com/erikherz/moqpush-open.git
cd moqpush-open
cargo build --release -p moqpush-app
Use the Push Key from the Dashboard to authenticate and publish to the moqcdn relay network:
# Start moqpush-app with your managed key ./target/release/moqpush-app \ --push-key mpk_YOUR_PUSH_KEY \ --tracks 3v1a \ --target-latency 200
moqpush-app authenticates with moqcdn.net, gets a JWT and relay assignment for your namespace, and starts listening for CMAF via DASH-IF Ingest.
Configure your encoder (e.g. Ateme Titan Live, FFmpeg + GPAC) to push CMAF segments via HTTP PUT to:
http://your-server:9078/ingest/
Once init segments arrive, moqpush-app connects to the assigned relay and begins publishing. Edge relays pull the stream via gossip for global distribution.
See the FFmpeg + GPAC setup guide for encoder configuration.
Your stream is live! Share the link with anyone:
https://moqcdn.net/my-stream
Viewers get low latency playback via Shaka Player and WebTransport in a browser.
16 relay PoPs across Google Cloud and Akamai in North America, Europe, South America, and Asia. GeoDNS routing with per-namespace relay selection.
MoQ over QUIC/WebTransport delivers low latency streaming with WebSocket fallback.
Standard DASH-IF CMAF ingest over HTTP PUT.
Live publisher and player metrics, per-region warm status, and real-time dashboards.
Share a link and anyone can watch in their browser.
QUIC is always TLS 1.3 end-to-end. CMAF DRM is supported.
Traditional ABR protocols buffer 6-30 seconds of content, making true live interaction impossible. MoQ Transport delivers media over QUIC streams with low latency while maintaining broadcast-scale reliability — no trade-off required.
Unlike TCP-based protocols (RTMP, HLS, DASH), QUIC provides independent stream multiplexing. A lost packet on one video track doesn't stall audio or other tracks. Each media stream flows independently through the connection.
QUIC's Connection ID replaces TCP's fragile 4-tuple. Streams survive WiFi-to-cellular handoffs, NAT rebinding, and IP changes seamlessly — the connection just keeps going. Critical for mobile and field production.
Unlike push-based protocols (WebRTC, SRT, RTMP) that stream constantly regardless of viewers, MoQ only transmits tracks when explicitly subscribed. Bandwidth-efficient by design — critical for satellite, cellular, and constrained networks.
When bandwidth drops, MoQ doesn't blindly drop frames like WebRTC. Subscriptions carry priority levels — the QUIC library transmits packets in priority order. Low-res streams and audio survive while high-res feeds gracefully degrade.
QUIC mandates TLS 1.3 and encrypts packet headers — even packet numbers. No middlebox interference, no ISP throttling, no protocol ossification. Uses UDP port 443 for universal firewall traversal.
Unlike TCP (locked in OS kernels), QUIC runs in userspace. Apps ship their own implementation with modern congestion control (BBR) without waiting for OS updates. Deploy improvements instantly across all platforms.
MoQ is not theoretical — it's been deployed in production, proving real-world reliability in harsh network conditions.