MoQ Draft-21 Lands and the First Managed Relay Networks Go Live - What That Means for CCTV Games

The Media over QUIC working group published draft-21 of the core transport spec on 8 September. The same day, NetActuate switched on a managed MoQ Relay network across 45 locations. Cloudflare's MoQ relay fabric already runs on every one of its servers in 330-plus cities. The transport layer that our August piece called "the shape of the pipe in 2027" now has commercial relay networks live and a stable draft one revision short of Working Group Last Call.

That matters for CCTV Games in a very specific way. Every round of Rush Hour, Duck River, Snow Run and now Footfall is a race between the camera in the world and the phone in your hand. The June latency piece put the live dealer floor at 1.5 to 2.5 seconds glass-to-glass. CCTV Games ran sub-second because 155.io built the stack on WebRTC. MoQ is the path to keeping sub-second at genuine broadcast scale.

What changed in September

Two things. First, draft-ietf-moq-transport-21 was posted on 8 September and the working group document tracker now shows the WG Last Call target held at December 2026. The wire format has been stable since draft-18 in May, so any implementation coded against 18 or later is production-safe.

Second, the relay layer went managed. NetActuate's MoQ Relay announcement on 8 September puts single-feed-to-many delivery across 45 edge locations behind a paid product. That sits alongside Cloudflare's global MoQ relay, which runs on every server in 330 cities and treats the protocol as first-class alongside HTTP. Studios that were rolling their own SFU fleets now have an off-the-shelf option.

Why the relay model fits the category

WebRTC scales linearly. Every extra viewer is another selective forwarding unit cost line. MoQ scales like a CDN. One feed hits an origin relay, fans out through edge relays, and each subscriber attaches to whichever relay sits nearest. For a category where 155.io's own dashboard puts platform-wide daily volume at about 59,000 rounds and an average round time of 38 seconds, per the studio's aggregator sheet, that cost curve is the difference between a viable price per round and one that fails at scale.

Ras Al Khaimah gets one thing extra out of this. The studio sits on a UAE hub chosen for jurisdictional and latency reasons, and the further the audience is from the origin the more a relay fabric earns its keep. A player in Lagos or Manila hitting a Cloudflare relay in-region rather than reaching back to a single Dubai origin is how you keep glass-to-glass under a second on a mid-range Android on 4G.

What to watch next

Working Group Last Call at the December IETF meeting. Once draft-21 clears, an RFC number follows and vendor lock-in on early forks stops mattering. WebTransport is now baseline in every major browser including Safari from iOS 26.4, per nanocosmos, so the receive side on the player's phone is already there. The remaining questions are commercial, not technical. Which relay networks win the aggregator contracts, and how quickly 155.io ports the CCTV Game pipeline off pure WebRTC to a MoQ track model. Neither will be quiet news.