← All proxy documentation

Froxy

Point a browser profile at Froxy residential proxies. Three steps, no plugin, no proxy-auth extension.

Froxy Fast proxies: one gateway, with the targeting kept in a saved filter in the dashboard rather than in the credential. Measured on a live account, not read off a docs page. Froxy sells residential and mobile pools separately - the filter logic and the fast.froxy.com gateway below are the Fast product, confirmed by Froxy after this page first went up.

https://froxy.com/en/fast-proxies

1. Get the credentials

In your Froxy dashboard, open the residential product and copy the gateway host, the port, and the username and password. Everything below assumes those four values.

2. Build the proxy URL

One string, credentials included. Targeting and session options go in whichever half this provider puts them in - the table below says which.

http://<filter login>:<filter password>@fast.froxy.com:10000

3. Launch

Timezone, locale and WebRTC are derived from the exit address, so a US exit does not arrive with your own timezone attached.

await ab.launch({
  profile: 'acc-01',
  proxy: 'http://<filter login>:<filter password>@fast.froxy.com:10000',
})
launch(
    profile="acc-01",
    proxy="http://<filter login>:<filter password>@fast.froxy.com:10000",
)

Prefer not to run an account at all? Managed residential proxies are included on paid plans.

Parameters

Read off Froxy's own documentation on 2026-09-14. Ports and endpoints differ by plan and by zone, so where this table and your dashboard disagree, the dashboard is right.

Gateway fast.froxy.com
Ports 10000-10999, as printed under the filter's own Show Details panel. Each port is a separate exit: 10000 and 10001 came out on different continents in the same minute.
Protocols HTTP. The panel hands you a ready Proxy URL in user:pass@host:port form.
Options ride in the port number
Country targeting Not in the credential. Country, region, city and ISP are dropdowns on the filter you save in the panel, and the credential the filter issues is what carries them. The readings below were taken with the filter left on All Countries.
Sticky session An IP Rotation setting on the filter, 90 seconds by default. The exit is tied to the port, so hold a profile on one port to hold one identity.
Session length Set per filter in the panel; five filters per subscription, 1000 ports on the plan tested.
Source https://help.froxy.com/en/how-to-connect-to-fast-proxies

Worth knowing

  • Nothing works until a filter exists: before that the subscription page says so in as many words, and there is no host or port to copy anywhere on it.
  • Measured on 2026-09-14 with AntiBrow, one profile per port: port 10000 exited in Belarus (178.120.172.109, Beltelecom, Pinsk) and port 10001 in the UK (88.97.195.205, YouFibre, Stockton-on-Tees). Both exits sat on consumer ISPs, which is what the Fast pool is drawn from; the plan tested was Fast 5.
  • The browser timezone followed the exit both times - Europe/Minsk on the Belarus port, Europe/London on the UK one - while the locale stayed at the profile's configured en-US. Timezone follows the exit; language does not, and you set it on the profile if the site should see a local one.
  • No WebRTC leak: the only ICE candidate carried the exit address itself, with no local or host address alongside it.