Latest updates and improvements to FourA
We updated robots.txt with a clear stance for 2026. Search engines and social previewers (Facebook, LinkedIn, Twitter, Slack, Discord and friends) are explicitly welcome. AI training crawlers are not.
Sharing a FourA link on Twitter, Slack, LinkedIn, or Discord used to fall back to one generic card. Every public page now has its own preview image with the right title and chips. Small detail, but it shows up every time someone shares us.
We just put up a /jobs page with two open positions. If you like building real systems instead of stitching together SaaS, take a look. We work in-house on every layer, ship constantly, and treat OSS as a first-class neighbour.
Dead exits now get evicted from the picker instead of retried, so response times hold under sustained load. In our load tests p95 sits under 500ms.
Smart picker, round two. The working pool used to grow as we discovered new proxies, and slower ones snuck back into rotation. Now it drops them on the fly, so response times hold steady whether you've been running ten minutes or ten hours.
Proxy selection used to be random. Now Proxy Finder remembers which proxies performed well for each destination, and picks those first. Early requests still sample a few to build the picture. After that, you should see steadier response times and fewer slow tails on repeat targets.
We tightened up our rollouts. When we ship a new version of Single, Proxy Finder, or Browser, the load balancer waits for each new instance to be actually ready before routing traffic to it. The brief blips you might've seen during our release windows are gone.
Country and continent fields on proxy lookups are more accurate now. We promoted the heavier-weight geo data source to authoritative and dropped the lighter one to fallback. Border-region IPs that used to flip between countries stay put. Filter by country in Proxy Finder, and your results should be steadier.
If your sign-in used to land on a raw 400 page after a stale tab or a slow callback, that's fixed now. We detect the session mismatch, wipe the bad cookie, and send you back to the login screen. Cleanly, every time.
New proxies stay inactive in Proxy Finder until validation confirms they actually work. Before this fix, fresh imports could be picked for live requests before anyone confirmed they were responding, which dragged down first-attempt success rates. That path is closed now.
We pruned two dead source feeds and added 25 new ones. Input validation got tighter too, so non-IPv4 hosts and unknown protocols never enter the pool. The result is a larger, cleaner pool feeding Proxy Finder.
We now return a 503 when our service is briefly unavailable, and a 502 when a response can't be parsed. Both replace the old generic 500. Your retry logic can trust the status code now.
Proxy Finder now keeps its ranking data across restarts. After a deploy, your requests route through proven-good proxies right away instead of waiting for the picker to warm up again. The first-request slowdown that used to follow restarts is gone.
Proxy Finder pulls in newly validated proxies incrementally now, so fresh IPs land in rotation seconds after they're verified. Stale ones drop out on the same cadence. If you've seen the occasional retry on a proxy that just died, that window's smaller.
Single, Proxy Finder, and Browser each get their own filter chip on the Overview tab. Pick one to see just that product's summary, timeline, and outcomes. Activity rows now carry matching colored symbols so you can scan the table fast.
