Regions
The nine regions you can run a SupaHost instance in, how to choose one, where your data and backups are stored, and why the region can't be changed later.
You choose a region when you create your instance. The VM, every project's database and Storage files, and the instance's backups all live in that region. Pick it carefully, because it can't be changed after the instance is created.
Available regions
| Region | Area |
|---|---|
| US Central | North America |
| US West | North America |
| US East | North America |
| Belgium | Europe |
| London | Europe (United Kingdom) |
| Frankfurt | Europe |
| Singapore | Asia Pacific |
| Sydney | Asia Pacific |
| Tokyo | Asia Pacific |
The region of your instance is shown on the Instance page and on each project's Overview and Settings tabs.
What lives in the region
| Data | Where it's kept |
|---|---|
| Project databases | On the instance's disk, in your region |
| Storage files | On the instance's disk, in your region |
| Daily backups and the WAL used for point-in-time recovery | A private bucket in the same region |
| Exports (pg_dump files and Storage archives) | Created on the instance and downloaded from https://<instance>.supahost.space/exports/... |
All projects on one instance share its region. You can't put one project in London and another in Tokyo on the same instance.
For more on where data goes, including emails and account data, see Data protection and privacy and Where is my data stored?.
Choosing a region
Every request from your app to the Data API, Auth, Storage, Realtime or Edge Functions travels to the region and back. A few guidelines:
- Put the instance near your app servers. If your Next.js app runs on Vercel functions or a container in Frankfurt, a Frankfurt instance keeps server-side queries fast. Server-side code often makes several database calls per page, and each one pays the round trip.
- Otherwise, put it near most of your users. For a browser or mobile app that talks to SupaHost directly, the distance between the user and the instance matters most.
- Think about data rules. If your customers expect their data to stay in the UK or the EU, choose London, Belgium or Frankfurt.
A quick way to compare is to time a request to your project from where your code runs:
curl -o /dev/null -s -w "total: %{time_total}s\n" \
-H "apikey: $SUPABASE_ANON_KEY" \
https://app-one.acme.supahost.space/auth/v1/health
Run it a few times and look at the typical value, not the first one.
If your app host lets you pick a region for server functions, set it to match the instance. On Vercel, for example, that's the function region in project settings; see Deploying your app on Vercel.
Changing region
An instance's region is fixed once it's created. Moving to a different region means setting up a new instance there and moving your projects across, using exports or the steps in Moving off SupaHost. Contact [email protected] before you start so the move can be planned. See Changing an instance's region.