> For the complete documentation index, see [llms.txt](https://titan-exchange.gitbook.io/titan/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://titan-exchange.gitbook.io/titan/developer-doc/developers-portal/latency.md).

# Latency and Server Locations

API regions and colocation guidance for lowest latency.

The Titan API is served from three regions. Latency depends primarily on the physical distance between your servers and the nearest region. Colocating your infrastructure in or near one of these regions gives the lowest round-trip time.

Requests to `portal.api.titan.exchange` are routed to the nearest region automatically. There is no regional hostname to select.

## Regions

| Region    | AWS Region ID    | Location  |
| --------- | ---------------- | --------- |
| Virginia  | `us-east-1`      | US East   |
| Frankfurt | `eu-central-1`   | Europe    |
| Tokyo     | `ap-northeast-1` | East Asia |

All regions serve the same API surface with the same data freshness. There is no difference in functionality or routing quality between regions.

## Colocation guidance

For the lowest API latency, deploy in the same AWS region as one of the regions above. On another cloud provider, choose a data center in the same city or metropolitan area. Colocation is available on request for [Enterprise](/titan/developer-doc/developers-portal/plans-rate-limits-credits.md#enterprise) customers.

For globally distributed users:

| Your users   | Deploy near |
| ------------ | ----------- |
| Asia-Pacific | Tokyo       |
| Europe       | Frankfurt   |
| Americas     | Virginia    |

## Rate limits across regions

The plan rate limit is a single rolling 60-second window shared across every key in the organization and across all three regions. Distributing traffic geographically does not raise the ceiling. See [Plans, Rate Limits & Credits](/titan/developer-doc/developers-portal/plans-rate-limits-credits.md#rate-limit).