Introduction

When Cloudflare HTTP/3 or QUIC is not working, the site often still loads normally over HTTP/2 or HTTP/1.1, which makes the problem easy to miss until performance tests or browser network tools show the fallback. Because Cloudflare handles HTTP/3 at the edge, the root cause is usually a proxy setting, client limitation, or network path issue rather than a broken origin server. The fastest way to fix it is to confirm the request is actually reaching Cloudflare's proxied edge and then determine whether UDP-based QUIC is being allowed on the client path.

Symptoms

  • Browser developer tools or protocol tests show HTTP/2 instead of HTTP/3
  • HTTP/3 works on one device or network but not on another
  • The site is behind Cloudflare, but QUIC never appears in test results
  • The issue started after DNS, proxy, VPN, or security changes
  • Performance is acceptable over HTTPS, but the expected HTTP/3 protocol is missing

Common Causes

  • The hostname is DNS-only instead of proxied through Cloudflare
  • HTTP/3 is disabled or not active yet for the zone you are testing
  • The browser or client does not support HTTP/3 on that connection or is reusing an older session
  • A firewall, VPN, antivirus product, enterprise proxy, or ISP path blocks UDP 443 traffic
  • Testing targets the origin directly or uses stale results that do not reflect the active Cloudflare edge path

Step-by-Step Fix

  1. Confirm the affected hostname is orange-cloud proxied in Cloudflare DNS, because Cloudflare can only serve HTTP/3 for traffic that actually passes through its edge.
  2. Check the zone's network settings and verify HTTP/3 is enabled for the exact site you are testing.
  3. Test with a current browser or client that supports HTTP/3, and use a fresh private window or new connection so an existing HTTP/2 session does not mislead the result.
  4. Make sure you are testing the public hostname behind Cloudflare rather than the origin IP, a direct origin hostname, or any gray-clouded record.
  5. Compare results from more than one network, because QUIC depends on UDP 443 and may fail only where a firewall, VPN, proxy, or ISP policy blocks that traffic.
  6. Temporarily disable or bypass client-side network filters such as enterprise inspection, endpoint security, or VPN tunneling if they are known to interfere with UDP traffic.
  7. Do not troubleshoot origin QUIC support first, because Cloudflare terminates HTTP/3 at the edge and the origin only needs a healthy supported connection behind Cloudflare.
  8. If only one hostname fails, review that record's proxy status, recent DNS edits, and any hostname-specific rules instead of assuming the entire zone is affected.
  9. Once HTTP/3 appears consistently, document the required proxy and network conditions so future DNS or security changes do not silently force the site back to HTTP/2.