Regional Services launched in June 2020, when data locality and data sovereignty were largely framed by European regulation. The pressure to localize has since widened: several countries now have data localization laws of some form, public-sector contracting rules in many countries require vendors to restrict where processing happens, and some customers want to keep processing out of particular jurisdictions altogether.

The expanded Regional Services configuration set covers a larger group of defined regions, and includes some of the most requested areas and specifications: Austria, Brazil, Cloudflare Green Energy, Exclusive of Hong Kong and Macau, Exclusive of Russia and Belarus, France, Hong Kong, Italy, NATO, the Netherlands, Russia, Saudi Arabia, South Africa, Spain, Switzerland, and Taiwan. The new regions enter early access in late May 2024, with general availability planned for June 2024.

Expanding Regional Services configuration flexibility for customers

Three shapes of a region

The additions fall into three patterns. Some restrict inspection of data to data centers inside a jurisdiction's boundaries, such as Brazil, Saudi Arabia, and Switzerland. Some do the inverse, permitting inspection everywhere except certain jurisdictions, as with the Exclusive of Hong Kong and Macau and Exclusive of Russia and Belarus offerings. The Cloudflare Green Energy region instead limits inspection to data centers committed to powering their operations with renewable energy.

Encryption as the prerequisite

Data localization compliance depends on strong encryption; without it, data would be readable wherever it is handled. Cloudflare enforces modern TLS in transit and encryption back to origin servers, and communication between edge and core data centers is always encrypted. At rest, everything Cloudflare handles is encrypted at the disk level — cached files at the edge as well as configuration state in core data centers.

How traffic is kept in region on an anycast network

All Cloudflare data centers advertise the same IP addresses over BGP, so an end user reaches whichever data center is closest from a network standpoint. That proximity shortens replies and helps absorb volumetric DDoS attacks, which are spread across the network and mitigated near their source. But anycast is unaware of regional borders, so proximity alone cannot guarantee that traffic from inside a country is serviced there; an ISP may route a request to another country.

With Regional Services enabled, each data center knows which boundary it operates in. If traffic lands in a data center that does not match the customer's selected region, Cloudflare forwards the raw TCP stream in encrypted form to a data center inside that region, which decrypts it and applies Layer 7 products — CDN, WAF, Bot Management, and Workers. Responses retrace the same path.

Worked example

An end user in Kerala, India is routed by BGP to Colombo, Sri Lanka, while the customer has selected India as the sole region. Colombo sees the traffic is bound for the India region, does not decrypt it, and forwards it to a data center in India. There it is decrypted and WAF and Workers are applied as if the request had arrived directly; the response follows the same path back.

Software defined regionalization

Cloudflare argues that localization and a global anycast network are not an either/or choice. It maintains that data localization should not serve as a proxy for privacy and that restrictions on cross-border data flows harm global commerce, while still supporting customers who must meet legal obligations and their own risk tolerance.

Fixed sovereign cloud deployments, in this view, are the wrong trade-off: they force all traffic to be regionalized whether or not it needs to be confined to a specific data center in a specific region. The alternative Cloudflare calls software defined regionalization (SDR) uses the global network as its foundation, letting customers choose granularly what traffic to regionalize and where, without new physical infrastructure or duplicate cloud deployments for the same application. Localization choices made in software are not bound by existing network geography or the location of cloud deployments, and can be adjusted as requirements change.

Open questions guide that development: localizing only the APIs that handle private customer information while serving static assets globally; letting customers choose where security processing for Zero Trust deployments occurs; and defining custom regions applied to specific hostnames and products alongside BYOIP or Static IP.

BLOG-2412 Embedded Image - Lk4ngY