> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/connectivity/load-balancer/details/service-description.md).

# Service description

***

### Regional availability

The product is present in the following locations:

* dc-fbg1 (our Falkenberg DC, Sweden)
* dc-sto1 (our Stockholm DC, Sweden)

### Technical specification

#### General information

| **Customer self-service**       | Yes, managed in the control panel |
| ------------------------------- | --------------------------------- |
| **Protocol(s)**                 | TCP / HTTP                        |
| **Processing of personal data** | Transfer                          |

#### Protocol and port

The Load Balancer establishes connections with its backend servers using the specified protocol and port, allowing it to utilize the protocol's capabilities for traffic management.

* **HTTP protocol (typically port 80 or port 443 if also using TLS):** The Load Balancer forwards HTTP connections to backend servers. Traffic will be forwarded without encryption.
* **TCP protocol:** The Load Balancer connects to backend servers using TCP and forwards TCP payloads without modification, except for encryption and decryption, as configured.

#### HTTP mode – specific features:

| **Sticky sessions**          | Yes                                                                                                                    |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **X-Forwarded-For header**   | Enabled by default                                                                                                     |
| **X-Forwarded-Proto header** | Enabled by default                                                                                                     |
| **TLS/SSL certificates**     | Yes, you can add a certificate to the frontend (no integrated feature for auto-renewing Let's Encrypt certifications). |

#### TCP mode – specific features:

| **Proxy protocol support** | No |
| -------------------------- | -- |

#### Timeout options

The Load Balancer service provides three different types of timeout settings:

1. **Timeout Client** \[set to 30 seconds by default]: The timeout client setting determines the maximum duration of client inactivity allowed when a client is connected to the server.
2. **Timeout Connect** \[set to 4 seconds by default]: The timeout connect is like a grace period that sets the maximum time for a client to connect to a server.
3. **Timeout Response** \[set to 30 seconds by default]: The timeout response, also known as the "timeout server," sets the maximum time to receive HTTP response headers from the backend server after it receives the complete client request.

#### Limits on Load Balancing resources

Each load balancer has the following configuration limits:

* Concurrent sessions: The maximum number of connections that the Load Balancer will accept are, by default, set to 1,000. Maximum value: 200,000.
* One IPv4 address and one IPv6 address.
* No geo-redundancy, private network, Server Name Identification (SNI) or proxy protocol support.

### Responsibilities

| **Infrastructure platform** | Glesys   |
| --------------------------- | -------- |
| **Client setup**            | Customer |
| **Client troubleshooting**  | Customer |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.glesys.com/products/connectivity/load-balancer/details/service-description.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.