Hi HN, I’m Joe, and I lead content delivery and security at bunny.net. We’ve just added a load balancer to Bunny CDN in public preview.
Previously, a Pull Zone pointed at a single origin. Customers who needed multiple origins had to handle balancing separately. Now they can configure a pool of origins and have the CDN distribute traffic and handle failover.
For example, you can have two regions sharing traffic with a third on standby. The edge builds the fallback order before contacting the first origin, so those priorities still apply if it needs to try another. Retries take request safety into account, and the failover chain has a time limit.
It’s HTTP(S) origin balancing within the CDN. Backends can also be Bunny Storage, Edge Scripts, or Magic Containers, so a static copy of your site could serve as the standby.
I’m around to answer questions about the implementation. I’d be interested in how you’re handling multiple origins today, especially across different providers.
Hi HN, I’m Joe, and I lead content delivery and security at bunny.net. We’ve just added a load balancer to Bunny CDN in public preview.
Previously, a Pull Zone pointed at a single origin. Customers who needed multiple origins had to handle balancing separately. Now they can configure a pool of origins and have the CDN distribute traffic and handle failover.
For example, you can have two regions sharing traffic with a third on standby. The edge builds the fallback order before contacting the first origin, so those priorities still apply if it needs to try another. Retries take request safety into account, and the failover chain has a time limit.
It’s HTTP(S) origin balancing within the CDN. Backends can also be Bunny Storage, Edge Scripts, or Magic Containers, so a static copy of your site could serve as the standby.
I’m around to answer questions about the implementation. I’d be interested in how you’re handling multiple origins today, especially across different providers.
ദ്ദി ˉ꒳ˉ )