Locations

Datum is available in 17+ global locations, organized into points of presence (PoPs), packaged into Regions and Availability Zones (AZs)

Datum’s infrastructure footprint is organized into points of presence (PoPs) that are packaged into Regions and Availability Zones (AZs). See our Locations for a visual overview of all PoPs.

Each Region represents a specific geographic and network boundary, while each AZ provides independent capacity within that Region. This structure supports predictable latency, fault isolation, and regulatory alignment.

Similar to the large public clouds, Datum uses a country-anchored naming format with the following elements:

Field	Description
Geography	Two-letter ISO country code (example: US, DE, IN)
Cardinal Direction	Directional indicator within the country: north, south, east, west, or central.
Number	Region index within that location.
Count	Availability Zone identifier: a, b, c, etc.

For example, here is how we describe the first region and availability zone in the eastern US.

<Geography>-<Location>-<Number><Count>

Example: us-east-1a

Regions and AZs are defined by distance and policy boundaries.

• When Points of Presence in the same country are separated by more than about 5 milliseconds round-trip time (RTT), a new Region is created.
• If multiple PoPs exist in the same metro but operate independently (for example, separate network clusters or facilities), they are modeled as separate AZs. Increment the Count value to the next letter.
• If PoPs are within about 5 milliseconds RTT and part of the same operational domain, they remain in the same Region. Example: us-east-1a, us-east-1b, us-east-1c.

Note: regulatory and export control requirements may restrict or define where data and workloads can reside. These boundaries take precedence over latency-based placement rules.

Regions

Region Code	Metropolitan Area
ae-north-1	Dubai
au-east-1	Sydney
br-east-1	São Paolo
ca-east-1	Toronto
cl-central-1	Chile
de-central-1	Frankfurt
gb-south-1	London
in-west-1	Mumbai
jp-east-1	Tokyo
nl-west-1	Amsterdam
sg-central-1	Singapore
us-central-1	Dallas
us-east-1	Ashburn
us-east-2	New York City
us-west-1	San Jose, California
za-central-1	Johannesburg

Region Tracing

Visit https://edge.datum.net/ to learn which Datum Region and availability zone you’re reaching via anycast. If you’re using Datum Tunnels, this will be your entrypoint into our network.

You can also access our zones and locations programmatically:

• JSON structured response https://edge.datum.net/api/edge-info
• Plaintext https://edge.datum.net/api/trace