The Globe edge network is located in some 300 cities in 100+ countries and is powered by Cloudflare’s network - which is milliseconds away from virtually every Internet user on the globe.

Our edge network is responsible for features such as DDoS mitigation, zero latency routing to our compute regions, instant rollbacks, A/B testing deployments and more.

Compute Regions

Globe runs your deployments in 37 (currently) compute regions.

Compute Regions
MAD (Madrid)SpainEurope
BRU (Belgium)BelgiumEurope
AMS (Netherlands)NetherlandsEurope
MXP (Milan)ItalyEurope
CDG (Paris)FranceEurope
TPE (Taiwan)TaiwanAsia
NRT (Tokyo)JapanAsia
KIX (Osaka)JapanAsia
HEL (Finland)FinlandEurope
TLV (Tel Aviv)IsraelAsia
DSM (Iowa)United StatesNorth America
CHS (South Carolina)United StatesNorth America
IAD (Northern Virginia)United StatesNorth America
CMH (Columbus)United StatesNorth America
DFW (Dallas)United StatesNorth America
PDX (Oregon)United StatesNorth America
HKG (Hong Kong)Hong KongAsia
ICN (Seoul)South KoreaAsia
SIN (Singapore)SingaporeAsia
CGK (Jakarta)IndonesiaAsia
BOM (Mumbai)IndiaAsia
DEL (Delhi)IndiaAsia
SYD (Sydney)AustraliaOceania
MEL (Melbourne)AustraliaOceania
WAW (Warsaw)PolandEurope
TRN (Turin)ItalyEurope
LHR (London)United KingdomEurope
FRA (Frankfurt)GermanyEurope
ZRH (Zurich)SwitzerlandEurope
DOH (Doha)QatarAsia
YUL (Montreal)CanadaNorth America
YYZ (Toronto)CanadaNorth America
GRU (Sao Paulo)BrazilSouth America
SCL (Santiago)ChileSouth America
LAX (Los Angeles)United StatesNorth America
SLC (Salt Lake City)United StatesNorth America
LAS (Las Vegas)United StatesNorth America

Globe compute regions will continue expanding into the following regions: Berlin (Germany), Dammam (Kingdom of Saudi Arabia), Querétaro (Mexico), Malaysia, Thailand, New Zealand, Greece, Norway, South Africa, Austria and Sweden.

Preferred Regions

In some cases, executing a request in a region closest to the user may not be desirable. Consider a user who hits your application from Europe but your application uses a region specific database located in the United States.

Multiple outbound requests from Europe to the US data center could result in potentially long response times for the user whilst data is sent across the network. In this scenario, it may make more sense to handle the request in the US data center, and then return the response to the user from there.

This can be achieved by specifying preferred region(s). When preferred regions are specified Globe will:

  • if a single preferred region is provided: execute the request in the preferred region
    • if the specified region is unhealthy or experiencing an outage, then default global routing behavior is used and the nearest healthy region executes the request.
  • if multiple regions are provided, Globe will choose the closest preferred region to the user and execute the request there
    • if any of specified regions are unhealthy or experiencing an outage, they will no longer be preferred.
    • if all of the specified regions are unhealthy or experiencing an outage, then default global routing behavior is used and the nearest healthy region executes the request.

Configure via Project Settings

Within the Globe dashboard, under Project -> Settings -> Preferred Region, you can select a preferred region for your project.

When selecting preferred regions from the dashboard, this will only apply to new deployments.

Configure via X-Globe-Preferred-Region header

Specify IATA codes from the region list in the X-Globe-Preferred-Region header of a request.

For example: X-Globe-Preferred-Region: DFW, PDX

Note that when specifying a preferred region via the header this will override any preferred region(s) set in the Project Settings dashboard.