Whitelisting NinjaCat IP Addresses for Smart Connectors

Default behavior: rotating public IPs

By default, NinjaCat Smart Connectors (SQL and FTP data sources) connect to your hosted database or FTP server using rotating public IP addresses, not a fixed set of IPs. For most integrations, no firewall changes are needed on your end.

When IP whitelisting is required

If your database or FTP server enforces IP-based firewall restrictions, rotating IPs won't get through. In that case, we need to switch your account over to connect from a fixed, unchanging IP address instead — this isn't turned on by default.

Before whitelisting anything, contact NinjaCat Support and ask to have your account set up to connect from a fixed IP address. Support will confirm once this is in place. Whitelisting the IP addresses below won't do anything until then — your connection will keep coming from a rotating IP in the meantime.

IP addresses to whitelist (once your account is set up for a fixed IP)

Once NinjaCat Support has confirmed your account is set up to use a fixed IP address, whitelist the following addresses on your firewall or database:

34.233.103.179
18.205.207.33
18.207.37.148
3.238.219.42
44.200.245.248
34.206.137.144
54.152.10.145
3.41.177.160/28

Exceptions: S3 and Snowflake

If your data source is an S3-hosted bucket or a Snowflake-hosted database, do not use IP whitelisting. These connections should be configured as direct connections instead — reach out to NinjaCat Support for setup help.

Still seeing connection errors after whitelisting?

If your firewall already allows the addresses above and you're still seeing authentication or connection errors, contact NinjaCat Support with your dataset ID and the error message. This usually means your account hasn't been switched over to a fixed IP address on our end yet.