Skip to main content

Load Balancing

Dedicated Workers' Load Balancing​

Your workers run in one of four locations: San Francisco, New York, Amsterdam, or London. Requests to https://chrome.browserless.io route to one of the four regions automatically.

To reduce latency, connect through the load balancer nearest to your servers:

  1. West load balancer (SFO): https://chrome-us-west.browserless.io
  2. East load balancer (NYC): https://chrome-us-east.browserless.io
  3. UK load balancer (LON): https://chrome-eu-uk.browserless.io
  4. AMS load balancer (AMS): https://chrome-eu-ams.browserless.io

Dedicated Worker IP Addresses​

Each dedicated worker's public IP is shown beneath its title in the Workers section of your cluster page. Click the IP address to copy it. Use these IPs if you need to allowlist traffic from your dedicated workers. For shared fleet IPs, see Whitelisting IP Addresses.

IP addresses change on Relaunch

When you Relaunch your fleet, new VMs are provisioned and worker IP addresses change. Update any IP-based allowlists after the Relaunch completes. The new IPs appear in the Workers section once the fleet is online.

Concurrency and Queue Settings​

Configure concurrency and queue limits in Settings in your account dashboard. When a worker reaches its concurrency limit, new requests enter the queue. If the queue is full, the worker returns 429. For tuning guidance, see Worker Settings.

Multiple Worker Load Balancing​

With multiple workers, Browserless load-balances across them using least-connections routing. To manage load-balancing yourself, find each worker's individual endpoint directly beneath its title in the Workers section of your cluster page. Click the IP address to copy it to your clipboard.