Latest updates and improvements to FourA
The default signature the unblocker sends is now a current major, not the old one scrapers hardcoded. Sites that had started returning static block pages to older majors return their real page on Single and Browser. Both products moved together, so a cf_clearance replay from Browser to Single still lands byte-for-byte.
Browser used to charge the 30-credit defense-solved tier only when a Cloudflare clearance cookie showed up. Now it does the same for any defense we recognise and clear, starting with SiteGround. The response also carries defenses: { present, cleared }, so you can tell which vendor was in the way even when we haven't beaten it yet (DataDome, PerimeterX, Akamai, Incapsula and hCaptcha are recognised for now, not yet cleared).
Browser responses now return defenses: { present, cleared }: every vendor the target ran, and every one we actually cleared. Billing follows the same rule. A request that clears any vendor (not only Cloudflare) is a defense solve, and vendors we recognise but can't yet beat show up in present and never raise the price.
If you pass exitCountries and your plan doesn't include geo targeting, you'll get a 403 that names the parameter and points to the fix. No more guessing which field on the request tripped the check. Plans that do include geo targeting are unaffected.
The plan compare table now has a bandwidth row. Every public plan comes with unlimited bandwidth, so egress won't quietly eat your budget as your traffic scales. Custom plans show their exact GB figure when they're capped.
Any worker that dropped out between releases used to stay offline until someone noticed, quietly dragging peak-hour capacity. Now every rollout brings the full pool back to strength alongside the rolling update, so traffic peaks land on the capacity you expect.
Usage & Limits now has per-tab attention dots, colored usage bars (amber at 80%, red once you're over), a sortable Last used column and 30-second auto-refresh. Open it from the sidebar in your Dashboard.
The pricing page compare table is now grouped by usage, features, rate limits, and account. Every cell comes from the same plan model the API reads, so what you see there is what your plan actually includes. Bandwidth is uncapped on every public plan.
Proxy Finder now runs its three liveness checks concurrently instead of one after another, so dead exits get recycled roughly three times faster. A head-of-line fix keeps validation throughput steady when one subnet hits its rate limit. Expect fewer stale proxies picked for your requests.
Proxies now get validated continuously from a separate network path, so the working pool only holds exits that actually work right now (not just when they were first found). When you call /api/proxy or let /api/auto route your request, the picked proxy is more likely to work first try.
The API blocks any Single or Browser request whose target URL, follow-redirect chain, or proxy field resolves to a private or reserved IP range. Even if a public target redirects into an internal network, the request stops before it gets there.
The language switcher across the main site, blog, docs, and Updates portal got an overhaul. Each option shows the language's native name plus its name in your current UI language (so 'Deutsch · немски' on the Bulgarian site), with a search box that filters all 13 locales by name, code, or locale id. Each option is now a real link with hreflang, so search engines and AI crawlers can follow every translation, and you can cmd-click to open another language in a new tab. The switcher also lives in the footer of every site.
Auto used to ratchet a host's session TTL downward on every replay failure, even when the failure didn't reflect a real cookie expiry. Sessions kept getting evicted and re-solved while their cookies still worked. The TTL now grows on aged successes and only retreats on real expirations, so a learned session for a Cloudflare-cleared host can carry across several minutes instead of dying after the first 403.
Auto sessions now adapt to what each target needs. Sites without interactive challenges run as portable sessions where cookies ride the proxy pool, so rotation and failover come automatically. Sites that bind their unlock to one exit (interactive Cloudflare being the main one) get pinned with a per-clearance concurrency cap, so a burst of replays can't burn through your unlock.
Request previews in Activity now show the opaque proxy ID everywhere, matching what responses already returned.
