bunny.net limits
The bunny.net limits orbitpush works within, for edge rules, regions and hostnames, and what can change after init.
orbitpush deploys to your own bunny.net account, so bunny.net’s limits are yours. This page lists the ones a site runs into.
Edge rule changes take a few seconds
bunny.net applies edge rule changes one by one, a few seconds after deploy finishes (2–6 s in our tests). Until then, a changed redirect or header may still behave as before.
The 50-rule limit
bunny.net allows 50 edge rules per pull zone by default, and bunny.net support can raise the limit. orbitpush uses:
- one rule per redirect, or one per 5 countries for a redirect with a
Countrycondition, because a bunny.net rule matches at most 5 countries - one rule per headers entry
- one rule per alias
- one rule for
noindexwhiledomainis set - one rule for the trailing-slash redirect
- one rule while the site is disabled
Rules created in the dashboard count too. bunny.net accepts no change to a full zone, so a deploy can use 49 rules. When a deploy would need more, it fails before uploading anything and says how many rules it needs.
Regions
| Setting | Values | Can change later |
|---|---|---|
region |
DE, UK, SE, NY, LA, SG, SYD, BR, JH |
No, it is fixed after init |
replicationRegions |
Same as region |
Only added: bunny.net does not support removing them |
geoZones |
EU, US, ASIA, SA, AF |
Yes, at least one |
The storage regions are Falkenstein (DE), London (UK), Stockholm (SE), New York (NY), Los Angeles (LA), Singapore (SG), Sydney (SYD), São Paulo (BR) and Johannesburg (JH).
Hostnames
A pull zone can have 10 hostnames, <name>.b-cdn.net included. That leaves room for one primary domain and 8 aliases. bunny.net support can raise the limit.