Where Ask RIKAI processes requests, and which region serves each tenant.
Regions
Every tenant is assigned to exactly one region. Assistant requests, embeddings, and conversation history stay inside that region.
| Region | Location | Assistant availability | Failover region |
|---|---|---|---|
| EU Central | Frankfurt, Germany | General availability | EU West |
| EU West | Dublin, Ireland | General availability | EU Central |
| US East | Ashburn, United States | General availability | US West |
| US West | Hillsboro, United States | General availability | US East |
| APAC South | Singapore | General availability | APAC East |
| APAC East | Tokyo, Japan | Controlled availability | APAC South |
Determining your region
Open Administration → Tenant → Overview. The region code appears next to the tenant identifier, for example eu-central. The same value is returned by the platform status endpoint.
Failover
If the primary region is unavailable, read traffic fails over automatically to the paired region listed above. Write traffic is queued and replayed when the primary returns. Failover stays inside the same legal jurisdiction.
Choosing a region
Pick the region closest to the majority of your users, subject to your data residency obligations. Round-trip latency above 150 ms is noticeable in streamed answers.
Controlled availability means the region is production ready but new tenants are onboarded on request rather than self-service.
Last updated: 2026-09-01