Skip to content
inetGeek

DigitalOcean Load Balancers

iScore40–54 · #4/4
www.digitalocean.com/products/load-balancer · Load balancing
SEPT 2026 audit

Managed load balancers billed per node per month, where a node is a fixed block of throughput rather than a usage meter.

Visit DigitalOcean Load Balancers documentation
Compare DigitalOcean Load Balancers with

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

Entry paid plan$12 a month for a regional load balancer with one node. The only member of this category priced monthly rather than hourly, and the only one where the entry price is a round number rather than a fraction of a cent.
Regions16 datacentres carry Load Balancers: NYC1, NYC2, NYC3, AMS3, SFO2, SFO3, SGP1, LON1, FRA1, TOR1, BLR1, SYD1, ATL1, RIC1, MKC1 and MEM1. Availability is published per product per datacentre rather than assumed from the region list.
CategoryLoad balancing

Updated 5 criteria comparedSources last checked

01.Evaluation guide

Who it suits

Knowing the bill in advance. $12 a month buys one node and a node is a fixed 10,000 requests per second — capacity that steps rather than meters, which is the only genuinely forecastable pricing in this category.

Consider something else if…

Your traffic is spiky or small. A node is bought whole, so half a node of traffic costs a whole node, and the ceiling is 100 nodes rather than an elastic limit.

Editorial · Palash Bagchi · approved

Each value below links to the page it was read from, with the sentence it came from. Criteria DigitalOcean Load Balancers does not publish are not listed.

Pricing
2 criteria
Entry paid plan$12 a month for a regional load balancer with one node. The only member of this category priced monthly rather than hourly, and the only one where the entry price is a round number rather than a fraction of a cent.
Sources (1) →
Pricing modelPer node, added and removed as you go, up to 100 of them. Each node is a fixed quantum of capacity rather than a meter, so the bill steps rather than tracking traffic — which makes it forecastable in a way per-hour and per-GB pricing is not, and wasteful if a node sits half-used.
Sources (1) →
  • Load Balancers Pricing ↗

    “Start with one node and add up to 100 of them, adding or removing nodes as you go.”

    Read 2026-09-15 · official pricing

Infrastructure
1 criteria
Regions16 datacentres carry Load Balancers: NYC1, NYC2, NYC3, AMS3, SFO2, SFO3, SGP1, LON1, FRA1, TOR1, BLR1, SYD1, ATL1, RIC1, MKC1 and MEM1. Availability is published per product per datacentre rather than assumed from the region list.
Sources (1) →
Inference
1 criteria
Rate limits10,000 requests per second per node, alongside 10,000 simultaneous connections and 250 SSL connections per second. Capacity is bought in these blocks, so the way to more throughput is another node rather than a larger bill for the same one.
Sources (1) →
  • Load Balancers Pricing ↗

    “+10,000 requests per second +10,000 simultaneous connections +250 SSL connections per second”

    Read 2026-09-15 · official pricing

Caching
1 criteria
Multi-region replicationThree types are offered — Regional, Global and Network — with the $12 entry price attached to the Regional one. The page names the three but prices only Regional here.
Sources (1) →
  • Load Balancers Pricing ↗

    “Type Regional Global Network Regional pricing starts at $12 per month”

    Read 2026-09-15 · official pricing

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

Compare DigitalOcean Load Balancers withAll alternatives, ranked →
DigitalOcean Load Balancers vs AWS Elastic Load Balancing
DigitalOcean Load Balancers vs Google Cloud Load Balancing
DigitalOcean Load Balancers vs Cloudflare Load Balancing

Every page here is sourced and dated.