> ## Documentation Index
> Fetch the complete documentation index at: https://jupiter-docs-beam-tx-jup-ag-submit.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Latency and Server Locations

> API gateway regions and colocation guidance for lowest latency

Jupiter's API gateway is distributed across six AWS regions worldwide. Latency to the API depends primarily on the physical distance between your servers and the nearest gateway region. Colocating your servers in or near one of these regions gives you the lowest possible round-trip time.

## Gateway regions

| Region    | AWS Region ID    | Location       |
| --------- | ---------------- | -------------- |
| Singapore | `ap-southeast-1` | Southeast Asia |
| Frankfurt | `eu-central-1`   | Europe         |
| Virginia  | `us-east-1`      | US East        |
| São Paulo | `sa-east-1`      | South America  |
| Tokyo     | `ap-northeast-1` | East Asia      |
| Oregon    | `us-west-2`      | US West        |

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

## Colocation guidance

For the lowest API latency, deploy your servers in the same AWS region (or the same availability zone) as one of the gateway regions listed above. If your infrastructure runs on a different cloud provider, choose a data centre in the same city or metro area.

If your users are globally distributed:

* **Asia-Pacific:** Singapore (`ap-southeast-1`) or Tokyo (`ap-northeast-1`)
* **Europe:** Frankfurt (`eu-central-1`)
* **Americas:** Virginia (`us-east-1`), Oregon (`us-west-2`), or São Paulo (`sa-east-1`)