Skip to main content
GPU infrastructure across four regions on three continents. Telnyx will endeavor to process requests in the region nearest the ingress domain you call, but this is not guaranteed.

​
Current Regions

RegionLocation
US EastAtlanta
US WestDenver
EUParis
Asia-PacificSydney

​
Routing

Inference processing is latency-based, influenced by the ingress domain you call, not by your account’s data locality setting. Telnyx will endeavor to process in the preferred region, but does not guarantee it:
Ingress domainPreferred region
api.telnyx.comUS
api.telnyx.euEU
api.telnyx.com.auAPAC
Calling a regional ingress domain (for example, api.telnyx.eu) directs requests to the nearest GPU region for that domain under normal conditions. Telnyx does not guarantee processing location: during failover or capacity events, requests are processed at the next-lowest-latency region rather than failing. A region-selection API parameter is on the roadmap.

​
Data Residency

Processing location and storage location are controlled separately:
  • Processing in transit is latency-based, influenced by the ingress domain you call (see Routing above). Telnyx will endeavor to process in the preferred region, but it is not a guaranteed processing location.
  • Storage at rest depends on the endpoint. The chat completions endpoint does not store request or response data. The responses endpoint stores conversations, and that storage is governed by your Data Locality setting.
For a full cross-product breakdown (including Voice AI Assistants), see the Data Residency & Compliance FAQ.

​
Roadmap

  • Region selection API parameter
  • Per-region model status and latency metrics
  • Edge inference for sub-50ms response times