Datacenter plans
Only available for shared datacenter proxies when you pay per GB
Your information is protected by 256-bit SSL
Google Pay and Apple Pay are only available with Smart Wallet
Pay per IP
Pay per GB
Access:
An exclusive IP pool with a possibility to customize the number of IPs.
Preferred locations worldwide.
Possibility to choose the amount of traffic.
Unlimited concurrent sessions and threads.
Rotating & static sessions.
A shared 100K+ IP pool worldwide.
Chosen amount of traffic.
Unlimited concurrent sessions and threads.
Rotating & static sessions.
Choose if:
You want to get a specific amount of IPs and traffic.
You need a big pool of rotating proxies.
Pay for:
Number of IPs and traffic (bandwidth).
Traffic (bandwidth).
Listen, we love you like no one’s business. That’s why we offer you the dopest services for a literal bargain, a bunch of free tools, and customer support that never sleeps. Seriously, we won the Best Value Provider award for this stuff.
Advanced proxy rotation
Get a unique proxy with every connection request or use sticky sessions to keep the same IP longer.
Individual setup
Customize your subscription plan to the max by choosing the number of IPs, specific locations, and traffic amount when you pay per IP.
Unlimited connections
Juggle projects of any size with unlimited concurrent sessions, connections, and threads when you pay per GB.
Intuitive self-service
Use our user-friendly dashboard for easy proxy management.
Learn statistics about your traffic usage, requests, and top targets.
Datacenter proxies are remote computers with their own IP addresses. They act as an intermediary between you and the target website: instead of connecting to the website directly, your request goes via proxies to hide any identifying personal information.
DC proxies share subnets which makes them easier to block compared to the more resilient residential proxies. However, since datacenter proxies are running on insanely fast machines, their connection speed and stability are definitely better – and speed can sometimes be the most important factor for your scraping projects.
Yes, you can. Once you have a subscription plan in the dashboard, go to the subusers tab and create a subuser. You will be able to set limits, dedicate traffic for different tasks, locations, etc. for every proxy user.
We offer two pricing models based on your needs: Pay per IP allows you to pay for a specific number of datacenter IPs (starting from 100 IPs) and GBs (starting from 50 GB) in chosen locations; Pay per GB lets you get unlimited IPs while paying for the traffic (bandwidth) only.
We accept payments with Credit Cards, PayPal, Alipay, and cryptocurrencies. With Smart Wallet, two additional payment methods are available (Google Pay and Apple Pay). All orders are processed by our online reseller Paddle.com which is a Merchant of Record for these orders. To contact Paddle’s support team, reach out via Paddle.net.
You can use our proxies with almost any application that supports HTTP/HTTPS Proxies. Smartproxy IP addresses work great with all search engines, ScrapeBox, and many other bots.
Using datacenter proxies for most scraping tasks is more efficient. We allow our clients to use datacenter proxies for data scraping tasks, but we recommend using residential proxies, as they have more quality IP addresses that have much higher scraping success rates.
Any good sneakerhead will tell you that it all depends on your setup. Sure, some pick datacenter proxies for sneaker bot speed, while others swear by residential IPs for higher add-to-cart rates. A good advice is to use both. Datacenter proxies are very fast but easy to block, so we recommend setting up DC proxies for monitoring tasks.
They do get banned a lot more often than residential IPs, but for some Adidas drops you might slip through with datacenter proxies too.
Shopify is one of the most difficult sites to bot right now. Datacenter proxies on Shopify are sitting ducks – you get the speed and the subnet bans. Use residential proxies instead.
Speed was tested using Python requests and time libraries by noting the time before sending a request and after receiving a response. We sent 500 requests per endpoint to the http://ipinfo.io/ip website. After receiving 500 HTTP 200 response codes, we divided the total time by 500 to determine the average response time. We tested speed with both US and European endpoints. Requests were sent from a US VPN server when connecting to US proxies and from Germany’s VPN when connecting to European proxies. The test was conducted using a rotating session type with Python 3.9.6. version. Check the Python code example in our help docs.