Network & Infrastructure / IPv6, TCP & Transport Engineering
QUIC blocked by UDP policy while HTTPS over TCP succeeds
Users report that a modern web application works slowly on one network despite ordinary HTTPS tests passing. QUIC may be blocked and the client may be using a fallback transport.
Environment and inputs: Dual-stack routed networks and transport endpoints; validate the complete path and the active operating-system version. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Compare transport selection, UDP reachability, endpoint logs and policy counters for the service. Distinguish deliberate UDP restriction from path-specific loss or unsupported application negotiation.
Explain the result
QUIC runs over UDP and implements transport functions above it. A successful TCP connection to the same service does not prove the QUIC path is permitted or healthy.
Plan the fix
Decide whether QUIC is supported by the network policy and application requirements. Correct the specific approved UDP path or document the expected fallback rather than opening unrestricted UDP.
Check the result and rollback
Measure startup and steady-state application behavior with each supported transport. Revert policy changes if they broaden access beyond intended endpoints or introduce state-table pressure.