Hey team,

I'm building a consumer app targeting Mexico and Latin America (expense splitting). Right now my project is on us-east-1 since that's the closest useful option, but my core users are in Mexico (Guadalajara, CDMX, Monterrey).

AWS already has a Mexico region available (mx-central-1) since early 2025. Would love to see Supabase support it, even just as a specific region option.

Why it matters:

Latency from central Mexico to us-east-1 is noticeable (~80-120ms round trip) vs what a local region would give
Mexico's startup/dev ecosystem is growing fast — there's real demand here
Data residency is becoming a bigger deal with Mexican regulations (LFPDPPP and its 2025 updates)
There's currently no LATAM region that actually helps Mexican users — São Paulo is even farther than Virginia

I know region expansion depends on demand and infrastructure capacity, just wanted to add another voice here. Would be great to keep things closer to home.

Cheers from Guadalajara

How to help

Erick A. Sanchez A. requests Supabase to support a new region in Mexico (mx-central-1) to improve latency and comply with local data residency regulations. He highlights the growing demand in Mexico's startup ecosystem and the limitations of current region options for Mexican users.

Help on GitHub