Cases (FAQ)

Would there be any way that we can stick to the specified IP address for more than 24 hrs(if the specified IP is online)? What would need to happen in order to do this?

When creating a proxy list, you can set the rotation parameter to -1. In this case, forced rotation will not occur as long as the node remains available. When using API tools, you can work with sessions, which also allows the IP to remain fixed and unchanged. The IP address stays online as long as the resident is available.

Ability to use a proxy on a wider area(without a city) but on the same ISP.

Currently, it is not possible to specify an ISP for proxy lists without defining the region and city. This option is available when using api-tools , where you can specify only the ISP without setting other parameters.

I need a large number of IPs from one location, how to configure them?

Use the API tool at for unlimited access to the full proxy pool. If you need proxies from a specific country, create multiple proxy lists with 1,000 ports in the selected country and configure IP rotation upon request.

Need a new IP for each request

It is recommended to avoid using sessions and instead use login credentials with geotargeting. This will ensure a new IP for every request. Reusing the same sessions increases the risk of being blocked by the target.

We're getting a limited number of IP addresses when forming a list

To access the full pool of IP addresses in the desired country, it is recommended to reduce targeting to country + city or just the country.

We receive an "error request" when using the proxy server

Avoid using sticky sessions or reduce the request timeouts. The IP address may be blocked or restricted by the service you are working with.

It is required that the outgoing IP remains unchanged for as long as possible

If, when using a static list with a single proxy server, it becomes necessary to change the outgoing IP (for example, due to slow performance), the new outgoing IP should ideally remain unchanged for as long as possible. This issue can be resolved by using the option to set sessions with fixed IP addresses, available in the API tool.

If you don't specify sessionId+ttl, what will be the rotation?

Rotation will be = 0, each request will be issued a new IP address

I have 50 containers/servers where the same code is and all will request different locations using the same port and login, will everything be fine?

Yes.