Almost every question about our proxies is answered here. Pick a topic and open the question you need.
Most of our proxies are datacenter proxies. When you check the IP, you'll see the address of the datacenter where the server is hosted. These are NOT residential or mobile proxies. The one exception is our ISP proxies: these are static residential proxies (the IPs belong to internet service providers but are hosted on our servers), combining the stability of datacenter proxies with the trust of residential ones. Keep this in mind before buying a proxy package.
Our packages are shared proxies, used by 3–5 people at a time. The IP lists aren't built in advance — with each new order, the package is generated automatically from our pool, so different users will never get the exact same set of IPs. Even if two users hit the same target in the same region, they'll have different IPs in their packages and won't hit that site twice from the same IP. This is how we can offer proxies at a price far below most competitors, while they perform much like dedicated IPs that can cost many times more.
Keep in mind that when buying several large packages from the same region, you may get duplicate IPs across packages. This comes down to how we balance load — the least-loaded IPs are handed out first. We do our best to avoid this when building the lists for identical packages, but the chance is still there. If you run into too many duplicates, reach out to support and we'll help.
Datacenter proxies are IP addresses hosted in data centers; no real home users sit behind these IPs — they aren't tied to any household connection. They're a good fit for most business use cases, with low cost, high stability, and unlimited bandwidth. That said, we don't recommend them for use cases where the target scrutinizes every user in detail (anti-fraud checks) — for example, signing up at betting sites, registering with banks and payment services, claiming cash bonuses across various platforms, and the like. For everything else, datacenter proxies offer an unbeatable price-to-performance ratio.
ISP (Internet Service Provider) proxies are static residential IP addresses that officially belong to internet service providers but are hosted on our servers in data centers. That gives them the best of both worlds: the trust of residential addresses (sites see an ordinary home connection from an ISP) plus the speed and stability of datacenter proxies.
Their key traits: they're static (the IP doesn't change during the paid period), fast, and come with unlimited bandwidth, and they enjoy higher trust from websites than regular datacenter proxies. They're a good fit wherever you need both IP trust and performance at once. Learn more on our ISP proxies page.
Datacenter proxies are hosted in data centers — a check will show the datacenter's IP. Residential proxies use the IPs of real home users.
ISP proxies are static residential IPs that belong to internet service providers but are hosted on our servers. They combine the trust of residential addresses (sites treat them as an ordinary home connection) with the speed and stability of datacenter proxies. That makes them a good fit wherever you need both IP trust and high performance at once. Learn more on our ISP proxies page.
Dedicated proxies are IP addresses that belong to you alone for the entire paid period. You don't share the bandwidth, connection limits, or IP reputation with anyone else.
In practice, that means you get the full bandwidth and all the connections in the package; the address's reputation depends only on your activity, not other users'; and you get higher stability and predictability. Dedicated proxies cost more than our shared packages, but they give you maximum control and suit use cases that need a clean personal IP — account management, social media and messaging apps, and access to streaming services. You can get them on our dedicated proxies page.
Rotating (backconnect) proxies work differently: you connect to a single entry point, and on each request the system automatically hands you a new IP from the shared pool. You don't see or manage specific addresses — rotation happens on our end. This is handy for web scraping and working with third-party APIs, where automatic IP rotation matters. How requests are counted on rotating proxies is covered in “What are API credits in rotating proxies?”.
Our proxies cover a wide range of use cases, and they're a great fit for most common scenarios. First and foremost they're built for professionals who need large-scale data collection, but they work well for everyday use too.
The most common use cases: web scraping and data collection (marketplaces, search results, price monitoring), SEO monitoring across regions, ad verification, multi-account management on social media and messaging apps, access to regional and media content, streaming, automation via bots and APIs, testing, and getting around geo-restrictions.
Either way, you can always start with a free trial or request a refund within 24 hours of payment.
If a package says 100 IPs, you get 100 different IP addresses. Different ports on the same IP don't count as separate proxies. So “100 IPs” always means 100 unique addresses, not a single address opened on several ports.
No, we provide IPv4 only — it's universal and works for virtually every use case.
We avoid IPv6 on purpose: the protocol has real downsides. Many sites and services still don't support it, or treat such addresses with suspicion. IPv6 is also handed out to providers in huge blocks, so it's easy to recognize an address as part of a “batch” and block whole subnets at once. The result is noticeably lower stability and compatibility, whereas IPv4 delivers a predictable, clean result.
These niches (bookmakers, payment services, casinos) run strict anti-fraud systems that scrutinize every user in detail. Datacenter IPs are relatively easy to identify, so they're usually a poor fit for this kind of task. What you typically need here are residential or mobile proxies, which we don't offer.
If you don't already have experience running datacenter proxies on such a target, we recommend starting with a free trial or using the 24-hour refund window — that way you can check risk-free whether our proxies fit your use case.
Proxies are issued automatically right after payment. If you don't receive access within 10 minutes of paying, please contact support.
Yes. You can get a free trial that runs for 60 minutes. Or, after buying a package, you can request a refund within 24 hours of payment.
You can pay in many ways:
Cryptocurrency: USDT (TRC20/ERC20), USDC, Bitcoin, Ethereum, Litecoin; Credit/debit cards: Visa, Mastercard, American Express; Other methods: Stripe, AliPay, WebMoney.
Pay with cryptocurrency and we add a bonus worth 10% of the invoice amount to your balance (more in “How do I earn and use bonuses?”). The current list of available methods is always shown on the invoice payment page in your Dashboard.
You can get a full refund if the proxies aren't a fit — just request it within 24 hours of purchase.
Refunds are issued using the same method you used to pay for the service. To request one, just contact support. You can find the detailed refund rules here.
After the first 24 hours, you can cancel an order and have any unused funds credited to your account balance. You can cancel an order once every three days from your Dashboard, without contacting support.
You can renew a service from the “Products/Services” section of your Dashboard, for any available term. Auto-renewal is available too: payment is charged automatically from your account balance, or — if you've paid by card before — from your saved card.
When you renew the same service, your IP addresses stay the same — the list doesn't change unless you refresh (replace) the IP list yourself (see “I bought a proxy package, but I want to refresh the IP list”). This lets you keep working without reconfiguring whitelisting or your software.
When you pay any invoice with cryptocurrency, a bonus of 10% of the invoice amount is immediately credited to your account balance. Bonuses don't apply as an instant discount on the current invoice; instead, they're added to your dollar balance in your Dashboard.
You can use accrued bonuses to pay for new purchases or to renew existing services — apply them toward part of the invoice and pay the rest as usual.
Bonuses can't be cashed out or transferred to other accounts; they can only be used to pay for our services. The bonus balance is displayed in dollars in your Dashboard and updates automatically after each cryptocurrency payment.
Unfortunately, no. The minimum term is 30 days; after that, you can renew for a longer period. You can request a refund within 24 hours of payment if the IPs aren't a fit for your use case for any reason.
For the full term you've paid for. Our proxies don't “die” during the paid period: if your package runs for 30 days, the proxies will work the full 30 days without replacement. The same goes for a 365-day term.
All our proxies use mandatory IP whitelisting — they only work from the IP address you whitelist. This isn't just a technical requirement; it's an important feature that gives you real advantages.
IP whitelisting lets us give you truly unlimited bandwidth and full speed on every proxy, so you can use them to their full potential without worrying about limits. It also maximizes security, since only you can use your proxies. Even if your username and password leak to a third party, they won't be able to use the proxies from another device, which keeps your data and your work protected.
To set it up, find the real public IP of the computer or remote server you'll run the proxies from (disable any VPN before checking). You can do this at showmyip.com. Write down the IP you get.
Next, in your Dashboard (https://papaproxy.net/panel/clientarea.php?action=services), open your active service.
On the service page you'll see the username and password for proxy authentication, plus a field where you enter the IP you got from showmyip.com. Enter your IP and click “Set.” It may take 1–5 minutes for the change to take effect, after which your proxies are ready to use.
In the “Products/Services” section of your Dashboard, click your active service. The username and password for proxy authentication are shown just above the field where you whitelist your IP.
We support the HTTP, HTTPS (HTTP/2), SOCKS5, and SOCKS4 protocols — all available at the same time, differing only by port. Every proxy list we issue already includes the port: just download your list from your Dashboard, and the port is shown next to each IP.
Ports by protocol and authentication method:
Protocol
IP whitelisting
IP + username/password
HTTP
8085
8080
HTTPS
8444
8443
SOCKS5
1085
1080
SOCKS4
1087
—
HTTPS also has a backup port, 993, which you can use in addition to 8444.
* SOCKS4 has no username/password authentication in the protocol itself, so it's available via IP whitelisting only.
A note for developers: SOCKS4 and SOCKS5 run on separate ports.
Most providers combine SOCKS4 and SOCKS5 on a single port. As a developer-focused service, we deliberately keep them apart — SOCKS5 on 1085, SOCKS4 on 1087. This matters because some software is built on the outdated SOCKS4 protocol but labels it “SOCKS5.” In that case our SOCKS5 port may not work with it — point such software to our SOCKS4 port (1087) instead.
Every proxy works over several protocols at once — HTTP, HTTPS (HTTP/2), and SOCKS5 (plus SOCKS4). There's nothing to switch: they're all available at the same time and differ only by port.
HTTP — the standard protocol for web traffic: loading sites, scraping pages, working through a browser. A universal choice for most use cases. HTTPS (HTTP/2) — the same, but over an encrypted channel with full CONNECT support, so your traffic stays encrypted on the leg between your device and our service. Choose it when connection privacy matters most. SOCKS5 — the most flexible proxy protocol: it works at a lower level and passes any kind of traffic, not just HTTP, which suits non-standard protocols, desktop applications, and high-throughput workloads.
If you're unsure, start with HTTP (port 8080 with username/password authentication) or use HTTPS for an encrypted channel. The full port table is in “What ports and protocols do you support?”.
Quick clarification: HTTP, HTTPS (HTTP/2), and SOCKS5 are protocols, not formats, and they're all available at the same time (nothing to switch).
The proxy list itself can be downloaded from your Dashboard in TXT, CSV, and JSON — with the right ports for username/password or IP (whitelist) authentication. There's also a format builder: you set the field order, separators, and line template to match your software.
On top of that, there's a link to import the whole list straight into your program, and a separate link that returns one random proxy from your package on each request.
Yes, you can. If your ISP changes your IP address within the same subnet, IP whitelisting in your Dashboard will keep working without constant updates.
Simply enter your current IP in the settings, use username/password authentication, and the system will automatically determine the allowed range in which your proxies will remain accessible. For HTTP proxies with authentication, use port 8080. For SOCKS5 proxies with authentication, use port 1080.
How does it work?
If your IP is, say, 85.249.3.145, the system automatically expands the range to 85.249.0.0–85.249.7.255 (a /21 subnet mask). Even if your IP changes within this range, the proxies will keep working without interruption.
Additionally, you can check your range using a CIDR calculator, for example here, but you don't need to whitelist the entire range manually — the system will handle it automatically.
Yes. By default any package can be whitelisted to several of your external IPs — up to 10 addresses in the whitelist. That's enough to use one package on several devices or servers at once.
The concurrent connection limit (more about limits) is shared across all whitelisted IPs, and you control how it's split from your Dashboard.
If you need more than 10 IPs in the whitelist, extra entries can be added for a fee through support. Alternatively, split a large package into smaller ones and whitelist each to its own IP.
No, whitelisting is mandatory — and it works in your favor: it's exactly what lets us give you truly unlimited bandwidth and full speed, while keeping your proxies safe from outsiders. Even if your username and password leak, no one can use the proxies from another device (more in “What is IP whitelisting and why is it needed?”).
If you have a dynamic IP, the proxies work with username/password authentication within a /21 mask — no extra setup needed. If you plan to use one large package across different servers, whitelist it to several of your IPs (up to 10) or split it into smaller packages and whitelist each to its own server.
Our proxies are universal and work anywhere you can specify an HTTP, HTTPS (HTTP/2), or SOCKS proxy: on Windows, macOS, and Linux, on servers (VPS/VDS), in browsers, antidetect browsers, scrapers, bots, and most desktop applications.
The one requirement: your traffic must originate from the device (computer or server) whose IP is whitelisted to the package in your Dashboard. Mobile devices and apps can use the proxies too, as long as they go online from the whitelisted IP. More on whitelisting in “What is IP whitelisting and why is it needed?”.
Every server has an 80 Gbps uplink. We don't apply artificial caps to proxy speed, which reaches up to 500 Mbps per proxy. You can read more about speed here — https://papaproxy.net/fast-proxy.php. Please also stay within the bandwidth fair use guidelines for your plan — see our Terms of Use.
No, bandwidth is genuinely unlimited — there are no data caps, and your speed doesn't drop no matter how much you transfer. We only ask that you stay within the bandwidth fair use guidelines for your plan (see the question about speed above).
It depends on your package. The limit is aggregate — it applies to the whole service, not to each IP.
Packages up to 999 IPs: 1,500 concurrent connections.
From 1,000 to 4,999 IPs: 3× the number of IPs in your package.
From 5,000 to 14,999 IPs: 2× the number of IPs in your package.
Packages with 15,000+ IPs: the limit equals the number of IPs in the package.
You can always see your current connection stats in your Dashboard. If you need more, you can purchase additional connections — the terms are described in our Terms of Use. We explain more about threads and connections in this article.
Your service (not your entire account) will enter “Slow Mode.” In this mode, you're allowed no more than one concurrent connection per IP address in your service package. The mode is dynamic:
Up to 2 violations per day: 5 minutes.
From 3 to 6 violations: 15 minutes.
From 7 to 10 violations: 30 minutes.
More than 10 violations: 60 minutes in “Slow Mode.”
We explain more about threads and connections in this article.
Our rotating proxies are designed to work with third-party APIs. One API request = 1 credit from your plan. We count all requests based on concurrent connections. If you're working with standard websites (e.g., page scraping), one request (thread) isn't always the same as one connection. Your browser or program may send dozens of requests at once. For example:
- Loading an online store page may take 10 to 40 requests.
- A Google search can send up to 100 requests per query.
Why does this happen?
Every webpage consists of multiple elements: text, images, styles, scripts, and so on. Each element is loaded through a separate request. So opening a single page might generate 10, 20, or even 50 requests — these are concurrent connections. It all depends on the specific site and your software, which is why we can't tell you in advance how many concurrent connections will be used per thread.
When choosing a plan, keep in mind that one request to a site can generate dozens of separate connections. This matters for correctly estimating your request volume and limits.
How do I check how many requests a site makes?
Before choosing a plan, we recommend checking how many requests the target website makes. You can do this with online tools such as RequestMap: enter the URL and you'll get a map of all requests, with their number and types. For example, it shows that the page https://papaproxy.net/faq.php consumes 21 requests (credits) when opened in a browser.
No, we only break proxies down by country. There's no way to select a specific city.
You can't pick specific subnets manually — the list is generated automatically, but from a large pool: we already have over 400 class C subnets (in the 146.19.39.0/24 format), so you get the widest possible variety within a package.
The rough number of /24 subnets depends on the package size and how popular the geo is (the more popular the country, the more subnets):
— a 100-IP package — from 3 to 30 subnets;
— a 500-IP package — from 5 to 40 subnets;
— a 1,000-IP package — from 50 to 150 subnets;
— a 5,000-IP multi-country mix — from 150 to 200 subnets.
Yes. Once every 8 days, you can regenerate your IP list from your Dashboard to get new addresses. This is optional, but available whenever you want it. We can't predict what percentage of the IPs will be new, since the process is fully automated.
This option isn't available for rotating proxies: you don't see the IP list and work through our entire proxy pool. For dedicated proxies, an IP refresh is available once every 30 days.
No. The list is generated randomly from the available addresses, so you end up with the widest possible variety.
To check the geolocation of your datacenter proxies, we strongly recommend using only the authoritative tool — RIPE Database Query. RIPE is the primary, internationally recognized source of IP geolocation data.
Keep in mind that datacenter proxies can change their geolocation much more often than residential or mobile proxies. There are also third-party geolocation databases such as 2IP, MaxMind, IP2Location, Ipify, and others; they aren't authoritative and may update with a delay, which can lead to inaccurate results.
We rely exclusively on RIPE data, as stated in our Terms of Use. This ensures your IP geolocation data is accurate and current.
Note that major tech companies — Meta, Google, Amazon, Microsoft, and Apple — maintain their own geolocation databases and don't rely on third-party sources. If you know exactly which geolocation database you need, open a ticket in your Dashboard to request a report based on MaxMind, IP2Location, or Ipify for new or existing proxy packages. This is a paid service that lets us tailor a package to your specific geolocation requirements.
Check things in order of priority:
1. IP whitelisting. Make sure the proxy list is whitelisted to the current IP of the device you're working from. If your main IP has changed, re-whitelist your new IP in your Dashboard. You can't verify this through a proxy checker: the proxies are only reachable from the whitelisted IP. 2. Connection limit. Check whether you've exceeded your plan's concurrent connection limit (shown in your Dashboard). If you have, the service enters Slow Mode — see “What happens if I exceed the limits?”. 3. A block on a specific site. If whitelisting and limits are fine, check whether the IP is blocked on your target.
The quickest way to see the error code is a simple request from the terminal on the device the service is whitelisted to. Test the proxy itself, then a request through the proxy to a specific site:
If you see the proxy IP and code 200, the proxies work and the issue is with your software. Code 407 — an authentication or whitelisting issue; 429 — the connection limit is exceeded; 403 — a block on the site's side. If the problem is on our end, send us the command output through support.
Your proxy list works only from the IP address you've whitelisted in your Dashboard. Since a proxy checker runs from a different IP than yours, the proxies will appear unavailable to it.
You should only test proxies from the device whose IP is whitelisted to the package in your Dashboard. From any other IP — through online checkers or third-party tools — the proxies won't work: that's by design, not a malfunction.
Step by step: 1. Whitelist the package to the real IP of the device you'll test from (disable any VPN first). To find your IP and set up whitelisting, see “What is IP whitelisting and why is it needed?”. 2. Enter the proxy IP and port in your browser settings (for HTTP we recommend port 8080). Step-by-step guides: setup in Google Chrome and setup in Mozilla Firefox. 3. Open whoer.net (or ipinfo.io). If the site shows the proxy IP instead of your real address, the proxies are working correctly.
Without exception, all of our proxies are anonymous — your real IP is fully hidden. If it's still visible during a check, the cause is almost always a setting on your end.
The most common culprit is a WebRTC leak in the browser: even when traffic goes through the proxy, WebRTC can expose your real IP directly. Disable WebRTC (via an extension or in your browser/antidetect settings) and check again. Also make sure the proxy is applied in the right application, not just system-wide, and that any VPN is turned off. Less often, the cause is a faulty checker.
We block mail ports (SMTP, POP3, IMAP) to prevent email spam through our proxy servers. Spam and any illegal activity through our proxy servers are prohibited, as stated in our Terms of Use.
We've also blocked most of the popular proxy checkers. Your proxy package is whitelisted to the IP address of the device (computer or server) you work from, so a request from the proxy checker's external IP doesn't go through — by default the proxies are unavailable to it. In addition, we block Google to avoid complaints from the search engine — please don't use our proxies with this target. You can find a more detailed list of what we block in our Terms of Use.
Didn't find the answer you were looking for?Our support team is online and happy to help with anything proxy-related.
