Bunny CDN

CDN Load Balancer

CDN Load Balancer

Group origins by priority and route requests by geography, latency, or load. When something fails, the Load Balancer follows the same routing logic to find the next eligible origin.

No credit card required. Complete setup in 2 minutes. Cancel anytime.

Trusted by developers around the world

bunny.net powers 1.5 million websites with fast, reliable global infrastructure.

Multi-origin setups get complicated

Multi-origin setups get complicated

More regions and backup capacity can make your app more resilient. They also add routing rules, failover paths, and infrastructure costs to manage.

Routing rules pile up as you add origins

Primary regions, standby capacity, and origins with different roles need different routing behavior. As the pool grows, keeping it all straight gets harder.

Advanced steering can mean add-ons

Routing by geography, latency, or connection load gives you more control. Some platforms put these options behind higher tiers or paid add-ons.

Redundancy can get expensive

Adding another origin can improve resilience, but per-origin fees increase costs even when backup origins serve little traffic.

One routing policy for all your origins

One routing policy for all your origins

Group origins by region, provider, capacity, or purpose, set priorities for each group, and choose how traffic is distributed. Bunny CDN applies that policy whenever it routes a request to an origin.

Control how traffic reaches your origins

Control how traffic reaches your origins

Choose how requests are distributed between origin groups and within each group, with a separate routing strategy for each layer.

Between origin groups

Spread traffic evenly, assign weights, or steer requests by geography or latency. Use priority tiers to decide which groups should receive traffic first.

Within each group

Use round robin, weights, least connections, or latency to choose an origin. Set the strategy per group to match how each pool should behave.

Prioritize primary capacity during failover

Prioritize primary capacity during failover

For each request routed to an origin, Bunny CDN orders eligible origins based on the priorities and routing rules you’ve already set. If a connection attempt fails, it moves to the next eligible origin before falling back to standby capacity.

Respond to health and performance at the edge

Respond to health and performance at the edge

Use network-wide health checks alongside local failure detection, and choose latency- or load-aware routing when you need it.

Check health across the network

Run HTTP(S) health checks from multiple regions. Unhealthy origins drop out of normal rotation globally and return automatically once they recover.

Route around local failures

If one edge can’t reach an origin, the Load Balancer can route traffic from that edge elsewhere while keeping the origin available to other edges.

Balance latency and load

Latency-based routing also considers requests already in flight, helping avoid overloading the fastest origin and spreadingwhile distributing traffic across available capacity.

Build around the origins you use

Build around the origins you use

Mix origin types, reuse one Load Balancer across Pull Zones, take origins out of rotation for maintenance, and keep sessions sticky without complicating your routing.

Reuse it across Pull Zones

Attach one Load Balancer to multiple Pull Zones and manage a single routing policy instead of recreating the same setup for each zone.

Mix different origin types

Combine standard HTTP(S) origins, Bunny Storage, Edge Scripting, and Magic Containers in the same pool, even when primary and standby origins differ.

Take origins out of rotation

Disable individual origins or whole groups during maintenance, then bring them back when ready without changing the rest of your routing setup.

Keep sessions sticky

Pin repeat requests to the same origin with cookie-based affinity. If that origin becomes unhealthy, Bunny CDN automatically assigns another one.

More origins shouldn’t mean a higher fixed costs

More origins shouldn’t mean a biggerhigher fixed costsbill

Pay per Load Balancer, with 50 million origin-bound requests included each month and simple usage pricing beyond that.

One price for the routing setup

Reuse the same Load Balancer across multiple Pull Zones with one monthly fee and shared request allowance. Requests served from the CDN cache don’t count toward usage.

  • Load Balancer
    $9.50/month
  • Origin-bound requests included
    50 million requests/month
  • Additional origin-bound requests
    $0.65/million requests