Latest updates and improvements to FourA
When a target's hostname doesn't resolve, Single, Browser, Proxy Finder and Auto now answer the way they do for any site they can't reach: status 0 and an error naming the host. It's recorded as a target outcome (application_fail), while private-network targets still get the 400 refusal. Outcomes reference →
Open Activity right after an Auto call and the row says its attempts are still settling, then fills in the attempt list, credits and bytes in place a few seconds later. No reload, so the row you're watching stays where it is.
Your Dashboard now counts each Auto call as one request, and the Single, Proxy and Browser attempts behind it are listed separately by name. Overview, Usage & Limits and Activity all carry the Auto product, and success and latency are measured on your calls.
The benchmarks page now tells you when the published run is more than 45 days old, read against your own clock, and points at the next monthly run. Sites change their defences without notice, so an old run is history, not a current reading.
Every run of our web scraping benchmark is now public. The script, the page list and every result live in fouradata/web-scraping-benchmark (code MIT, data CC BY 4.0), so you can run the same pages yourself and check our numbers. See the latest run
The plans page now shows how much proxy port traffic each plan includes, from 2 GB on Free to 750 GB on Business, and what an extra gigabyte costs. Both figures also sit in llms.txt for agents that read plans from there.
When an allowance reaches 95%, you get an email with the day it runs out at this period's pace, set against your reset date, and the one action that raises it. The 100% email now says how many days remain until the reset and, on plans with overage, what the rest is billed at.
On a paid plan sold by credits, the proxy port has its own included gigabytes, and you can now buy more from the Proxy port card on your Billing page. The port's usage emails offer the same top-up.
A consumption limit you've reached, such as credits, traffic, Browser pages per day or rate, now shows a red At limit, because the next request is refused. A count limit at its ceiling, such as API keys or team members, shows amber, since it only stops the next addition.
The Billing page now shows the same four cards on every plan: credits or standard traffic first, whichever the plan is sold by, then the other figure, Premium, and the Proxy port. Every card has a Buy button, and where your plan doesn't price that item it says so and offers a contact link.
Your Limits page gets a Traffic panel with the total, the API, the proxy port and premium, each with a bar wherever your plan sets a ceiling. The API keys table adds Traffic and Premium columns, and every product panel on the Overview shows its own traffic.
On phones and tablets, the menu on the main site now opens and closes the moment your finger lifts, iPhone included. It fills the screen in two columns: Products, Pricing and Tools on the left, Resources and Compare on the right, under headings that match the footer's.
Any member of an organization can now send a Playground request with its keys. The list is grouped the way the Metrics filter groups it: your own keys under My Keys, then a group for each organization you belong to.
FourA vs others now prices what each service charges for the sites that turn a plain address away, per 1,000 requests, and shows how many requests each plan runs at once. Bright Data, Oxylabs and Firecrawl join the tables, every figure read from the service's own pricing page and dated.
A request the standard pool answers before any premium exit is tried still costs no premium traffic. Once a premium exit has been tried, the bytes it carried count toward your premium allowance even if that attempt didn't bring back the page. Your plan's traffic ceiling counts standard bytes only.
