Latest updates and improvements to FourA
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.
We tightened proxy redaction in stored request payloads. Before, an internal upstream proxy address could leak into the Activity log preview when the original request was mutated for forwarding. Now any raw proxy URL in a stored payload is replaced with the opaque proxy ID (or with [redacted-proxy] if there's no ID to restore). The visible response was already opaque; this closes the same loop on the request preview.
Every Auto response now carries a meta object (which rung won, whether a challenge was solved, attempt count, total credits) plus the working session (proxy, cookies, userAgent) so you can see what cracked the target and replay it yourself. The session.proxy field is the opaque base36 proxy ID, never a raw address. Set returnSession: false if you don't want the session in the response.
Auto now handles non-interactive Cloudflare challenges (the "Checking your browser" wall some protected sites serve) end-to-end, instead of returning the challenge page as if it were content. Two related cases also got fixed: a transport 200 hiding a challenge interstitial now escalates to a real solve, and a challenge that re-serves the wall after dropping a clearance cookie now reloads and pulls the real content. Marathonbet is the headline site that newly passes; vinted and a few other interstitial-on-200 targets also benefit.
Refreshing the Playground no longer flashes the static state before yours reappears. A new Reset button (behind a confirm) clears all three request tabs, cookies, and carried proxies in one go. A response can now also carry its proxy ID or User-Agent into the next request when you ask for it, instead of auto-applying behind your back.
Each Single response now includes the proxy ID that handled the request, and Browser responses do the same. Useful for chained calls that need to stick to the same proxy.
Click a column header in the Dashboard to sort it. Works on Activity, API Keys, and sessions, survives the auto-refresh, and Ctrl-click (Cmd on Mac) clears the choice. The sidebar also collapses to an icon rail when you want the table to breathe.
Activity used to show raw outcome strings like Application_fail while Overview used friendly labels (App Fail) with proper colors. Activity now uses the same labels and colors, so the two views read the same.
Authenticated calls now come back with an X-Foura-Request-Id header. Stash it in your own logs and you can match any request to its row in Activity, or hand it to support so we can look up exactly what happened on our side.
Hit the new Cancel button while a playground request is loading and we abort it cleanly. The panel snaps back to idle with a 'Request canceled' note instead of a scary network error.
