UDP Proxies for Gaming, VoIP, and Streaming

Name: UDP proxies
Brand: PapaProxy.net
Availability: InStock

UDP Proxies

SOCKS5 with a full UDP ASSOCIATE implementation: your datagrams are relayed as UDP, with no silent fallback to TCP. Available as an add-on for datacenter packages, dedicated IPs, and ISP proxies — gaming, VoIP, streaming, and WebRTC work the way they're supposed to.

Pricing for proxies with the UDP add-on

Pay with cryptocurrency and get a 10% bonus to your balance Full refund within 24 hours if the proxies aren't a fit The UDP add-on is enabled in the checkout configurator

	HTTP	HTTPS	SOCKS4	Works with UDP SOCKS5
Traffic encryption	✕ No TLS to the proxythe proxy connection is unencrypted	✓ TLS tunnelto our server and the target site	Depends on the application protocolHTTPS traffic remains encrypted	Depends on the application protocolHTTPS traffic remains encrypted
Header handling	May add or modify HTTP headers	TunneledHTTP headers inside the tunnel are not modified	Passes application traffic unchanged	Passes application traffic unchanged
TCP / UDP	TCP	TCP	TCP	TCP + UDP
Username/password auth	✓ Supported	✓ Supported	✕ No password authentication	✓ Supported
Remote DNS resolution	Client-dependent	Client-dependent	✕ Nothe client resolves the hostname	✓ Supportedwhen the client sends the hostname to the proxy
When to choose it	Web and API traffic, especially with software that supports HTTP proxies	When you need a TLS-encrypted connection to the proxy	Legacy software that only supports SOCKS4	General-purpose applications, gaming, streaming, and UDP traffic
	All four protocols come with every PapaProxy.net plan — UDP is added as an option on SOCKS5 See pricing

HTTP

HTTPS

SOCKS4

Works with UDP
SOCKS5

Traffic encryption

✕ No TLS to the proxythe proxy connection is unencrypted

✓ TLS tunnelto our server and the target site

Depends on the application protocolHTTPS traffic remains encrypted

Header handling

May add or modify HTTP headers

TunneledHTTP headers inside the tunnel are not modified

Passes application traffic unchanged

TCP / UDP

TCP

TCP + UDP

Username/password auth

✓ Supported

✕ No password authentication

✓ Supported

Remote DNS resolution

Client-dependent

✕ Nothe client resolves the hostname

✓ Supportedwhen the client sends the hostname to the proxy

When to choose it

Web and API traffic, especially with software that supports HTTP proxies

When you need a TLS-encrypted connection to the proxy

Legacy software that only supports SOCKS4

General-purpose applications, gaming, streaming, and UDP traffic

All four protocols come with every PapaProxy.net plan — UDP is added as an option on SOCKS5 See pricing

Meet PapaProxy.net

A bulk IPv4 proxy service built by engineers, not marketers.

PapaProxy.net was founded in 2019 by an engineer who needed reliable bulk proxies at a reasonable price. That shaped our core principle: invest in technology and infrastructure rather than advertising, and pass the savings on to customers.

We use our own hardware and automation instead of rented servers and manual processes. That's how we keep prices below market without sacrificing stability. Real people handle support tickets and live chat, and most payment methods require no KYC.

More about the company

1,500+ concurrent connections — even on the smallest plan

Unlimited bandwidth on every plan — no need to count gigabytes

80 Gbps uplink per server

Up to 500 Mbps per proxy in your package

Servers on 4th-gen AMD EPYC (Genoa) Hosted in Tier III data centers with redundant connectivity Kubernetes orchestration Monitoring with no content logging

Connect in 60 seconds

UDP traffic is proxied through SOCKS5: connect through it, and once the association is up, your datagrams flow through the proxy. HTTP and HTTPS work on the same addresses too — those protocols are TCP-only, for web, APIs, and scraping; UDP does not pass through them. Copy the example for your stack — or hand it to your AI assistant.

# HTTP or HTTPS proxy
curl -x http://login:password@IP:port https://example.com

# SOCKS5
curl --socks5-hostname IP:port \
  --proxy-user login:password \
  https://example.com

import requests

proxy = "http://login:password@IP:port"  # your proxy from the Dashboard

r = requests.get(
    "https://example.com",
    proxies={"http": proxy, "https": proxy},
)
print(r.status_code)

import { ProxyAgent } from "undici";

const dispatcher = new ProxyAgent("http://login:password@IP:port");
const res = await fetch("https://example.com", { dispatcher });
console.log(res.status);

$ch = curl_init("https://example.com");
curl_setopt($ch, CURLOPT_PROXY, "IP:port");
curl_setopt($ch, CURLOPT_PROXYUSERPWD, "login:password");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);

One list, proxies for TCP and UDP traffic: use the SOCKS5 line for UDP jobs and the HTTP line for TCP jobs on the same addresses. Exports come as ip:port or ip:port@login:password; access is whitelist-based — up to 5 of your IPs free, in which case no credentials are needed.

