Proxies

What it's for

Umbra doesn't sell exits. You bring your own pool of proxies; Umbra tests each one, hands a single exit to each Account, and rotates them only on the rules you set. The result is that every Account browses from its own place, and no two Accounts share an IP by accident.

Come here when you first set up, when you add capacity before a drop, or when one Account's exit goes bad mid-week.

Add your proxies

Don't reuse a burned exit

An exit that browsed for an account carries that account's history with the site. Delete a banned Account, scroll the list, and hand its old exit to a fresh Account, and you've given the new one a head start on the same fate — a reused exit tends to burn faster.

So Umbra remembers every exit that has ever been attached to an Account, and keeps that memory even after you delete the Account. A used exit is marked in red everywhere you can pick a proxy — the Account's own picker, the per-Session picker in the address bar, and the Connections list — so the warning is in front of you at the moment you choose, not after. The mark never says which Account held it; it only says this one has been used.

To see the history — which Account names an exit carried and when, so you can rebuild one you've lost from the record — open the exit and read Previously attached to.

Test before you trust

Testing an exit does two jobs at once. It confirms the exit actually answers, and it reads back where that exit comes out — its country, city and time zone. Those readings are what Umbra later copies onto any Account you place behind the exit, so its clock and locale match the place it appears to browse from.

Prove it doesn't leak

Testing confirms an exit answers. Verify goes further: it opens a throwaway session routed through that exit and runs a WebRTC leak check on it — the same class of leak that can surface your real address around a proxy. Umbra never runs this check on a direct connection; if the exit can't be routed, the verify refuses rather than probing your real network.

Health at a glance

The Speed cell prints the last reading, and the result strip above the table sorts every exit into Good, Slow, Failed, Blocked or Not tested — click one to show only those. The state decides whether an exit can be handed to an Account.

Assigning and rotating exits

Umbra spreads your pool evenly — one exit per Account — and rotates on the trigger you choose: on launch, on a timer, or when a health check finds an exit has died. A Session that's holding a live cart is never rotated out from under you.

What "eligible" really means

Every place that picks an exit — first assignment, rotation, de-link, and bulk distribute — runs the same eligibility rule. That one shared rule is why a dead or blocklisted exit is never handed out anywhere.

If a bulk distribute can't cover every Account, it doesn't force a bad assignment — it leaves the uncovered Accounts exactly as they were and tells you the shortfall. Read that banner: an Account it couldn't cover keeps whatever exit it had, including none at all.