Residential Network

Gal El Al
Gal El Al
  • Updated


Residential network policy

Each account must present and clarify its use case as a part of the "Know Your Customer" (KYC) process, in which Bright Data grants access to the Residential proxy network.

To protect Bright Data's residential network, monitoring rules are applied to all traffic preventing customers from accessing domains outside their use case and Bright Data's network policy.

Nevertheless, you may ask for access to a specific domain out of Bright Data network policy by contacting our compliance team (at compliance@brightdata.com) or your account manager and explaining/demonstrating why accessing such a domain is needed for your use case. 

When trying to access a domain that is forbidden to your vertical, the typical error message returned is:

x-luminati-Error: Access denied: {Domain} access was blocked as it might breach Bright Data usage policy. Contact complaince@brightdata.com or your Account Manager for further assistance

Error code: 403 Forbidden

 

Network size

To see the availability (estimated) of Bright data network within a country, please check:
https://brightdata.com/locations

To check a specific country, add to the URL the country code:
E.g.:
For Argentina, use the following:
https://brightdata.com/locations/ar
For Great Britain use:
https://brightdata.com/locations/gb

 

Start Using

Before using Bright Data's residential IP network, a Bright Data representative will ask you to go through a short User compliance evaluation process (KYC). The User compliance evaluation process may include a quick intro video call and some verification of your company or personal information.

To initiate the process, open a residential proxy zone:

  • Go to your proxies page: https://brightdata.com/cp/zones
  • In the "Add proxy" drop-down menu, choose "Residential Proxies":
  •   proxy.png
  • In the proxy configuration page, adjust the proxy to your needs, then click on "Add proxy":
  • add.png
  • In case you require to submit a KYC form, The KYC process initiation window will appear automatically, enter your details and wait for us to contact you.

Allocation type of the residential IPs

shared pool

Connecting you to our entire network of 72+ million IPs. You can rotate between countries, cities, and ASNs using the Proxy Manager, Extension, or the raw API.
The cost is per GB used, according to your monthly plan.

 

Dedicated IPs (gips)

Bright data residential network built from different users sharing their devise resources when their device is ideal.
Since the peer IP is available to use only when ideal, Bright data developed the group IPs
Each gip (group IP) contains between 6-90 IPs at any given moment from the same region

and can be used for dedicated domains you selected within your zone "access parameters" section

Requests to domains that are not in the list will be sent from the super proxy server
There is no option to add "all domains"

 

Rate limit and IP detection domains 

To protect the peer network (PII regulation), Bright data enforce a rate limit to IP detection domains.
Therefore, requests to such domains might result in the following errors:


- The proxy server is refusing connections
- Header error:

< HTTP/1.1 429 Requests rate to <Domain> is too high
< X-Luminati-Error: Requests rate to <Domain> is too high

The rate limit is per user and use-case and can be resolved by choosing a different super proxy.
(replace zproxy.lum-superproxy.io with specific super proxy IP, or use session ID for the super proxy)

 

Note - http://lumtest.com/myip.json domain is not monitored by the rate limit function and will return the IP geolocation and Hashed IP

If your program/tool requires IP detection domains to connect, you can contact our compliance team and elaborate on the use case - compliance@brightdata.com

 

Hashed IP format

When using Bright data residential network, the response header of the IP (AKA x-luminati-ip header)

will return the IP address hashed (16digits encryption)

Response example:

{"ip":"ra2612b761c84a8b5cbd207a1d8a7386d","country":"US","asn":{"asnum":14618,"org_name":"AMAZON-AES"},"geo":{"city":"Ashburn","region":"VA","region_name":"Virginia","postal_code":"20149","latitude":39.0469,"longitude":-77.4903,"tz":"America/New_York","lum_city":"ashburn","lum_region":"va"}}

We want to protect the IP address for two main reasons:
- PII regulation: protect the information of the peer
- Reduce/Abolish the option of abusing the peers

Requests to domains out of our control will be rate limited.

Datacenter and ISP networks are out of the above policy and will provide the IP address in the response.

 

Superproxy Bypass (direct request)

The "x-luminati-ip" header in the request refers to the IP address which will send the request to the domain (AKA "Proxy peer").
Due to different network restrictions mentioned in the article, in some cases, the residential proxy peer won't be allowed to send the request, and the request will be sent from the super proxy server.

< x-luminati-ip: superproxy bypass

 

If it's required to send the request from the proxy peer and not the super proxy, you should contact compliance to whitelist the domain activities; this will allow the request to be sent from the proxy peer.


Please note that the Bright data compliance team will require a detailed explanation to allow requests from the proxy peer, not the super proxy. 
You can contact compliance@brightdata.com to add domains or support@brightdata.com to get more information about Super proxy direct requests.

 

Due to Bright data policy, requests to forbidden domains might face "block" response, in such cases please get in touch with our compliance department to confirm your activity and use case