TABLE OF CONTENTS

➡️ Overview

Rayobyte Residential Proxies support flexible location and network targeting, allowing you to request IPs by country, region, city, ZIP or postal code, or Autonomous System Number (ASN).

This guide explains how to configure these targeting options, connect using either HTTP or SOCKS5, and troubleshoot situations where a matching residential IP isn't immediately available.

➡️ Targeting Options

Configure Through the Residential Proxy Dashboard

You can configure the following options directly from the Residential Proxy Dashboard:

  • Country
  • Region / State
  • City
  • Sticky Sessions

These settings are automatically applied to your proxy credentials. If you prefer, you can also configure them manually by appending the corresponding parameters to your proxy password.

Advanced Manual Targeting

The following advanced targeting options currently need to be added manually to your proxy password:

  • ZIP or Postal Code: -zip-43212
  • ASN: -asn-AS7922

Support for configuring ZIP codes and ASNs directly from the Residential Proxy Dashboard will be added in a future update.

➡️ Targeting Parameters

Append one or more parameters to your residential proxy password to request a specific type of residential IP.

TargetFormatExampleNotes
CountryCountry code-country-USUse the appropriate two-letter country code.
Region / StateRegion name-region-CaliforniaUse the standard region or state name.
CityCity name-city-Los_AngelesReplace spaces with underscores for multi-word cities.
ZIP / Postal CodePostal code-zip-43212Availability depends on active residential connections within that postal area.
ASNASN with the AS prefix-asn-AS7922Requests an IP belonging to a specific network or ISP.
SessionSession ID-session-Example123Uses the existing sticky-session format.

For consistency, we recommend appending targeting parameters in the following order:

PASSWORD-country-XX-region-REGION-city-CITY-zip-POSTALCODE-asn-AS12345-session-SESSIONID

This recommended order is intended to keep your proxy credentials organized and easier to read. In most cases, the order of targeting parameters does not affect how the system processes your request.

You can combine multiple targeting parameters in the same proxy password as needed.

Keep in mind: Every additional targeting parameter narrows the pool of available residential IPs. For the best availability, only specify the filters you actually need.

➡️ Examples

Country targeting

PASSWORD-country-US

Country + Region

PASSWORD-country-US-region-California

Country + Region + City

PASSWORD-country-US-region-California-city-Los_Angeles

Country + ZIP Code

PASSWORD-country-US-zip-43212

Country + ASN

PASSWORD-country-US-asn-AS7922

United Kingdom + ASN

PASSWORD-country-GB-asn-AS5378

Combined targeting

PASSWORD-country-US-region-Ohio-city-Columbus-zip-43212-asn-AS7922-session-Example123

The ZIP codes and ASNs shown above are examples only and do not guarantee that matching residential IPs will always be available.

➡️ Using ASN Targeting

ASN targeting lets you request an IP that belongs to a specific Internet Service Provider or network.

When using ASN targeting:

  • Include the AS prefix (for example, -asn-AS7922).
  • Some ASNs may have very few or no active residential devices.
  • Cloud or datacenter ASNs are generally much more difficult to obtain from a residential proxy network.
  • When troubleshooting availability, start by testing Country + ASN only. Once you've confirmed that a matching residential IP is available, gradually add additional targeting, such as a region, city, ZIP code, or sticky session if needed.

You can find ASN numbers using publicly available ASN lookup services.

➡️ Residential IP Availability

Residential proxies rely on real residential internet connections, so available IPs constantly change as devices connect to and disconnect from the network.

The more specific your targeting is, the smaller the available pool becomes.

For example:

  • Country targeting usually provides the largest pool.
  • Region and city targeting narrow that pool.
  • ZIP code and ASN targeting narrow it even further.
  • Combining city, ZIP code, ASN, and sticky sessions may leave no matching residential IP available at that moment.

If no residential IP currently matches your requested targeting, your request may fail instead of automatically returning an IP from a broader location.

If this happens, try broadening your targeting by removing the least important parameter and testing again.

➡️ HTTP Examples

HTTP with ASN targeting

curl -x "http://USERNAME:PASSWORD-country-US-asn-AS7922@la.residential.rayobyte.com:8000" https://ipinfo.io/json

HTTP with ZIP targeting

curl -x "http://USERNAME:PASSWORD-country-US-zip-43212@la.residential.rayobyte.com:8000" https://ipinfo.io/json

Replace USERNAME and PASSWORD with your own Residential Proxy credentials.

➡️ SOCKS5 Support

Residential Proxies also support SOCKS5 connections on port 1080.

For the best compatibility, we recommend using socks5h rather than plain socks5.

Using socks5h ensures that hostname resolution is performed through the proxy, while plain socks5 may resolve hostnames through your local network instead.

SOCKS5h example

curl -x "socks5h://USERNAME:PASSWORD-country-US-asn-AS7922@la.residential.rayobyte.com:1080" https://ipinfo.io/json

Replace USERNAME and PASSWORD with your own Residential Proxy credentials.

➡️ Troubleshooting

If your proxy works without targeting but stops connecting after you add a city, ZIP code, or ASN, your credentials are probably still correct. In many cases, this simply means there isn't currently a residential IP available that matches your requested targeting.

SymptomPossible CauseWhat to Try
Authentication errorIncorrect credentials or formattingVerify your username, password, and targeting parameters.
Connection timeoutNo matching residential IP currently availableWait a few moments and try again, or broaden your targeting.
HTTP proxy error 552A matching residential IP may not currently be availableRetry, then remove the narrowest targeting parameter.
SOCKS5 reply code 5Connection rejected or no usable residential exit foundTest without targeting, then add parameters one at a time.
Correct country, but unexpected cityDifferences between third-party IP geolocation databasesVerify the IP using another reputable geolocation provider.
  1. Retry the same request after a short delay.
  2. Remove the city or ZIP code.
  3. Remove the ASN.
  4. Test using country targeting only.
  5. Contact our support team if a location that normally works continues to fail.

➡️ Protect Your Credentials

To help keep your account secure:

  • Never include your full proxy password in support tickets, screenshots, or chat messages.
  • Mask or remove credentials before sharing configuration examples.
  • If you believe your proxy password has been exposed, change it as soon as possible.

➡️ Need Help?

If you need help configuring targeting parameters, testing a specific city or ASN, or setting up a SOCKS5 connection, we're happy to help.