Regions - SpatialReal

Globally distributed service

Our avatar service runs in multiple regions. You can choose the region that’s closest to your infrastructure to minimize latency.

Use these region names when selecting a deployment:

When a doc example uses <console-api-host>, substitute the host for your region:

Region	`<console-api-host>`
`ap-northeast`	`console.ap-northeast.spatialwalk.cloud`
`us-west`	`console.us-west.spatialwalk.cloud`

When a doc example uses console endpoint url or ingress endpoint url, substitute the URL for your region:

Region	Console Endpoint URL	Ingress Endpoint URL (v2)
`ap-northeast`	`https://console.ap-northeast.spatialwalk.cloud/v1/console`	`wss://api.ap-northeast.spatialwalk.cloud/v2/driveningress`
`us-west`	`https://console.us-west.spatialwalk.cloud/v1/console`	`wss://api.us-west.spatialwalk.cloud/v2/driveningress`

The following identifiers/credentials are not region-specific and can be used across regions:

This means you can switch regions or run multi-region without recreating apps, rotating keys, or re-generating avatars.

Services in different regions run on separate infrastructure, so you can improve availability by implementing fallback:

Primary + backup: if requests to the primary region fail, retry against another region.
Data sync: since the identifiers/credentials mentioned above are portable, you can keep using them when failing over to another region.