Does one lost QUIC packet stop every HTTP/3 stream?
Not necessarily. QUIC tracks data by stream, so a stream that does not need the missing data can make progress. Streams still share connection-level congestion control and other resources, so independent delivery does not guarantee independent performance.
Answered in
HTTP/2 vs HTTP/3 Under Packet Loss: What QUIC Changes—and What It CannotCompare HTTP/2 over TCP with HTTP/3 over QUIC: how loss affects streams, and which flow-control or congestion limits both still face.
Read the full analysisOther questions this article answers
More network protocols questions
- Did HTTP/1.0 always open a new TCP connection for every resource?
- Does HTTP/2 eliminate every form of head-of-line blocking?
- Does HTTP/3 make packet loss irrelevant?
- Does HTTP/2 multiplexing prevent TCP head-of-line blocking?
- Is HTTP/3 always faster than HTTP/2?
- Does DNS happen before every HTTP request?
- Is UDP an unreliable protocol with no congestion control?
- Is QUIC just UDP with encryption?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Network Protocols beat.