Skip to main content

Load Balancing

Dedicated Workers' Load Balancing​

Your worker can be located in 4 different sites: San Francisco, New York, Amsterdam, or London. If you request to https://chrome.browserless.io, it will redirect to one of the 4 regions.

In order to improve the latency by having a worker located closer to your client, you'll want to use the load balancer closest to your machine to reduce the distance data from requests must travel. These are the load balancers available for you to point your traffic to:

  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 listed in the Production Workers section of your account dashboard under the "Public IP" column. Use these IPs if you need to whitelist traffic from your dedicated workers. For shared fleet IPs, see Whitelisting IP Addresses.

Concurrency and Queue Settings​

Dedicated workers have configurable concurrency and queue limits. You can adjust the maximum number of concurrent browser sessions and the queue length from the worker settings in your account dashboard. When a worker reaches its concurrency limit, new requests are queued. If the queue is also full, the worker returns a 429 error. For tuning guidance, see Worker Settings.

Multiple Worker Load Balancing​

When you have multiple instances, it'll automatically load-balance amongst them by least connections. If you want to handle load-balancing on your end, you can get the endpoint for every individual worker by clicking on the URL in the "Address" Column in the Production Workers table available in your account dashboard.