Skip to main content

Allowlisting IP addresses

Egress from LangChain SaaS

Internet-bound traffic leaving LangSmith services is routed through a NAT gateway and originates from the following IP addresses. Vertex AI requests can use a different path, as described in Allow Vertex AI access.
Agents on LangSmith Agent Server egress from a separate IP list.
Allowlisting these IP addresses may be useful when connecting to your own AzureOpenAI service or other endpoints required by the Playground or Online Evaluation.

Allow Vertex AI access

For Vertex AI connections from LangSmith SaaS on GCP, public egress IP allowlisting alone might not satisfy VPC Service Controls. Private Google Access keeps Google API traffic within Google’s network instead of using the NAT gateway’s public IP addresses. See Google’s source IP access guidance. Configure a VPC Service Controls ingress rule for the source project corresponding to your LangSmith SaaS region: These source projects are specifically for Vertex AI connections from the US, EU, and APAC GCP SaaS regions. Use the numeric projects/PROJECT_NUMBER value in the ingress rule, not the project ID. Restrict the rule to the calling identity, your destination projects, and the required Vertex AI operations. The connection still requires the appropriate IAM permissions. See Google’s ingress rule configuration. Select the source project by your LangSmith SaaS region, not the Vertex AI model’s region. Pod or node scaling does not change the source project number. Moving the source workload or VPC network to another project can change the required allowlist.

Egress IP inventory

Fetch the egress IP inventory (JSON) to automate allowlist updates. Filter addresses by:
  • service: langsmith or langsmith-deployment (deployed agents).
  • cloud: gcp, aws, or azure.
  • region: us, eu, or apac.
Allowlist every matching cidr. Listed addresses may be used now or in the future. Poll periodically and compare version to detect changes. Review additions and removals before updating firewall rules.

Ingress into LangChain SaaS

The LangChain endpoints map to the following static IP addresses. Traffic terminates on the GCP load balancers (US/EU/APAC), the Azure ingress in centralus, or, for AWS US, the Network Load Balancer in us-east-2 (API and gateway hostnames): Allowlist every address in the column for your region so your private network can reach LangSmith Cloud (api.smith.langchain.com, smith.langchain.com, beacon.langchain.com, eu.api.smith.langchain.com, eu.smith.langchain.com, eu.beacon.langchain.com, apac.api.smith.langchain.com, apac.smith.langchain.com, apac.beacon.langchain.com, azure.smith.langchain.com, azure.api.smith.langchain.com, beacon.azure.langchain.com, aws.api.smith.langchain.com, aws.smith.langchain.com). GCP US, EU, and APAC are moving to the additional addresses in the last row (34.56.47.75, 34.32.254.168, and 34.151.160.163). Add those addresses now. The current GCP addresses keep serving these hostnames until February 10, 2027. After that date, the hostnames use only the additional addresses. Remove a current GCP address from your allowlist only after the hostname no longer resolves to it. The AWS US and Azure addresses are not changing. This list is only for LangSmith Cloud. A BYOC or self-hosted deployment uses the load balancer in your own environment. If your private network reaches Cloud over the public internet, including through a BYOC control plane connection, allowlist the Cloud addresses for your region. AWS PrivateLink, GCP Private Service Connect, and Azure Private Link do not use these addresses.