Summary

  • bunny.net combines its EU and EEA routing filters by intersection. Selecting both has the same effect as selecting EU alone, excluding the Norwegian and Icelandic locations added by EEA.
  • Visitors outside the selected area still reach permitted nodes inside it. Switching off a pricing region also redirects its visitors to the nearest enabled region rather than denying access.
  • Country blocking in Traffic Manager acts at DNS, returning 127.0.0.1. The blocked request never reaches the CDN, creates no charge for that request and leaves no Pull Zone HTTP log entry.

A European procurement checklist can lose Norway with one extra tick. In bunny.net, adding EU to an EEA routing filter removes the Norwegian and Icelandic serving locations that the broader choice allowed. The form looks more thoroughly completed. The available network has shrunk.

The documentation makes the calculation explicit. Multiple routing filters intersect: a point of presence must belong to every selected area. Since EEA contains EU, selecting both leaves EU. Another tick adds a condition, not another collection of places.

That small operation exposes a larger buying problem. Geography can describe where a visitor lives, where a server answers or which price region carries the traffic. A business can reasonably want different answers to all three. Calling the whole arrangement “European delivery” saves space in a slide deck and leaves the network to resolve the ambiguity.

Norway’s reader stays; Norway’s node goes

A Pull Zone connects a customer’s original content to bunny.net’s CDN. Routing Filters restrict the locations from which that content can be served. Requests from outside the selected area are also directed to permitted points of presence inside it.

A Norwegian reader therefore retains access under the EU filter. The Norwegian serving location loses eligibility. Access and proximity can move independently: a service remains open to the world while becoming more distant from part of it. Treating those outcomes as one geographical restriction gives a performance setting powers it does not exercise.

The published EEA description includes Iceland and Norway in addition to EU locations. Liechtenstein belongs to EEA but currently has no bunny.net point of presence in the documentation. Switzerland and the United Kingdom fall outside that EEA filter. Institutional membership, familiar ideas of Europe and an actual deployed location are three separate lists.

bunny.net warns that users outside the filtered area will face increased latency. “Nearest” now means nearest among the places still eligible to answer. A convenient dot on the provider’s global map may have been removed from this customer’s service by the configuration itself.

The restriction can be useful precisely because it executes a location requirement. The buyer also needs to own the journey it imposes on distant users. Otherwise one department approves the geography and another inherits the explanation for slower service.

Cheap Europe uses a different map

Pricing regions affect the route too. The quickstart says disabling a region leaves its visitors able to access content: their requests automatically move to the nearest enabled region. The customer has reduced the places that serve demand, not the places allowed to create it.

Traffic Manager also offers redirected countries. Its documentation sends requests from those countries to the cheapest pricing region, North America/Europe. That is an economic routing choice. Europe in that commercial grouping is not the institutional boundary of an EU-only routing filter.

A screenshot can consequently be genuine and still support a false conclusion. It may show a preference for a cheaper delivery region while a procurement note presents it as proof of EU-only serving. The error is in the proposition attached to the image. One control cannot certify a different control just because both contain a familiar place name.

Standard and Volume introduce another choice. Standard combines wider network coverage with regional rates; Volume uses a smaller network and global volume bands. The configuration pattern is similar, but the available possibilities differ. Regional filters apply to both types. Selecting an area does not award every plan all the points drawn inside it on the marketing map.

A business distributing large files may sensibly accept a different trade-off from an application built around quick, repeated interactions. The decision belongs to the workload and its audience. Reward only the lower bill and the audience’s waiting time becomes a cost with no line in the winning spreadsheet.

A blocked request can vanish before the log

Country blocking is a separate Traffic Manager operation. It acts at DNS: blocked requests resolve to 127.0.0.1, so the connection never reaches the CDN and the user encounters a connection error. Because the attempt ends before HTTP, bunny.net says it creates neither a Pull Zone log entry nor a charge for that request.

That changes what a quiet dashboard can mean. Fewer HTTP requests from a country might reflect lower demand. They might also reflect more attempts stopped before the measurement point. Counting customers inside a shop will not tell management how many people found the approach road closed.

The geographical input is specific as well. bunny.net uses the end-user EDNS client subnet supplied by the resolver; without it, the resolver’s own IP address is used. The decision classifies a network-visible location, rather than checking a person’s verified nationality. A VPN or proxy can change the location presented. Stricter requirements need additional controls, including the token-authentication restrictions described by the provider.

The observation point therefore matters as much as the setting. A serving-location filter is checked through the places that answer and the experience delivered. A DNS block also requires the client’s resolution and connection results. One HTTP graph cannot represent both mechanisms equally well.

The filter does not move the whole chain

Routing Filters cover CDN Pull Zone traffic. DNS continues to use the global DNS network. The quickstart separately asks the customer to choose an Origin URL or a Storage Zone from which original content will be fetched.

A buyer can make good use of this separation. Match each geographical undertaking to the action and control that implement it. CDN serving locations have one configuration; the origin has another; DNS has its own service description. Storage, logs and every intermediate transport hop do not acquire a location automatically from a screenshot of the routing filter.

The RIPE NCC’s primary member record lists BUNNYWAY, informacijske storitve d.o.o. in Slovenia. That provides an organisational identity anchor. The locations available to a particular customer come from the service and its settings, not from the member’s registered address.

Quantifying a customer’s gain or loss requires regional before-and-after measurements under comparable load, tied to business outcomes; those measurements are missing here. The published rules already specify where to look: the surviving set of serving places, the journey imposed on remote readers and attempts rejected before HTTP.

The value of geographical choice is that it makes a requirement executable. Its quality is measured by whether the remaining network matches the buyer’s intention. Tick count is a poor substitute. A company should be able to name the places it has excluded and the person who accepted the resulting journey for its audience.

Primary sources