WAYAVPN PROXY GRID • DC + RESIDENTIAL ROUTES
Fast DC power. Trusted residential reach.
WayaVPN Proxy Network gives you HTTP(S) and SOCKS5 proxy access across two routing layers: high-speed DC routes for performance-focused tasks, and residential routes for ISP-like regional access.
Route control
Choose how your traffic exits
Datacenter routes
Built for throughput, consistency and direct workloads.
Residential routes
ISP-like regional access where supported and available.
Proxy plans
Choose a proxy plan
Both plans work with available Waya proxy locations. The locations you can use may vary by server availability and proxy type.
Subscribers
Proxy access linked to your VPN plan.
If you already subscribe to WayaVPN, proxy access is included where supported. Choose DC locations for speed or residential locations when you need a residential IP in a specific area.
- Data per device
- 10,000 MB / device
- Validity
- Follows your VPN subscription
- Route mix
- DC + Residential where active
≈
Pay-as-you-go
Generate proxy access with points.
Need proxy access only when a project demands it? Use points to generate proxy credentials with a fixed bundle. Pick from available routes in your dashboard when they are enabled for your account.
- Points per generation
- 10 points
- Data included
- 300 MB
- Validity
- 24 hours from activation
≈
After generation, your dashboard shows the exact host, port, username, password and proxy strings.
DC ROUTES
Built for speed, uptime and fast access.
DC proxy routes are optimized for stable throughput, fast response and direct workloads. They are ideal when you need speed, automation, app testing or quick region-based access.
RESIDENTIAL ROUTES
Residential IPs in the locations you need.
Residential proxy routes help traffic appear from real ISP environments where available. They are useful for regional checks, content visibility, market research and trust-sensitive workflows.
HTTP(S) + SOCKS5 • DC + RESIDENTIAL
One proxy account. Two location types.
Choose DC locations for speed or residential locations for a residential IP in a selected country. Get your credentials from the dashboard and use them in browsers, apps, scripts, APIs, or test tools.
Regional access
Browse or test from selected countries using either fast DC exits or residential ISP-style routes.
Best with: DC or residential by needAutomation & tools
Run scripts, headless browsers, API clients and app tools through dedicated proxy credentials.
Best with: fast DC routesWebsite QA
Check redirects, uptime, localization, login behavior and regional content from multiple network types.
Best with: mixed DC + residentialMarket checks
Compare content, pricing and offers across countries with the route type that best fits the task.
Best with: residential where availableBrand monitoring
Review pages, listings and ads from the same regions your real users care about.
Best with: residential + DC coverageAd verification
Confirm campaign pages, tracking pixels, variants and region-specific funnels from target countries.
Best with: project-specific proxy accountsStreaming checks
Validate catalog differences, availability, playback reachability and regional media behavior.
Best with: VPN + proxy toolsAPI & app testing
Route mobile emulators, API clients or browser profiles through HTTP(S) or SOCKS5 credentials.
Best with: DC speed layerReady to start with Waya Proxy Network?
Review the full route map below, then generate available proxy credentials from your dashboard.
Proxy FAQ
Before you generate credentials
Fast answers about Waya DC and residential proxy access.
What protocols does Waya Proxy Network support? ⌄
Waya proxy locations can support HTTP(S) and SOCKS5. Protocol support depends on each configured location and is shown on each route card below.
What is the difference between DC and residential routes? ⌄
DC routes are built for speed, stability and quick access. Residential routes are built for ISP-like country access where available. Your dashboard shows which configured routes are currently available for your account.
Do I need an active VPN subscription to use proxies? ⌄
Not always. Subscribers can receive proxy access through their plan. Standard users can use points to generate a proxy account even without an active VPN subscription.
Where do I get hostname, port, username and password? ⌄
Sign in and open your proxy dashboard. Your generated proxy strings, hostname, port, username and password are shown there.
Can I use these proxies in bots, browsers, apps or scripts? ⌄
Yes. Waya proxy credentials are designed for browsers, automation tools, API clients, scripts and apps that support HTTP(S) or SOCKS5 proxy configuration.
How long does a proxy account last? ⌄
Subscriber proxy access follows your VPN subscription. Pay-as-you-go proxy accounts use the configured points, data bundle and validity window shown above.
Are all locations always available? ⌄
This page shows the full configured server list. Actual usability may differ by route type, proxy support, server status, maintenance status and network partner availability.
Should I use VPN or proxy? ⌄
A VPN tunnels your device traffic. A proxy is usually configured per app, browser, script or tool. Many Waya users combine both depending on the workflow.
Network Routes
Browse Proxy Locations
View the full configured DC and residential server list by region.
North America
Configured proxy routes in this region
USA - New York
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - California
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Texas
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Florida
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
Canada
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Illinois
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Pennsylvania
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Ohio
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Arizona
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Washington
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - North Carolina
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Michigan
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Nevada
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Georgia
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - New Jersey
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Virginia
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Massachusetts
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Tennessee
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Indiana
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Alabama
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Alaska
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Arkansas
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Colorado
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Connecticut
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Delaware
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Hawaii
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Idaho
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Iowa
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Kansas
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Kentucky
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Louisiana
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Maine
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Maryland
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Minnesota
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Mississippi
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Missouri
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Montana
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Nebraska
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - New Hampshire
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - New Mexico
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - North Dakota
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Oklahoma
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Oregon
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Rhode Island
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - South Carolina
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - South Dakota
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Utah
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Vermont
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - West Virginia
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Wisconsin
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
USA - Wyoming
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
Mexico
Residential route • configured server
- Network type
- Residential ISP
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
United States
Fast DC route • configured server
- Network type
- DC Datacenter
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
Canada
Fast DC route • configured server
- Network type
- DC Datacenter
- Protocols
- HTTP(S) · SOCKS5
Full proxy strings are visible after sign-in: hostname, port, username and password.
