Network Restrictions

Each Supabase project comes with configurable restrictions on the IP ranges that are allowed to connect to Postgres and PgBouncer ("your database"). These restrictions are enforced before traffic reaches your database. If a connection is not restricted by IP, it still needs to authenticate successfully with valid database credentials.

To get started:

1. Install the Supabase CLI 1.22.0+.
2. Log in to your Supabase account using the CLI.
3. If your project was created before 23rd December 2022, it will need to be upgraded to the latest Supabase version before Network Restrictions can be used.
4. Ensure that you have Owner or Admin permissions for the project that you are enabling network restrictions.

Check restrictions#

You can use the get subcommand of the CLI to retrieve the restrictions currently in effect.

If restrictions have been applied, the output of the get command will reflect the IP ranges allowed to connect:

If restrictions have never been applied to your project, the list of allowed CIDRs will be empty, but they will also not have been applied ("Restrictions applied successfully: false"). As a result, all IPs are allowed to connect to your database:

Update restrictions#

The update subcommand is used to apply network restrictions to your project:

The restrictions specified (in the form of CIDRs) replaces any restrictions that might have been applied in the past. To add to the existing restrictions, you must include the existing restrictions within the list of CIDRs provided to the update command.

Remove restrictions#

To remove all restrictions on your project, you can use the update subcommand with the CIDR 0.0.0.0/0:

Limitations#

• The current iteration of Network Restrictions applies to connections to Postgres and PgBouncer and doesn't currently apply to APIs offered over HTTPS (e.g., PostgREST, Storage, and Auth).
• Network Restrictions should not be used if you need to connect to your Postgres database using Edge Functions.