IP addresses

Cequence AI Gateway uses fixed IP addresses for outbound connections. You can use these addresses to configure your firewall rules, security groups, and vendor allowlists anywhere AI Gateway needs to reach a system in your environment. These addresses will not change without notice.

This page applies to every feature that connects outbound from the gateway — you do not need a different set of addresses per feature.

Outbound IP addresses

These are the stable IP addresses that the Cequence-hosted (SaaS) AI Gateway connects from when it makes requests to your systems.

IPv4

34.132.39.216
34.170.84.5

Allowlist both addresses. Traffic can leave from either one, so permitting only one produces intermittent failures that are hard to diagnose.

These addresses are static NAT addresses. They are not the address of the AI Gateway portal, so allowlisting the portal hostname does not grant the access described here. The same addresses appear in the portal wherever a feature needs them, so you can confirm them at the point of configuration.

Private cloud and self-hosted deployments

If you run AI Gateway in your own cloud or data center, outbound connections originate from your infrastructure — your NAT gateway, egress IP, or load balancer — not from the Cequence-hosted addresses above.

Do not allowlist the Cequence-hosted addresses for a private cloud deployment unless Cequence Support has explicitly given you a different set to use. Ask your own cloud or network team for the egress address of the cluster running AI Gateway.

Tips

• Allowlist by IP and port. A rule scoped to a single host and port is far easier to get approved than a broad rule.
• If a connection test fails immediately with a timeout or connection-refused error, an allowlist gap is the most likely cause. Check it before investigating credentials.
• Confirm the target host is reachable from the public internet and presents a valid TLS certificate signed by a public CA. Allowlisting has no effect if the host is not routable, and AI Gateway validates certificates on outbound connections.
• For vendor-hosted targets, check whether allowlists are self-service or need a support case. That determines how long the change takes to land.
• Keep a note of where the rule was added — firewall, security group, or vendor allowlist. It saves time when something stops working after an unrelated network change.