# Regions

> How the caller's region is worked out and how it affects which provider is fastest. Regions rank offers by distance; they don't restrict where data goes.

Source: https://digitspace.ai/docs/routing/regions · Last checked: 2026-10-31

The gateway estimates how far each provider's servers are from your callers, and adds that network time to its speed estimate. With the **Balanced** and **Fastest response** strategies, a nearby provider therefore ranks higher.

> **Warning:** Regions only change the ranking. They don't keep requests in a region: a request can still go to a provider elsewhere, for example when the nearby one fails. Don't rely on them for data residency.

## How the caller's region is chosen

The first of these that's set wins:

1. The project's **Caller region**, under **Routing → Custom settings** (Enterprise).
2. The `X-DigitSpace-Region` request header.
3. The country your request comes from.
4. The gateway's own region.

## Values

`X-DigitSpace-Region` takes one of these values, in any case:

| Value | Region |
| --- | --- |
| `us-east` | US East |
| `us-west` | US West |
| `eu-west` | Europe West |
| `eu-central` | Europe Central |
| `eu-north` | Europe North |
| `singapore` | Singapore |
| `tokyo` | Tokyo |
| `seoul` | Seoul |
| `sydney` | Sydney |
| `beijing` | Beijing |

It also understands common names for them: `us`, `eu`, `apac`, `asia`, `jp`, `au` and `cn`, and cloud region names such as `us-east-1`, `eu-central-1`, `ap-southeast-1` and `ap-northeast-1`. An unknown value is ignored.

```bash
curl https://api.digitspace.ai/v1/chat/completions \
  -H "Authorization: Bearer $DIGITSPACE_API_KEY" \
  -H "X-DigitSpace-Region: singapore" \
  -H "Content-Type: application/json" \
  -d '{ "model": "auto", "messages": [{ "role": "user", "content": "Hi" }] }'
```

Offers whose provider has no region, or serves globally, are treated as far from everyone.