Rotating residential proxies on infrastructure we own
One stable endpoint, a residential IP behind it that you can change whenever you want. Billed per key per day in credits, with no bandwidth tiers and no seat fees.
Our own lines, not resold
Every IP is a live PPPoE session on FPT fibre we operate ourselves. No upstream reseller deciding who else shares your subnet, and no pool of unknown provenance.
Rotate on demand
Change the residential IP behind your key whenever you want, from the dashboard or a single API call. Minimum 60 seconds between changes.
Rotating or sticky, your call
A rotating key refreshes itself every 30 minutes so you never write a scheduler. A sticky key holds one IP until you change it, for flows that tie a session to an address.
HTTP and SOCKS5
One credential works for both. Paste it into curl, a browser, a scraper, or any client that speaks either protocol.
Pricing
Paid from the same credit balance as the rest of SerpPortal. Buy a key for as many days as you need; renew it in place before it lapses.
1 day
4,000 / key / day
1 week
4,000 / key / day
1 month
best value4,000 / key / day
- Unmetered bandwidth
- HTTP and SOCKS5 on one credential
- Rotate from the dashboard or the API
- Renew in place, credentials never change
The rules, up front
The constraints that actually affect how you use these, stated before you buy rather than discovered in an error message.
Questions
- Does my endpoint change when the IP rotates?
- No. You always connect to the same gateway host and port with the same username and password; only the residential IP behind it changes. Nothing to reconfigure, and no window where your client points at a dead address.
- How do I rotate from code?
- GET /api/v1/rotate?key=<token>:<secret> against the gateway API. It returns the new IP and when the next change is allowed. There is also ?checkOnly=true to read the current IP without spending a rotation.
- What happens when a key expires?
- It stops resolving and the IP returns to the pool. You can renew it in place for up to 7 days afterwards, which keeps the same credentials so you do not have to re-paste anything into your clients.
- What are these good for?
- Anything that needs to originate from a real Vietnamese residential connection: local SERP checks, ad verification, price and availability monitoring, QA of geo-targeted flows.
- What do you log?
- Per connection: the time, your key, your source address, the egress IP, the destination hostname and port, and a byte count. Never URLs, paths, query strings, headers or content. The lines are registered to us, so we have to be able to answer a lawful request about traffic that left them; keeping only destination-level metadata is the shallowest record that can. Kept 24 months, then deleted.
- Is anything blocked?
- Gambling destinations are tagged and may be refused, because operating or facilitating gambling is illegal in Vietnam. Otherwise nothing is filtered. If a category you need is being caught by a keyword rule, tell us and we will look at it.