Configure Supabase Network Restrictions

Add the IP addresses

Add each IPv4 CIDR below to the project's Network Restrictions allowlist.

Backup connections come from a fixed set of outbound addresses, shared by the onboarding check and by scheduled backup and restore work. Any connection can use any address in the set, so add all of them. A partial allowlist lets backups fail on an irregular schedule.

208.77.244.240/32
152.55.184.241/32
152.55.185.190/32
208.77.244.241/32
152.55.184.240/32
152.55.185.189/32

Allowlisting these addresses permits network traffic only. Database access still requires a valid temporary login.

Update the project allowlist

1. Open the project in the Supabase dashboard, then go to Database Settings.
2. Under Network Restrictions, choose Add restriction.
3. Add each CIDR listed above. Keep any existing ranges the project still needs.
4. Save the changes, wait for them to apply, then retry the connection or backup.

You need the Owner or Administrator role in Supabase to change Network Restrictions. If the setting is unavailable, the project may need a Postgres version update first.

What Network Restrictions affect

• Network Restrictions apply to direct Postgres and connection pooler traffic before database authentication.
• They do not apply to Supabase HTTPS APIs, including Auth, Storage and PostgREST.
• Each backup uses a temporary database login that expires after six hours. Removal is requested when the job ends.

Supabase documentation: Network Restrictions