Export in any format

Choose a standard format or create a custom one with any field order and delimiter your software requires.

IP:port login:password@IP:port {scheme}{ip}{port}{login}{password} — builder

HTTP HTTPS SOCKS4 SOCKS5 HTTP/2 ✓

See the FAQ for the ports used by each protocol.

Setup guides for browsers and antidetect tools

PapaProxy API

You can automate purchases, renewals, whitelist changes, and proxy list exports. Create an API key in your Dashboard in a couple of clicks.

Create a key in your Dashboard

MCP server for AI agents

Claude, Cursor, and other agents buy proxies, rotate IPs, and monitor performance automatically — 50 tools. See the details below.

Works with

Playwright

Scrapy

Selenium

Puppeteer

ZennoPoster

BAS

Dolphin

AdsPower …and 500+ more tools

Proxies managed by your AI agent

The PapaProxy.net MCP server gives your agent access to 50 Dashboard tools. Claude, Cursor, or any MCP-compatible agent buys, rotates, and monitors proxies on its own — you describe what you need in plain English.

AI agent + PapaProxy.net MCP

Get me 500 IPs from the Europe package and whitelist the office IP

quote_compositecalculates a quote for the multi-country mix✓

order_compositepackage purchased and activated✓

add_whitelist_ipoffice IP whitelisted✓

list_proxy_ipsproxy list exported to chat✓

Why did the success rate dip yesterday?

get_usage_timeserieshourly chart✓

get_diagnosticserrors by status code and affected hosts✓

get_recommendationswhat to fix — in the agent's reply✓

Ordering and renewals The agent quotes multi-country mixes with volume and term discounts, buys, renews, and turns on auto-renewal. Canceling a plan triggers a prorated refund for unused days.

IPs, credentials, whitelist List exports, IP rotation, username/password changes, IP whitelisting with connection limits — no Dashboard login needed.

Analytics and diagnostics Success rate, latency, top domains, error breakdowns by code, and recommendations: which limits to raise, which IPs sit idle.

Balance, invoices, support Balance top-ups, payment history, PDF invoices, and support tickets — directly through the agent.

Create the access token in your Dashboard. The agent can spend only the funds available in your account balance, and it never sees your card details. Set it up in your Dashboard

Frequently asked questions

How do I enable UDP, and what does it cost?

UDP is a plan add-on, not a separate product. It costs 50% of the base plan price and is available for all plans except rotating proxies. For a new order, select the UDP option in the checkout configurator; it will be enabled on every IP in the package. You can also add UDP to an active plan, with the surcharge prorated for the remaining term.

What is UDP, and how is it different from TCP?

UDP (User Datagram Protocol, RFC 768) is a connectionless protocol: it skips the handshake, never retransmits lost packets, and doesn't guarantee delivery order. Corrupted datagrams are simply dropped after a checksum test — no waiting, no retries. The differences from TCP, axis by axis: connection — TCP establishes one via handshake, UDP runs sessionless; reliability — TCP guarantees delivery and resends losses, UDP drops them; ordering — TCP delivers in sequence, UDP makes no promises; overhead — TCP carries more, which is why UDP feels snappier. Hence the division of labor: TCP for web pages, files, and email; UDP for gaming, VoIP, streaming, and DNS, where reaction speed beats perfect delivery.

The practical consequence for proxies: push UDP through a TCP-only tunnel, and every datagram gets wrapped in a stateful TCP connection — one lost batch stalls the entire stream while TCP waits for a retransmit (head-of-line blocking). That's where the stutter in games, the ping spikes, and the choppy calls come from. Which is exactly why we implemented full UDP ASSOCIATE: datagrams stay datagrams.

Do HTTP proxies support UDP?

