Does Oxylabs support MASQUE for HTTP/3 connections?

Yes. Residential Proxies support native UDP and HTTP/3 tunneling via MASQUE (RFC 9298 CONNECT-UDP).

Most proxy routes force traffic through a TCP connection – via HTTP CONNECT, or SOCKS5 without UDP support – which causes HTTP/3 requests to downgrade to HTTP/2 or HTTP/1.1. Reaching HTTP/3 targets without that downgrade was possible before, using our SOCKS5 endpoint with UDP support, but it often required custom client code.

MASQUE maintains an end-to-end QUIC connection through our residential exit nodes, so your client transmits native UDP traffic directly to modern targets. Connection setup takes fewer round trips, no single lost packet holds up the rest, and the traffic looks like ordinary HTTP/3 rather than a recognizable proxy tunnel.

It is an addition to our existing HTTP, HTTPS, and SOCKS5 protocols. For detailed entry node setups and protocol rules, visit the Protocols page or explore the MASQUE Integration Guide.