n0-computer announced Noq today—a QUIC implementation that solves two problems plaguing peer-to-peer networking: multipath support and production-grade NAT traversal. Already running at scale (200,000+ concurrent connections via iroh), Noq is the first implementation to handle both robustly. This matters because P2P systems rely on expensive relay infrastructure—WebRTC needs TURN relays for 10-15% of connections—and Noq’s approach reduces that dependency dramatically.
The Two Problems
QUIC is the UDP-based transport protocol replacing TCP, the foundation of HTTP/3. It offers multiplexing and built-in TLS, but standard QUIC can’t use multiple network paths simultaneously. Your phone has Wi-Fi and cellular. Your laptop might connect through a relay and directly. QUIC sees one path. When you switch networks, the connection drops. When you could aggregate bandwidth, you don’t.
NAT traversal costs money. 82% of devices sit behind NAT or firewalls. P2P systems use STUN to discover public IPs and TURN to relay traffic when hole-punching fails. TURN works for 10-15% of WebRTC connections—mostly cellular networks and restrictive enterprise Wi-Fi—but adds latency and bandwidth costs. Running TURN infrastructure at scale is expensive. P2P isn’t really peer-to-peer when 10-15% of your traffic flows through relays you pay for.
Before Noq, iroh (n0-computer’s distributed systems toolkit) was “doing a lot of heavy lifting around QUIC: switching between relay and direct paths, managing NAT traversal, juggling congestion state.” QUIC couldn’t see these operations. Apps hacked around the limitations. It worked, but barely.
Noq’s Technical Breakthrough
Noq implements the IETF multipath QUIC specification, making paths first-class QUIC concepts instead of application-level workarounds. Before Noq, iroh managed paths “as a kind of sleight of hand below the QUIC layer.” QUIC was blind to multiple paths. Congestion control treated relay and direct connections identically. Path switching required hacks—”congestion controller resets” to force QUIC to behave.
With multipath as a native QUIC feature, the protocol maintains per-path congestion control, makes intelligent routing decisions, and handles path failures gracefully. “Latency improvements we had to hack in via congestion controller resets are now handled correctly and systematically,” per the Noq announcement.
NAT traversal moves from below QUIC to inside QUIC. Hole-punching becomes a QUIC-level operation. The congestion controller sees NAT traversal. Loss detection improves. The team claims Noq is “the first to do this in a production-grade, robust way.” QUIC Address Discovery (QAD) replaces STUN with an encrypted alternative—no more unencrypted public IP discovery.
Why Hard Fork Quinn?
Quinn is a pure Rust async QUIC implementation founded in 2018. It’s solid, widely used, and general-purpose. But iroh’s needs were “specific enough that a separate codebase, with collaboration where our interests overlap, is the honest path forward.” Multipath and NAT traversal required architectural changes Quinn wasn’t designed for. Rather than burden Quinn’s maintainers with fundamental redesigns, n0-computer forked.
The team emphasizes this is “in no way a rejection of Quinn, which remains a great implementation.” Noq and Quinn continue collaboration—Noq tests interoperability against picoquic, the IETF reference implementation. This is a respectful fork, not a hostile split.
Real-World Impact
Noq isn’t vaporware announced today and deployed never. It’s been powering iroh since v0.96, tested at 200,000 concurrent connections with millions of devices deployed. Production scale, not lab experiments.
Cost savings: TURN relay bandwidth costs disappear for connections that now succeed via direct NAT traversal. Reduced infrastructure dependency. Lower service costs. iroh’s case study: “200k concurrent connections and millions of devices on the same network with low service costs.”
Use cases:
- P2P file sharing: IPFS alternatives. GuardianDB migrated from IPFS to iroh for better performance and large file handling.
- Real-time collaboration: WebRTC alternatives for video conferencing and collaborative editing without mandatory relay infrastructure.
- Blockchain and crypto: Node-to-node communication for decentralized apps where reliability matters more than hype.
- Edge computing: IoT device communication, distributed AI training where centralized cloud infrastructure doesn’t make sense.
Compared to WebRTC, Noq offers simpler architecture and better NAT traversal. Compared to IPFS, iroh (powered by Noq) handles large files efficiently—terabytes, not just kilobytes. Compared to other QUIC implementations, Noq is the only production-grade multipath + NAT traversal combo.
Why Multipath QUIC Matters Now
Users switch between Wi-Fi and cellular constantly. Traditional QUIC drops the connection. Multipath QUIC transitions seamlessly. Better user experience, especially for mobile apps that can’t afford dropped connections during network changes.
5G and Wi-Fi can run simultaneously. Multipath QUIC aggregates bandwidth from multiple interfaces. High-bandwidth apps—video streaming, large file transfers—benefit immediately.
The decentralization movement (Web3, blockchain, decentralized apps) needs reliable P2P infrastructure. Noq provides the foundation. Less reliance on centralized cloud providers. Better privacy. Lower costs. P2P systems that actually work without expensive relay infrastructure.
QUIC adoption is growing—8.9% of websites as of April 2023, up from 5% in March 2021. HTTP/3 is built on QUIC. As QUIC matures, multipath extensions follow. Noq is ahead of the curve: production-grade today while the IETF multipath spec is still a draft.
Key Takeaways
- Noq implements multipath QUIC and production NAT traversal, the first to do both robustly
- Already deployed at scale: 200,000+ concurrent connections, millions of devices via iroh v0.96+
- Reduces reliance on expensive TURN relay infrastructure (10-15% of WebRTC connections currently require relays)
- Multipath QUIC enables seamless network transitions (Wi-Fi to cellular) and bandwidth aggregation
- Hard fork of Quinn with continued collaboration, driven by architectural needs specific to P2P systems
- Production-proven today while IETF multipath spec is still in draft, positioning Noq ahead of broader industry adoption
