August 20, 2026 · 2 min read · The Rcloak Team
Introducing Rcloak
Most rotating-proxy services hand you a single dumb endpoint and call it a day. We wanted something closer to what you'd build in-house if you had the time: a pool that heals itself, selection strategies that actually mean something, and billing that matches how bandwidth plans should work.
What's different
- Self-healing pool. Every proxy is health-checked on a loop. Three consecutive failures and it's frozen (excluded from new requests, but still retried); ten and it's gone for good.
- Four selection profiles.
randomfor even distribution,stablefor the highest success rate,fastestfor the lowest latency, andfreshfor round-robin over the newest additions to the pool. - Sticky sessions, opt-in. Add a session ID to your username and you'll keep the same proxy until it fails — useful for anything that needs a consistent IP across a few requests. Leave it off and every request gets fresh selection.
How it works
Your proxy URL encodes everything:
http://<profile>[-<country>[-<session_id>]]:<token>@proxy.example.com:8080
profile is required. Country and session are both optional and independent — you can specify
a country without a session, or neither at all.
We'll be writing more here as new features ship. If there's something you'd like covered, get in touch.