Learn / Answers

Why is QUIC (HTTP/3) not getting a response?

QUIC is the UDP-based transport behind HTTP/3, on UDP port 443. Some firewalls block UDP 443, so the browser's QUIC attempt gets no answer and it falls back to TCP. Sites still load, just a little slower to start.

What it looks like in the packets

  • UDP packets to port 443 from the client (QUIC Initial packets), with nothing coming back.
  • A TCP connection to the same server on port 443 shortly after (the fallback).

Common causes

  • A firewall or corporate network blocking UDP 443.
  • A server that doesn't support QUIC.
  • A middlebox that only understands TCP.

What to check

  1. If sites load, nothing needs fixing.
  2. To get HTTP/3, allow outbound UDP 443 on the firewall.

Wireshark display filters

  • quicall QUIC packets
  • udp.port == 443UDP to or from port 443

How Blame Finder flags it

Informational; it doesn't affect the health grade. Upload a capture and the finding links straight to the packets behind it.