Available regions
| Code | Location | Recommended use case |
|---|---|---|
FRA | Frankfurt, Germany | European users (GDPR-compliant) |
LON | London, United Kingdom | UK and Western Europe |
SGP | Singapore | Southeast Asia, Oceania, and APAC |
JPN | Japan | Japan and Northeast Asia |
SFO | San Francisco, United States | US West Coast and Pacific |
NYC | New York, United States | US East Coast, Latin America, and global default |
Choosing a region
Minimize latency for your users. A search that takes 5 ms to execute on the server can feel instant or sluggish depending on whether the user is 10 ms or 200 ms away. Choose the region closest to the majority of your users. Consider data residency requirements. If your application handles personal data subject to GDPR or other regional regulations, ensure your project is hosted in a compliant region.FRA and LON are located within the EU and UK.
Plan for multiple regions if you have a global audience. You can create separate projects per region and route search traffic to the nearest instance from your application layer. Each project is billed independently.