Skip to main content
Routing Filters allow you to control which CDN locations serve your content. When enabled, traffic is routed only to Points of Presence (PoPs) within the selected regions. This is primarily useful for GDPR compliance and data residency requirements where you need to ensure user data stays within specific geographic boundaries.

How it works

When you enable a routing filter (such as European Union or the European Economic Area), all requests to your Pull Zone are routed exclusively to PoPs within that region. Users outside the filtered region are also routed to those same locations.
Combining multiple routing filters creates a cross-section. Traffic is only routed to PoPs contained in all selected filters.

Available filters

European Union (EU)

Routes all traffic exclusively through 24 PoPs within EU member states:
Austria, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, and Sweden.

European Economic Area (EEA)

The EEA extends the EU single market to three non-EU countries (Iceland, Liechtenstein, and Norway), all of which have adopted the GDPR. Choose this filter when you need the same data-residency guarantees as the EU filter but also want to serve users in these additional countries. Routes all traffic exclusively through 26 PoPs, covering every EU PoP plus Iceland and Norway:
Austria, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, and Sweden.
Liechtenstein is part of the EEA but currently has no bunny.net PoP. Because the EEA contains every EU country, the EEA filter is a superset of the EU filter, so selecting both is equivalent to selecting EU alone. Switzerland and the United Kingdom are not part of the EEA and are excluded by this filter.

Enabling Routing Filters

  1. Go to your Pull Zone in the dashboard
  2. Navigate to Pricing & Routing
  3. Enable the desired routing filter
The filter applies to both Standard and High Volume tier zones automatically.

Performance considerations

Routing Filters significantly limit global coverage. Users outside the filtered region will experience increased latency since their requests are routed to the nearest PoP within the filter, not the nearest global PoP.
For example, with the EU or EEA filter enabled:
  • EU / EEA users: Excellent performance with local PoPs (24 for EU, 26 for EEA)
  • Everyone else: Routed into the filtered region, negating most CDN performance benefits
Only enable Routing Filters if you have specific compliance requirements that outweigh the global performance trade-off.

Limitations

Routing Filters only apply to CDN Pull Zone traffic. DNS traffic continues to use the global DNS network, but DNS requests generally don’t contain personally identifiable information.
Last modified on August 14, 2026