Load Balancer & Waiting Room
Geo-aware load balancing, health checks, session affinity. Waiting Room queues users when origin is over capacity.
What it is
The Load Balancer routes traffic across origin pools with health-based, geo-based or weighted rules. Session affinity keeps a user on the same origin. Waiting Room turns origin overload into a polite queue (estimated wait time, queue position) instead of 5xx errors.
When to use it
- Active-active multi-region origins with automatic failover.
- Sticky sessions for stateful back-ends.
- Cap concurrent users on a launch event so origin doesn't melt.
Quickstart
asc edge lb pools create web --origins ip://1.2.3.4,ip://5.6.7.8 --health-check '/healthz'
asc edge lb create example.com --pool web --steering geo
asc edge waiting-room create example.com --max-active 5000 --queue-page ./queue.htmlclient.edge.lb.pools.create('web', origins=['1.2.3.4','5.6.7.8'], health_check='/healthz')
client.edge.lb.create(zone='example.com', pool='web', steering='geo')await client.edge.lb.pools.create({ name: 'web', origins: ['1.2.3.4'], healthCheck: '/healthz' });Limits & quotas
| Limit | Default | Burst | Notes |
|---|---|---|---|
| Origin pools per project | 100 | 1,000 | |
| Health-check frequency | 10 s default | 5 s | |
| Waiting Room sessions (free) | 1M (Business plan) | — | Extra: $0.20 / 1K |
Pricing
See pricing. Pay-as-you-go, billed monthly via Stripe.
API surface
POST /v1/edge/lb/poolsPOST /v1/edge/lbPOST /v1/edge/waiting-rooms
Required scope(s): edge:write. See Scopes.
Security
All access is authenticated and scoped. See Auth & scopes and Network controls.