We built full UDP support across our residential and mobile pools. No fuss. Just plug in and go.
What you get
Use it for browsing, API work, and automation against targets that have moved to HTTP/3. When a destination only accepts TCP, your requests take the normal TCP path, so nothing breaks.
A UDP proxy forwards datagrams instead of streams. That lets apps and sites use protocols that live on UDP, like QUIC for HTTP/3, WebRTC checks, and more. You get lower latency and a network shape that mirrors modern browsers and phones.
If you use SOCKS5, UDP is part of the spec. Clients send a UDP ASSOCIATE command and the proxy relays datagrams for you.
Your app connects to anyIP using HTTP, HTTPS, or SOCKS5. If the target speaks HTTP/3, we pass QUIC over UDP end-to-end. If the target stays on HTTP/1.1 or HTTP/2, traffic uses TCP as usual.
Controls you keep
Compatibility notes
Pick a client that supports UDP or enable the UDP option so it can send the UDP ASSOCIATE command.
It reduces handshake trips and removes stream-level head-of-line blocking, which often cuts latency and stalls.
No one is 100 percent invisible, but matching the site’s transport and timing removes a big tell. Pair UDP with good fingerprints and sane behavior for best results.
Experience seamless connectivity with our diverse proxy types.