📘 Knowledge Base

Jetproxy is a residential proxy platform based on a peer-to-peer network with 40M+ residential IPs worldwide. We provide residential IP addresses for regional QA, market research and permitted automation where location accuracy and route stability matter.

Simple analogy: you are the customer 🍔, the proxy is the courier 🛵. The courier handles a request through the selected route, so your team can check how a website, product or service behaves from a specific region.

Our IP addresses are sourced from a peer-to-peer network of real users. People voluntarily and legally install a special application on their devices, share part of their internet bandwidth, and receive compensation.

IP addresses from a P2P network of real user devices. This is Jetproxy’s main product. Compared with datacenter routes, residential addresses are better suited for regional QA, availability checks and market research that depends on local network context.

Residential proxy traffic is purchased in gigabytes. The larger the volume, the lower the price per 1 GB. Purchased traffic is non-expiring — use it whenever convenient, it never expires.

We accept several payment methods — choose the one that suits you:

In the proxy generation window, set the required parameters. Brief overview of each:

Generated proxies can be used anywhere HTTP or SOCKS5 is supported: standard browsers, QA tools, permitted data collection pipelines, automation tools and internal services.

login:password@host:port

Use residential routes to check local creatives, landing pages, search results and tracking flows from the regions where your campaigns operate.

• Review local landing pages and ad destinations before launch
• Keep QA sessions stable while checking approved campaign flows
• Use IPs from the target audience region for accurate previews

Assign separate proxy endpoints to different client projects, QA environments or internal workflows so diagnostics and traffic accounting stay clear.

• Separate client projects and test environments
• Maintain consistent routing parameters for each workflow
• Track traffic usage by package, proxy list and endpoint

Residential proxies help distribute permitted data collection and monitoring workloads while keeping location and session settings predictable.

• Use multiple proxies simultaneously to distribute the load
• Disable image and video loading — save up to 40% traffic
• Choose Rotating mode for broad regional sampling

Check storefronts, prices, catalog availability and localized checkout flows from the same regions your customers use.

In Keep same IP mode, Jetproxy keeps the same exit IP while the current node remains online. This is not a fixed-duration session: the IP can change if the node disconnects or becomes unavailable.

In per-request rotation, every request gets a new random IP from your geo pool. Timed rotation changes the IP after the selected interval, for example every 5 minutes or every 1 hour. Both modes are useful when stable identity is less important than scale.

Pay for traffic in gigabytes. The number of proxies you can create is unlimited. You can generate 10 or 1,000 proxies — you only pay for the volume of data that passes through them.

Most connection issues can be read from the HTTP status returned by the proxy. Use this table before changing the whole setup.

Residential routes are dynamic. A saved proxy line gives you a stable access point and rules, while the actual exit IP depends on rotation mode, geo filters, and current availability.

• Use separate endpoints for separate workflows. This makes routing easier to debug and prevents one task from affecting another.
• If a city or ISP has Low availability, start from country or state first. Add city/ISP only when the broader route works reliably.
• For long logins, checkouts, or account sessions, use Keep same IP while available or a longer timed interval.
• Different ports are parallel endpoint slots. They are useful for concurrency, but they do not guarantee a permanent fixed exit IP.
• Choose the closest gateway region when latency matters. A farther entry point can add delay even if the exit country is correct.

Crypto payments in Jetproxy are processed through a CryptoCloud checkout page. Jetproxy creates an order and invoice, you send the exact amount in the selected coin and network, CryptoCloud tracks the blockchain transaction, and Jetproxy activates the package automatically after payment confirmation.

1. 1Jetproxy order. Choose a traffic package, apply a promo code if needed, and continue with cryptocurrency payment.
2. 2CryptoCloud invoice. An external checkout page opens with the INV number, currency, network, exact amount, address, and timer.
3. 3Wallet transfer. Send funds in the selected network and make sure CryptoCloud receives the invoice amount after any fees.
4. 4Network confirmations. CryptoCloud waits for blockchain confirmations. Timing depends on the selected network and its current load.
5. 5Package activation. After successful payment status, Jetproxy marks the order as paid and adds the purchased traffic to your dashboard.

Most crypto payment issues happen before the Send button is pressed. Use this short checklist before making the transfer.

• The coin in your wallet matches the invoice coin: for example USDT, BTC, ETH, or TON.
• The network matches exactly: TRC20, ERC20, BSC, TON, SOL, BASE, ARB, OP, and other networks are not interchangeable.
• The address is copied from the current CryptoCloud invoice or scanned from its QR code, with no manual typing.
• The amount received by the address will equal the invoice amount; wallet, exchange, and network fees are handled separately.
• The invoice timer is still active. If it is almost expired and you have not sent funds, create a new invoice.
• You saved the invoice INV number and can find the TxID after sending the transaction.

This flow works for wallets and exchanges. Button names may differ, but the logic is always the same: selected coin, selected network, address, exact amount, confirmation.

1. 1Choose CryptoCloud. Select cryptocurrency in the Jetproxy payment form. We create the order and send you to the secure CryptoCloud checkout page.
2. 2Choose coin and network. On the invoice page, pick the coin and network you want to use. Enter email if CryptoCloud asks for it for notifications.
3. 3Copy address or QR. Use the copy button or QR code. Do not type the address by hand: one wrong character can make the funds unrecoverable.
4. 4Open wallet or exchange. In Send, Withdraw, or Withdrawal, choose the same coin and the same network shown on the invoice.
5. 5Enter amount with fees. CryptoCloud must receive the invoice amount. If your exchange deducts the withdrawal fee from the amount, increase the sent amount by that fee.
6. 6Check everything again. Before confirming, verify the address, network, amount, and invoice expiry time. Blockchain transactions are irreversible.
7. 7Wait for confirmation. After sending, save the TxID. When the network confirms the payment, the invoice status changes and Jetproxy activates the package.

The invoice shows the amount that must arrive at the CryptoCloud address. Fees from your wallet, exchange, or network must not reduce that amount. Providers handle fees differently: some add the fee on top, while others subtract it from the withdrawal amount.

A crypto network (blockchain) is the route used by a transaction. The same coin can exist on several networks, so it is critical to choose the exact network shown on the CryptoCloud invoice.

The invoice is considered paid after CryptoCloud sees the transaction and receives the required number of network confirmations. Jetproxy then receives a notification and activates your traffic automatically.

TxID is a unique transaction identifier on the blockchain. It is needed to confirm payment or track transfer status. In a blockchain explorer, a TxID shows the sender, receiver, amount, status, and fee.

Explorers let you track a transaction in real time. Paste the TxID into the explorer for the correct network to see status, amount, and confirmations.

Below are the most common situations from CryptoCloud and Jetproxy payment support. Almost every case is resolved faster when you have the invoice INV number and transaction TxID.

The more precise the data, the faster the invoice can be checked. Never send private keys, seed phrases, 2FA codes, or wallet access. Support will never need them.

Official CryptoCloud help pages: CryptoCloud End Users · CryptoCloud Issues