Virtual Machines
Virtual machines sized for your workload, billed per second.
Learn moreDistribute traffic across your virtual machines and keep it away from unhealthy ones. The guided setup ends with a review of exactly what will be sent before the load balancer is created.
ICT Cloud console · illustrative data
Details, listener, pool, members, health monitor, and review.
Health monitors keep traffic away from members that stop responding.
The review shows the precise request that will be sent.
Pick a balancing algorithm and tune how members are checked: delay, timeout, retries, and, for HTTP, the URL path and expected codes.
Protocol and port for incoming traffic.
Round robin, least connections, or source IP.
Your virtual machines as backend targets, now or later.
Type, delay, timeout, max retries; URL path and expected codes for HTTP.
A VIP in the subnet you choose, assigned automatically or fixed.
Listeners, pools, members, and monitors with their status.
Name, subnet, and VIP.
Protocol and port.
Balancing algorithm.
Backend targets.
Probe configuration.
Check and create.
| Setup | Guided, six steps |
|---|---|
| Network | VIP in your subnet, automatic or fixed |
| Listener | Protocol and port |
| Algorithms | Round robin, least connections, source IP |
| Members | Virtual machines |
| Health monitor | Type, delay, timeout, max retries |
| HTTP probes | URL path and expected codes |
| Region | Istanbul 1 |
Spread traffic over several web servers so no single instance is critical.
Add members as load grows.
Take a member out of the pool while the others keep serving.
Round robin, least connections, and source IP.
Members are not actively checked. Add a monitor so traffic avoids members that stop responding.
Yes, from the load balancer’s detail page.

Creating an account is free. Resources are billed per second, with a 60-second minimum.
Your privacy. We use strictly necessary cookies to run this site. With your consent we would also use analytics cookies to improve it. This prototype sets none.