Static ISP Proxies
Static ISP proxies provide dedicated static IP addresses. Use this proxy type when a workflow needs a consistent exit address rather than a rotating residential session.
Scrapeless describes this offering as residential ISP IPs with HTTP, HTTPS, and SOCKS5 support. Its setup uses a purchase flow separate from Residential, Datacenter, and IPv6 channels.
When to use static ISP proxies
Consider Static ISP Proxies for recurring access to the same service, workflows that associate a session with an IP address, or integrations that need a stable proxy assignment.
An IP address is one part of a session. Your application still needs to manage its own cookies, login state, and target-site behavior. A static IP does not guarantee that a target site will accept a request.
For temporary IP continuity with rotation after a configured period, review Residential Proxies.
Obtain your proxies
- Sign in to the Scrapeless dashboard.
- Open Proxy Solutions → Static ISP Proxy.
- Select Apply Now to open the purchase page.
- Choose the quantity and review the available offering, then complete the purchase.
- In the Static ISP Proxy channel list, select the channel and choose Start to view its connection details.
Use the location and resource choices available for the Static ISP offering. Review the purchase details for the applicable terms and allocation.
See Getting Started for the documented purchase flow.
Test the assigned connection
Use the host, port, username, and password shown for your Static ISP proxy. Do not replace them with connection details from another proxy type.
curl --proxy 'http://YOUR_PROXY_HOST:YOUR_PROXY_PORT' \
--proxy-user 'YOUR_PROXY_USERNAME:YOUR_PROXY_PASSWORD' \
'https://api.ipapi.is/'Replace the four placeholders with the connection details for this proxy type. YOUR_PROXY_USERNAME means the complete generated username, including any options already present. Use the proxy password from that channel.
This example makes an HTTPS request through an HTTP proxy. The response comes from the IP-check service and describes the exit connection it observed. Inspect your actual response; the exit address is not a fixed example value.
Repeat the test with the same assigned connection details and compare the reported exit address. For a workflow that depends on a particular IP, record and monitor that address in your application.
Keep the assigned configuration
Use the connection string provided for your Static ISP resource. The generic username syntax elsewhere in the documentation includes rotation and session options, but the Static ISP setup does not document how those options apply to a purchased static resource. Keep the supplied configuration unless the Static ISP connection details explicitly expose an option.
Do not change the proxy-type identifier to convert an existing Residential channel into a Static ISP proxy. The proxy type is bound to the channel.
Resolve connection problems
| Symptom | What to check |
|---|---|
HTTP 407 | Confirm the proxy username and password, resource availability, and any applicable channel limit. |
| Connection timeout | Check the host and port against the assigned details and verify that your application can reach them. |
| Unexpected exit IP | Confirm that you are using the intended Static ISP resource and that the application is applying its proxy settings. |
| Target returns an error | Test the proxy against the IP-check URL, then inspect the target response separately. |
When escalating an issue, include the proxy type, error, and time of the request. Omit passwords from shared logs.
Related configuration
- Authentication and Endpoints: credentials, connection-string fields, and gateways.
- Integrations: connect your application or proxy client.
- Troubleshooting: diagnose authentication, connection, and upstream errors.