Answers, including the inconvenient ones
If what you need is not here, open a ticket — a person reads them, and the answer usually ends up on this page afterwards.
delivery < 60s after payment clears protocols HTTP + SOCKS5, same port auth user:pass or IP whitelist blocked 25, 465, 587, 22 (no opt-out) usage hourly rows, kept 12 months
Choosing and getting started
Quick answers before you launch.
If a ban on the address would cost you real money, buy dedicated: nobody else can spend its reputation. If you mainly need a lot of addresses cheaply and can tolerate the occasional flagged one, buy shared at roughly 60% less per IP. Running all three on one account is normal — datacenter for volume, residential for the targets that refuse it.
Both are available. Datacenter (dedicated and shared) runs on nodes we operate: cheapest, fastest, and the right tool wherever the target does not specifically reject datacenter ranges. Residential leaves through an upstream partner's consumer connections, is billed per gigabyte, and is what you reach for when a datacenter address gets refused.
Point your client at the host and port from your client area and authenticate with the username and password shown there, or whitelist your own server's IP and connect without credentials. The same endpoint speaks HTTP and SOCKS5.
Provisioning starts automatically when the invoice is paid and normally finishes in under a minute. If a node is at capacity your order waits in the queue with a visible status rather than failing quietly.
Use the bulk export in the client area. It produces a plain ip:port:user:pass list for every proxy on the account — the format almost every tool already expects.
Billing
Quick answers before you launch.
Per IP, per month, in advance. The billable fact is the assignment, not the traffic: each proxy carries a preset allowance, and the price does not move with what you use inside it.
Prices are set in USD and shown in USD or BDT — switch in the header. We accept card via SSLCommerz, plus bKash and bank transfer for customers in Bangladesh.
Yes. The rate follows the quantity on the service, so crossing a published break lowers your per-IP price from the next invoice without you having to ask.
Proxies are suspended rather than terminated and the addresses are held for you through the grace period. Pay and service resumes on the same IPs. Termination is announced before it happens.
If an IP is dead on arrival or unusable for what you bought it for, tell us within 24 hours and we replace or refund it. After that, proxies are a consumable service and refunds are handled case by case.
Acceptable use
Quick answers before you launch.
No spam or unsolicited mail of any kind, no attacks or intrusion attempts, no malware distribution, and nothing illegal in Bangladesh or in the region the node sits in. Outbound mail and SSH ports are blocked at the network level, so the first of those is not merely forbidden but impossible.
We investigate the same day and contact you. A genuine, ongoing problem gets the address pulled quickly, because one burned range harms every customer on it. A disputed or one-off complaint gets a conversation first.
No. We record byte counts per account per hour because invoices and disputes depend on them. Destinations and content are not recorded.
250 GB per IP each month on dedicated, 100 GB on shared, and a rate ceiling of 100 and 50 Mbps respectively. It is preset by the plan rather than chosen at checkout, so ten dedicated proxies carry 2,500 GB between them. The allowance resets on the first of the month, and reaching it stops the proxy instead of producing an overage invoice — you are never billed for traffic you did not agree to buy. Residential is different: there the gigabytes are the product, and you buy as many as you need.
Still deciding?
Five dedicated or ten shared is a small enough order to answer the question properly.
24/7 Support
Not sure which proxies you need?
Tell us the targets and the volume — we will say whether dedicated or shared fits, and whether we can supply the region.
