QUIC
lastmod 2026-03-22created 2019-11-1515 edits
QUIC (pronounced 'quick') is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google, implemented, and deployed in 2012, announced publicly in 2013 as experimentation broadened, and described to the IETF. While still an Internet Draft, QUIC is used by more than half of all connections from the Chrome web browser to Google's servers. Most other web browsers do not support the protocol.
Implementations
See also
- UDP
- HTTP3
- MoQ CDN (Cloudflare) - QUIC-based media delivery
- Media over QUIC (MoQ)
Favorite site
- Wikipedia (en) QUIC
- QUIC protocol - QUIC (Quick UDP Internet Connections) protocol
- QUIC (Quick UDP Internet Connection) concepts
- Is QUIC the alternative to HTTP for the web in the 5G hyper-connected era?
- Why did HTTP/3 choose UDP?
- (Facebook Engineering blog translation) How to handle billions of traffic with QUIC
- CUBIC and HyStart++ support in quiche
Article/News
- Starting as Google QUIC and going through about 5 years of IETF standardization, QUIC version 1 has finally been formalized as RFC 9000.
- The current state of HTTP/3
- Google Chrome starts supporting HTTP/3 and IETF QUIC
- Firefox starts supporting QUIC and HTTP/3
- 75% of Facebook traffic now uses QUIC and HTTP/3
- How to handle billions of traffic with QUIC (translation)
- Why did HTTP/3 choose UDP?
- Performance comparison of HTTP/3 and HTTP/2
- QUIC is not quick enough over fast internet | GeekNews
- Why HTTP/3 is widely supported but rarely used in practice | GeekNews
- QUIC for the Linux kernel | GeekNews - The first patch to officially integrate the QUIC protocol into the Linux kernel has been submitted
- Firefox's Rust-based fast UDP I/O | GeekNews
- About 20% of Firefox's HTTP traffic uses HTTP/3, which runs on top of QUIC and UDP
- Replaced the existing network I/O layer NSPR with the Rust-based quinn-udp, strengthening performance and memory safety