> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Regions & Availability

> GPU regions and routing behavior for the Telnyx Inference API, spanning four regions across three continents with automatic nearest-region routing.

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

| Region       | Location |
| ------------ | -------- |
| US East      | Atlanta  |
| US West      | Denver   |
| EU           | Paris    |
| Asia-Pacific | Sydney   |

## 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 domain      | Preferred region |
| ------------------- | ---------------- |
| `api.telnyx.com`    | US               |
| `api.telnyx.eu`     | EU               |
| `api.telnyx.com.au` | APAC             |

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](#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](/docs/account-setup/data-locality) setting.

For a full cross-product breakdown (including Voice AI Assistants), see the [Data Residency & Compliance FAQ](/docs/inference/data-residency).

## Roadmap

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