Technology & Internet • Protocol

QUIC

QUIC is a transport-layer network protocol designed for fast, secure communication over the internet.

By Ethan Anderson| Reviewed by Olivia Bennett, Standards & Fact-Checking Lead| Updated July 26, 2026|2 min read| Fact-checked

QUIC is a transport-layer network protocol designed for fast, secure communication over the internet. It was originally developed at Google and later standardized by the Internet Engineering Task Force (IETF) as a UDP-based multiplexed and secure transport protocol. QUIC is now widely used in modern web browsers and HTTP/3 deployments, affecting everyday web performance and security.

History

QUIC was first implemented and deployed by Google in 2012 and publicly announced in 2013. It was later standardized by the IETF, with RFC 9000 defining the core protocol.

Design

QUIC is built on top of UDP and combines transport features with integrated security. Its design includes multiplexed streams, low-latency setup, flow control, and network path migration. QUIC integrates encryption and authentication as core protocol features, not as optional add-ons.

Relationship to HTTP/3

QUIC is the transport foundation for HTTP/3. This pairing is intended to improve web performance and reduce latency compared with traditional TCP-based approaches. HTTP/3 uses QUIC as its transport layer, making QUIC central to the latest major version of HTTP.

Adoption

QUIC is supported by major web browsers, including Chrome, Edge, Firefox, and Safari. Its deployment has made it an important part of modern web transport. QUIC matters to Canadian internet users because it is widely used in modern web browsers and HTTP/3 deployments, affecting everyday web performance and security on Canadian networks.

Key facts

QUIC is a general-purpose transport protocol that runs over UDP.
It provides low-latency connection establishment and flow-controlled streams.
QUIC integrates security features such as encryption and authentication into the protocol design.
It supports stream multiplexing and helps avoid head-of-line blocking.
QUIC includes support for connection migration and resilience to network path changes.

🍁

Canadian context

QUIC matters to Canadian internet users because it is widely used in modern web browsers and HTTP/3 deployments, affecting everyday web performance and security on Canadian networks.[2][5]

Frequently asked questions

What does QUIC stand for?

It originally stood for “Quick UDP Internet Connections,” but in IETF usage QUIC is treated as a name rather than an acronym.

What problem does QUIC solve?

QUIC was designed to reduce connection latency, improve performance for web traffic, and address limitations of TCP such as head-of-line blocking.

Is QUIC the same as TCP?

No. QUIC is a different transport protocol that runs over UDP and incorporates features that would traditionally be split between TCP and TLS.

Is QUIC encrypted?

Yes. QUIC includes encryption and authentication as core protocol features, not as optional add-ons.

What is HTTP/3’s role with QUIC?

HTTP/3 uses QUIC as its transport layer, making QUIC central to the latest major version of HTTP.

References

IETF — https://datatracker.ietf.org/doc/html/rfc9000
Supports: Core QUIC definition, transport features, low-latency connection establishment, flow control, path migration, and security.
Wikipedia — https://www.wikipedia.org/wiki/QUIC
Supports: History, Google origin, deployment date, public announcement, browser support, and acronym note.
IETF — https://www.ietf.org/archive/id/draft-hamilton-quic-transport-protocol-00.txt
Supports: Design properties including multiplexing, encryption, congestion control, and resilience to NAT rebinding.
F5 — https://www.f5.com/glossary/quic-http3
Supports: Relationship between QUIC and HTTP/3, UDP foundation, and integrated TLS/security.
Cloudflare — https://blog.cloudflare.com/the-road-to-quic/
Supports: Secure-by-default design, multiplexing behavior, and use of UDP datagrams.