# Load balancers

This document explains how load balancing operates on CloudBrowser. Our infrastructure currently includes a single load balancer, but we plan to expand with additional load balancers in the United States and a well-connected location in Asia (such as Singapore) in the future.

#### CloudBrowser Workers <a href="#id-0-toc-title" id="id-0-toc-title"></a>

When you send a request to our endpoint, whether it’s `https://production.cloudbrowser.ai` it passes through our load balancer and is directed to one of our instances for processing `wss://browser.cloudbrowser.ai/*`. We provide a list of IP addresses from our shared fleet for whitelisting purposes.

Our cloud-unit fleet consists of numerous machines running CloudBrowser. The load balancer automatically selects the appropriate machine to handle each request. If a particular machine is overwhelmed and unable to handle the incoming connection, our load balancer will divert the request to a different machine. Simply put, we utilize a customized least-connected algorithm to make sure your request is managed effectively.

#### Load Balancer Workers <a href="#id-1-toc-title" id="id-1-toc-title"></a>

We use load balancing to distribute traffic to all our workers located in Amsterdam. This mechanism ensures that the workload is evenly shared across multiple servers, preventing any single machine from becoming a bottleneck. By dynamically routing requests based on current server load and capacity, we enhance performance, reduce latency, and improve the overall reliability of our services. Additionally, our system continuously monitors server health and adjusts traffic distribution to maintain optimal efficiency and uptime for all connected clients.

#### Future Expansion Plans <a href="#id-2-toc-title" id="id-2-toc-title"></a>

Currently, our infrastructure includes a single load balancer. However, we plan to enhance our system with additional load balancers located in United States and a well-connected hub in Asia, such as Singapore, to further reduce latency and improve performance globally.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cloudbrowser.gitbook.io/docs/cloud-service/load-balancers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.