Does Cloud SQL Authorized Networks block dynamic IP addresses?

We are using Firebase Data Connect with Cloud SQL (PostgreSQL).

The Cloud SQL instance is configured with Authorized Networks (IP whitelist).
A developer claims that connections from dynamic IPs (e.g. home ISP)
are not supported and that only static IPs work,
even when the current public IP is added with /32.

However, our understanding is that Authorized Networks should allow
any public IP (static or dynamic) as long as the correct public IP is registered.

Could someone please confirm:

  1. Whether Cloud SQL Authorized Networks technically block dynamic IPs by design
  2. Or if dynamic IPs should work as long as the current public IP (/32) is registered
  3. If there are known cases (CGNAT, Private IP only, Data Connect restrictions)
    where this behavior may occur

This confirmation will help us determine whether this is an architectural limitation
or a configuration issue.

Colu

You can take a look at this document: Authorize with authorized networks to understand what is meant by an authorized network in GCP Cloud SQL.

At the same time, could you please let me know which method you’re using to connect to the SQL Server, and which parameters you’re using such as host IP (public or private), port, and whether SSL is enabled?