No. HTTP and HTTPS proxies work over TCP only (via the CONNECT method), so they physically cannot carry real UDP traffic — which is why our UDP proxies run on SOCKS5 with UDP ASSOCIATE, not on HTTP. This matters in practice: plenty of providers label their proxies "UDP-compatible" while quietly forwarding TCP only. Ours implement ASSOCIATE for real, verified in testing, so your datagrams are actually relayed. (UDP over HTTP does exist on paper — MASQUE / CONNECT-UDP in HTTP/3 — but in 2026 it's still experimental and available from only a handful of large CDNs, so we ship the proven SOCKS5 path.)

Where is UDP actually used today?

UDP is the backbone of the real-time internet, and here's what our customers run through UDP proxies most often. Online gaming — racing, MMOs, and shooters use UDP for low-ping client-server traffic where single milliseconds count. Voice and video calls — Discord, Zoom, Microsoft Teams, and other VoIP apps stream audio and video over UDP (RTP). Streaming and IPTV — UDP removes the stutter that retransmits cause in real-time video. DNS queries — DNS runs over UDP, port 53. WebRTC — in-browser real-time communication runs on UDP and is a notorious source of IP leaks. Torrents — BitTorrent's uTP protocol rides on UDP. NTP — time sync uses UDP, port 123. UDP VPN tunneling — for example, disguising WireGuard as ordinary traffic to get through strict firewalls.

Does a SOCKS5 UDP proxy encrypt my traffic?

No — and we say so plainly. Our proxies replace your real IP with the proxy's IP, but SOCKS5, like UDP itself, does not encrypt packet contents. If you need encryption, use an application that brings its own (HTTPS, or DTLS for WebRTC), or run an encrypted tunnel such as WireGuard on top of our proxy. The proxy gives you a clean IP and true UDP transport; encryption is the application's job, one layer up.

What makes PapaProxy.net UDP proxies stand out?

Three things. Real UDP, not a label: full UDP ASSOCIATE, implemented and tested end to end — datagrams are relayed, never silently downgraded. Speed: up to 500 Mbps per proxy on a managed network — enough for HD streaming, heavy transfers, and low-latency gaming. Clean static IPs: your real address is replaced by the proxy's, which lowers detection risk when juggling multiple accounts, switching regions, or checking latency from different locations. And if any UDP application gives you trouble, our support team has configured these setups many times and will get you connected.

How do I verify that a proxy actually supports UDP?

Three checks, from quickest to most reliable. WebRTC test: run one through the proxy — if it shows the proxy's IP instead of yours, UDP is being relayed. DNS through the proxy: send a query like dig @8.8.8.8 example.com (DNS rides on UDP) — a normal answer means UDP passes. Any real UDP application: launch a game or join a voice chat through the proxy — if the connection comes up and holds, UDP works. If everything times out or quietly switches to TCP, the "UDP support" you were sold is a label, not a feature. Our proxies pass all three checks — and if something looks off, our support team will run them together with you.

How do I use a UDP proxy in a browser without leaking my IP?

This is exactly where most people get burned. WebRTC sends STUN requests over UDP (port 3478), and most browsers — Chrome included — do not route UDP (or QUIC/HTTP/3) through a SOCKS5 proxy at all: only TCP gets proxied. So if you simply type the proxy into browser settings, your UDP won't go through us, and your real IP can still leak. What actually works: route all system traffic through the proxy with a UDP-capable tool — Proxifier (GUI, Windows/macOS) or tun2socks clients like sing-box, Clash / Clash Verge, or hev-socks5-tunnel push everything, UDP included, through our SOCKS5; this is the most reliable option. Chrome/Chromium flag: launch with --force-webrtc-ip-handling-policy=disable_non_proxied_udp so WebRTC's UDP goes proxy-only. Just need to plug the leak? Use a WebRTC-blocking extension such as WebRTC Control or WebRTC Leak Prevent, or an antidetect browser where WebRTC can be disabled or proxied per profile — we have ready-made guides for Dolphin{anty}, AdsPower, GoLogin, and others.

Need a step-by-step walkthrough? Check our setup guides for browsers, operating systems, and 14+ antidetect browsers — or just tell support which OS, browser, or antidetect you use, and we'll point you to the exact setup.

Is UDP faster than TCP?

On latency and overhead — yes: no handshake, no acknowledgments, no retransmits. But UDP doesn't guarantee delivery, so it's only "faster" where the occasional lost packet is acceptable — games, voice, streaming. For transfers that must arrive complete and in order, TCP is the right tool, which is why our plans support HTTP and SOCKS5 over TCP out of the box, and you add UDP on top when your use case requires it.

What's the difference between UDP and QUIC?

QUIC runs on top of UDP. Raw UDP fires datagrams with no handshake, no delivery guarantees, and no encryption — minimal latency, with reliability and security left to the application. QUIC (developed at Google, later standardized by the IETF as RFC 9000) builds on UDP and adds the comforts of TCP while keeping latency low: built-in TLS 1.3 encryption from the first packet, reliable in-order delivery with fast loss recovery, stream multiplexing without head-of-line blocking, and rapid 0-RTT / 1-RTT connection setup. HTTP/3 runs on it. And since QUIC uses UDP, the same UDP ASSOCIATE mechanism our proxies run on can carry QUIC / HTTP/3 traffic as well — provided your client actually sends its UDP through the proxy.

Reviews

A few service metrics—and feedback from our customers.

27,000+

proxy packages sold since 2019

60%

of customers upgrade their plan after the first month

100,000+ IPs

in our own pool across 22 locations

I can't get to the site in any way. The functionality suits me, prices and quality of proxies too. All cool, thanks!

E EvilFox February 2025

Socks are great! They work without interruptions and, the main thing, are stable. They are perfect for parsing sites. No bans, the cost is reasonable, I recommend them.

SM Spencer McDonald September 2025

Out of a hundred proxies some failed, but the workers of the service have quickly replaced them. I am very much pleased with the servers speed. I use it for targeting in social networks and all my accounts are safe and sound. My personal recommendation.

T Taylor November 2025

The proxies are not bad. I have not had any problems with their work since I have been using them for three months. Data collection speed is good and I have not had any interruptions yet. I use the rebates I receive for prolonging my proxy for the next month.

AW Alex Wallace November 2025