Browser opens URLs that carry an anchor
Ask Browser for a URL with #reviews on the end and the page comes back at normal speed. If anchored links were coming back as timeouts on you, that's gone.
Latest updates and improvements to FourA
Ask Browser for a URL with #reviews on the end and the page comes back at normal speed. If anchored links were coming back as timeouts on you, that's gone.
Browser now solves Cloudflare's checkbox challenge on concurrent requests to the same page, and a press only counts once the challenge is really gone. Three requests at once clear in 5 to 9 seconds.
Playground now renders the response from your target, including on sites that set large cookies, and API endpoints always answer in JSON.
If your target redirected to a different URL path, Browser used to return 'No response received' even though the page arrived. That's fixed; the request follows the navigation wherever it lands. eBay, redirect-heavy shops, and anything with a 3xx to a challenge page all work now.
A service now counts as down only when it has lost every instance, the one state where your request has nowhere to land. Routine rolling deploys no longer show up as incidents on the status page.
When your bank asked for 3D Secure on a plan upgrade, the request would poll for a change that never arrived (nobody had prompted you to authenticate). The change-plan flow now handles the extra step like the first subscribe does, so the upgrade goes through.
Browser now handles a challenge page that redirects before its body can be read, so requests to protected sites come back with content instead of an empty response.
When you send a header on Single or Proxy requests with the unblocker on (default), your value now reaches the origin as sent. Common headers like Accept and User-Agent could go out twice, and some upstreams picked the wrong one. If you noticed Accept: application/json coming back as XML, or a pinned User-Agent not being honored, that's fixed.
Credit usage warnings are paused until every account has its plan assigned. If you got a '100% used' notice, you can ignore it; nothing on your account changed.
Dropdowns, checkboxes, scrollbars, autofilled fields, and dialog buttons showed a light look on dark theme (white boxes, stray outlines). Now every control follows the active theme. Modals stop scrolling the page behind them, tooltips inside dialogs sit on top, and number inputs hide their spin buttons.
The PDF button on some paid invoices didn't render because we weren't setting the underlying link. Every paid invoice in the Invoices tab now has a working PDF button.
If you passed a negative validate to /api/auto (like {data: {fail: ['"Due to legal reasons"']}}), a Cloudflare 'Just a moment' interstitial could slip through as a cached success because the fail-list didn't happen to match its text. Auto now rejects challenge pages before applying your validate rules, and it swaps the bad exit and re-solves instead of scoring it.
If you set a long timeout on foura_auto through the hosted MCP server, the request could time out at the edge before your call finished. That's fixed. Full-budget auto calls now run their 180-second budget end to end.
If you've been hitting 429s when firing many concurrent Auto calls at one target, those calls used to funnel onto a single cached exit because the warm path picked the score-favourite and replayed once. Auto now opens additional sessions on demand and routes each call to the least-loaded exit, so a burst fans out across multiple proxy IDs instead of hammering one. Measured locally: a 100-call burst on a no-cookie portable host now spreads across the grown pool within seconds.
Cloudflare injects a passive script even on pages that pass cleanly, and Auto used to treat any reference to it as an active challenge and run a full browser solve anyway. Now only true interstitial markers (the 'just a moment' page and friends) trigger the browser path; a clean 200 comes back from the cheaper proxy rung. Auto also follows up to 5 redirects by default (configurable via followRedirects).