Skip to main content
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: For example, here is how we describe the first region and availability zone in the eastern US.
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), Datum creates a new Region.
  • If multiple PoPs exist in the same metro but operate independently (for example, separate network clusters or facilities), they become 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 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:
Last modified on July 6, 2026