Good point about WebRTC. A mismatched exit IP can make the whole setup look inconsistent.
Yep, that’s how I see it too. TCP for most web tasks, UDP when real-time traffic matters.
Gaming is probably the clearest UDP use case. Curious if anyone uses it much outside real-time traffic.
from my experience, tcp tbh work perfectly fine on all kinds of tasks i tried for web-related stuffs till now, that is why it was not vry important for me to test udp. Just want to ask if anyone used it with residential proxies and if they noticed any improvements.
That’s what we see from many users too. TCP covers most web-related tasks, while UDP is usually needed for more specific use cases.
Good question. We’re curious about that too, especially whether users see a noticeable difference with residential proxies when UDP is enabled.
for scraping and browser work TCP is enough, UDP barely comes up. its for voip, gaming, live streams, stuff where retransmits hurt. i know iphey supports it but ive never had a reason to use it in practice
Good point. SOCKS5 and UDP support are often treated like the same thing, but they’re not. Full-device tunneling is where UDP starts to matter much more.
To add to this, the thing to ask the provider is if they support UDP ASSOCIATE, a lot of socks5 setups only do CONNECT (tcp). wireguard is udp only so it just won’t work without it, openvpn can at least fall back to tcp. quic/http3, voip and most games are udp too, so if any of that matters test it before you buy a big plan
Good point on HTTP/3. UDP support doesn’t automatically mean better performance.
Yep, checking UDP ASSOCIATE first is a good call before buying in volume.
Good point. Browser SOCKS5 support and full UDP tunneling are definitely two different things.
