# Start using Dedicated ISP Proxies {% embed url="" %} ## Self-Service Dedicated ISP Proxies ### Create a proxy user Create an account on the [Oxylabs dashboard](https://dashboard.oxylabs.io/en/). Then, pick a plan that fits your needs – allocate your IPs to desired locations, assign premium ASNs, and set up a proxy user. If no locations or ASNs are selected, they will be chosen randomly. ### Make a cURL request After creating a proxy user, you’ll be prompted to send your first request: ``` curl -x disp.oxylabs.io:8001 -U "user-USERNAME:PASSWORD" https://ip.oxylabs.io/location ``` Replace `USERNAME` and `PASSWORD` with your proxy user credentials. When you run the command, the response shows the IP address used for your request. Each port is linked to a fixed IP, so connecting through the same port (for example, `8001`) will always return the same address, even across long-running sessions. To switch to a different IP or test additional ones, simply change the port number (`8002`, `8003`, and so on). Self-Service Dedicated ISP Proxies also support automatic rotation. Switch your port to `8000` to receive a random IP from your proxy list with each request. ### Find your proxy list In the Oxylabs dashboard, go to **My Products → Dedicated ISP Proxies → Proxy List** to find your proxy list and selected premium ASNs. **What’s included in a proxy list?** | Entry point | The gateway to connect to your proxies | | ----------- | ----------------------------------------------------------------------------- | | Port | The specific port that allows you to access a particular proxy from your list | | Country | Two-letter country code that represents the location of your proxy | | ASN | The name of the ASN chosen during the initial setup | | Assigned IP | A specific proxy assigned to the indicated port | ### Location & ISP settings Dedicated ISP proxies are tied to fixed locations, so no extra parameters are needed – just send a request to the port linked to the IP for your chosen location. If you need to verify the network provider or ASN, we recommend using the [RIPEstat](https://stat.ripe.net/) database for the most accurate, real-time data. ### Protocols Self-Service Dedicated ISP Proxies support HTTP, HTTPS, and SOCKS5 protocols. If you want to set the desired protocol, for example, HTTPS, add `https://` to your entry point. For example: `https://disp.oxylabs.io:8000` ``` curl -x https://disp.oxylabs.io:8000 -U user-USERNAME:PASSWORD https://ip.oxylabs.io/location ``` Make sure that the libraries or third-party tools you intend to use are compatible with HTTPS and SOCKS5 protocols. Here’s a code example with the SOCKS5 protocol: ``` curl -x socks5h://user-USERNAME:PASSWORD@disp.oxylabs.io:8000 https://ip.oxylabs.io/location ``` ### Response codes When using Dedicated ISP Proxies, you may receive response codes that indicate specific reasons for success or failure. Here are the most common ones: | Response code | Error message | Description | | ------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------- | | `407` | Proxy Authentication Required | User credentials are not provided / are incorrect / the user is connecting from an IP that is not whitelisted. | | `504` | Gateway Timeout | A proxy server timed out, waiting for a response from the target server. It usually takes about 60s. | | `503` | Service Unavailable | Failed to connect to the target server. DNS failure to resolve the target server address. | | `404` | Not Found | The domain specified could not be found. | | `500` | Internal Server Error | We had a problem with our server. Try again later. | | `429` | Too Many Requests | User has reached the thread/concurrent session limit. | **🎯Important:** Find more information with codes samples in our [documentation](/products/proxies/dedicated-isp-proxies.md). ## Enterprise Dedicated ISP Proxies ### Create a proxy user Visit the [Oxylabs dashboard](https://dashboard.oxylabs.io/en/?_gl=1*1gcvaz7*_gcl_aw*R0NMLjE3Njg5NzY1NjcuQ2p3S0NBaUE3THpMQmhBZ0Vpd0FqTVd6Q09VQ2RRbzlxUlFyeVJkOTAtM0k2U2VIdTBpYllfUF9TeEZFV1dFaHNOd2d0YlR0b2NjZHFSb0Nxb2dRQXZEX0J3RQ..*_gcl_au*MTcwMTg2MDQ2Ni4xNzY3NTk3NzIy*_ga*MTgxNzcwNzAzNC4xNzUxMzU2MDU4*_ga_FC1FV63ZQ4*czE3NjkwNjA2MTgkbzExMSRnMSR0MTc2OTA4ODI2NiRqNTIkbDAkaDg4MzI2ODY4MQ..) to create an account, then purchase Dedicated ISP Proxies through the Sales Team or sign up for a free trial. Afterward, you’ll receive an email with proxy credentials from your Account Manager or our Support Team. ### Find your proxy list There are two ways you can get to your IP list: * Via browser: Open the URL you received (e.g., `https://proxy.oxylabs.io/all`) and log in using HTTP Basic Authentication. * Via API request: Send a `GET` request to the same URL, replacing `USERNAME` and `PASSWORD` with your proxy user credentials. **🎯Important:** More detailed instructions on how to retrieve your Dedicated ISP Proxy list, including basic URL access and RESTful API endpoints, can be found in our [documentation](/products/proxies/dedicated-isp-proxies/enterprise/proxy-lists.md). ### Make a cURL request By default, Oxylabs proxies and Proxy Rotator use a basic [HTTP authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) that requires you to provide a username and password. You can send your first request like this: ``` curl -x 1.2.3.4:60000 -U user1:pass1 http://ip.oxylabs.io/location ``` **🎯Important:** We also support authentication based on whitelisted IP addresses. Find more detailed setup steps in our [documentation](/products/proxies/dedicated-isp-proxies/enterprise/making-requests.md). ### Protocols If enterprise plan users need to use the SOCKS5 protocol with Dedicated ISP proxies, it must be enabled manually by contacting our Customer Support team via or live chat. Dedicated ISP Proxies support HTTP by default. You can connect to Dedicated ISP Proxies using standard HTTP requests: ``` curl -x http://1.2.3.4:80 -U USERNAME:PASSWORD https://ip.oxylabs.io/location ``` Once SOCKS5 is enabled for your account, include `socks5h://` in your request: ``` curl -x socks5h://1.2.3.4:1180 -U USERNAME:PASSWORD ip.oxylabs.io ``` Dedicated ISP Proxies use standard ports by default: | Protocol | Port | | -------- | ----- | | HTTP | `80` | | HTTPS | `443` | Access to additional ports requires compliance verification. Please contact our support team for assistance. ### Response codes When using Dedicated ISP Proxies, you may receive response codes that indicate specific reasons for success or failure. Here are the most common ones: | Response | Error Message | Description | | -------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------- | | `407` | Proxy Authentication Required | User credentials are not provided / are incorrect / the user is connecting from an IP that is not whitelisted. | | `504` | Gateway Timeout | A proxy server timed out, waiting for a response from the target server. It usually takes about 60s. | | `503` | Service Unavailable | Failed to connect to the target server. DNS failure to resolve the target server address. | | `404` | Not Found | The resource specified could not be found. | | `500` | Internal Server Error | We had a problem with our server. Try again later. | If you receive any other response code, please contact your Dedicated Account Manager for more information. **🎯Important:** For more information on managing your Dedicated ISP Proxy IP whitelist and proxies via the RESTful API, as well as details about the Proxy Rotator feature, see our [documentation](/products/proxies/dedicated-isp-proxies/enterprise/restful.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developers.oxylabs.io/help-center/getting-started/start-using-dedicated-isp-proxies.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.