HTTP/3 is the latest HTTP version that runs over QUIC (on UDP), providing multiplexed streams with built-in TLS 1.3 and connection migration to avoid TCP head-of-line blocking and improve performance.
HTTP 3.0
HTTP/3 is the newest major version of the Hypertext Transfer Protocol, standardized as RFC 9114, and it is the same standard tracked under this HTTP 3.0 entry. It preserves familiar HTTP semantics while replacing the underlying transport with QUIC, which runs over UDP and eliminates the connection-level head-of-line blocking that constrained TCP-based versions.
- QUIC over UDP - Independent streams mean a single lost packet no longer stalls unrelated requests sharing the connection.
- Encryption by default - TLS 1.3 is integrated into the transport, so there is no unencrypted mode to fall back to.
- Reduced handshake latency - Transport and cryptographic setup are combined, with 0-RTT resumption trimming round trips for repeat clients.
- Connection migration - Sessions persist across network changes, such as switching from Wi-Fi to cellular, without a fresh handshake.
In practice, API teams adopt HTTP/3 by enabling it at the CDN or gateway edge rather than rewriting services, since the request and response semantics stay identical to HTTP/2 and HTTP/1.1. Its resilience to changing networks makes it a strong fit for mobile clients and the long-running, streaming connections that increasingly define agentic API consumption.
Referenced on the API Evangelist blog
Where this standard shows up across sixteen years of my writing at apievangelist.com — how it fits into API design, governance, and the agentic turn.
