Cloud regions

Reference of all available Meilisearch Cloud regions with location and latency guidance.

Meilisearch Cloud is available in nine regions. Choosing the right region is one of the most impactful decisions for search latency: network round-trip time between your users and the Meilisearch instance is typically the largest contributor to perceived search speed.

Available regions

Code	Location	Recommended use case
FRA	Frankfurt, Germany	European users with EU data residency requirements
PAR	Paris, France	European users; low-carbon region on the AWS European Sovereign Cloud
LON	London, United Kingdom	UK and Western Europe
SGP	Singapore	Southeast Asia and APAC
JPN	Japan	Japan and Northeast Asia
SYD	Sydney, Australia	Australia and Oceania
SFO	San Francisco, United States	US West Coast and Pacific
NYC	New York, United States	US East Coast and global default
SAO	São Paulo, Brazil	South America and Latin America

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 PAR are located in the EU, while LON is located in the UK. For workloads with strict European data sovereignty requirements, PAR runs on the AWS European Sovereign Cloud.

Minimize your carbon footprint. Regions differ in the carbon intensity of their local power grid. PAR is a low-carbon region thanks to France’s largely low-emission electricity mix. See carbon footprint for more on how region choice affects emissions.

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 accrues its own charges, billed together at the team or organization level.

Changing a region

Regions cannot be changed after a project is created. To move to a different region, create a new project in the target region and re-index your documents.

Requesting a new region

The list of available regions grows over time. If none of the current regions fit your requirements (latency, data residency, or compliance), contact [e-mail] to request a new one.

Multi-region replication

For Enterprise workloads that require data to be replicated across multiple regions (for disaster recovery, global low-latency search, or compliance), Meilisearch supports multi-region replication. This is an Enterprise feature that requires dedicated infrastructure setup. Contact [e-mail] to discuss your requirements.