HTTP/3 Won Quietly and Most Graphs Still Say TCP

HTTP/3 has been 'coming' for so long that a lot of teams missed the part where it arrived. Chrome, Safari, Firefox, Cloudflare, Fastly, and the big CDNs speak QUIC by default. That means a request that used to be TLS over TCP is now UDP with its own congestion control, and a packet loss no longer stalls every stream on the connection the way head-of-line blocking did.

The operational hangover is that a lot of monitoring still assumes TCP. Retransmit graphs, SYN-scan alerts, and middleboxes that 'help' by inspecting packets all see less of what they used to. QUIC encrypts almost everything, including the bits operators liked to peek at. When a site feels slow, the useful numbers are now handshake time, 0-RTT acceptance, and whether a corporate firewall is falling back to HTTP/2 because it dropped UDP/443.

This is not a reason to rip out TCP metrics. Plenty of APIs and internal services still speak HTTP/1.1. It is a reason to stop treating a clean TCP graph as proof the edge is healthy. If the browser is on HTTP/3 and your packet capture is looking for TCP RSTs, you are debugging a protocol the client already left.