Action Gateway Outgoing IP Addressespublic

Last verified 18 Nov 2026

Action Gateway connects applications and AI agents to tools through a managed MCP endpoint or SDK, with the accounts and permissions you choose. See What You Can Build for standalone agent examples.

Action Gateway calls external services, such as Snowflake, on your behalf. Some services only accept connections from approved IP addresses. If a service restricts access by IP address, for example with an allowlist or network policy, allow the addresses on this page so Action Gateway can reach it.

Outgoing IP Addresses

Action Gateway tool calls to public services come from these IPv4 addresses. This includes tool calls made from code that runs in the Code Execution tool (action_code), because those calls go through Action Gateway.

  • 129.212.241.165
  • 209.38.2.205
  • 165.245.149.125
  • 165.245.156.118
  • 24.144.69.169

Allow all five addresses. Calls can come from any of them, and the addresses are the same in every region.

Direct network requests from the Code Execution tool, such as an HTTP request in its Python code, run in a separate sandbox and do not come from these addresses.

These addresses are fixed. If they change, we update this page and announce the change in the release notes.

Calls to Private Networks

These addresses apply to calls to public services. Calls that go through a VPC do not come from these addresses. For the source addresses to use in firewall rules for private destinations, contact DigitalOcean Support. For the private network setup, see Access Tools and MCP Servers on a Private Network.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.