> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/products-and-features/does-oxylabs-support-masque-for-http-3-connections.md). # Does Oxylabs support MASQUE for HTTP/3 connections? Yes. [Residential Proxies](https://oxylabs.io/products/residential-proxy-pool) support native `UDP` and `HTTP/3` tunneling via MASQUE ([RFC 9298 CONNECT-UDP](https://datatracker.ietf.org/doc/html/rfc9298)). 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](/products/proxies/residential-proxies/protocols.md) page or explore the [MASQUE Integration Guide](/products/proxies/residential-proxies/protocols.md#http-3). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developers.oxylabs.io/help-center/products-and-features/does-oxylabs-support-masque-for-http-3-connections.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.