Quickstart
Learn how to create and configure a Load Balancer.
View QuickstartLoad Balancers distribute workloads across servers, ensuring scalable and continuously available applications, even during heavy traffic.
Load Balancer QuickstartLearn how to create and configure a Load Balancer.
View QuickstartCore concepts that give you a better understanding of Load Balancers.
View ConceptsCheck our guides to creating and configuring Load Balancers.
View How-tosGo beyond the basics with detailed, in-depth guides to configuring your Load Balancer.
Read moreManage Load Balancers using the Scaleway API.
Go to Load Balancer APIFollowing the deprecation of static Private Network attachment, the Load Balancer API will no longer accept static Private Network attachement with an IP address outside of the Private Network subnet.
Please update to DHCP attachment type (recommended) or use an IP address which belongs to the Private Network subnet.
If you already use DHCP attachment mode or static attachement mode with an IP address belonging to the Private Network subnet, you're not affected by this change.
You can now add a public IPv6 address to both new and existing Load Balancers. This feature is available for all regions, and IPv6 addresses can be attached in addition to existing IPv4 addresses. Find out more in our documentation.
Load Balancer now generates logs when the state of backend servers changes, or when your frontend TLS certificates expire. These logs are sent to your Scaleway Cockpit and you can browse them via the dedicated LB Logs Overview dashboard. They provide information not only on the changes in state of backend servers, but also the reasons for these changes. With these logs, you will be equipped to properly troubleshoot backend server issues.
Read more about Load Balancer logs in our documentation.
Visit our Help Center and find the answers to your most frequent questions.
Visit Help Center