langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 20:35:34 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[GH-ISSUE #2404] [langsmith]: Missing LangSmith Cloud egress IP in allowlist docs (EU): 34.90.213.236 #298

New Issue
Closed
opened 2026-02-17 17:19:35 -05:00 by yindo · 0 comments
yindo commented 2026-02-17 17:19:35 -05:00
Owner
Copy Link
Copy Source

Originally created by @farouk09 on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/langchain-ai/docs/issues/2404

Type of issue

issue / bug

Language

Python

Description

Hi,

I’m running a LangSmith Cloud deployment (EU region) that must connect outbound to my own Postgres. The docs list EU egress NAT IPs, but the actual observed egress IP for my deployment is 34.90.213.236, which is not in the published list.

Because it wasn’t listed, I spent significant time debugging firewall rules (OVH edge firewall + UFW) and TCP connectivity. Once I allowlisted 34.90.213.236, outbound TCP to my DB worked immediately.

Docs page referenced

“Allowlisting IP addresses → Egress from LangChain SaaS”
Current EU list (as of today):

  • 34.13.192.67
  • 34.147.105.64
  • 34.90.22.166
  • 34.147.36.213
  • 34.32.137.113
  • 34.91.238.184
  • 35.204.101.241
  • 35.204.48.32

Observed egress IP (EU deployment)

  • 34.90.213.236

Impact

Outbound connections from LangSmith Cloud were blocked by upstream firewall because the IP wasn’t in the documented allowlist. This caused psycopg.OperationalError: server closed the connection unexpectedly and TCP timeouts until the IP was explicitly allowed.
Request

Please update the documentation to include 34.90.213.236 or other IP adresses (or clarify how to reliably discover the actual egress IP per deployment).

Thanks!

Originally created by @farouk09 on GitHub (Jan 29, 2026). Original GitHub issue: https://github.com/langchain-ai/docs/issues/2404 ### Type of issue issue / bug ### Language Python ### Description Hi, I’m running a LangSmith Cloud deployment (EU region) that must connect outbound to my own Postgres. The docs list EU egress NAT IPs, but the actual observed egress IP for my deployment is 34.90.213.236, which is not in the published list. Because it wasn’t listed, I spent significant time debugging firewall rules (OVH edge firewall + UFW) and TCP connectivity. Once I allowlisted 34.90.213.236, outbound TCP to my DB worked immediately. Docs page referenced **“Allowlisting IP addresses → Egress from LangChain SaaS”** Current EU list (as of today): - 34.13.192.67 - 34.147.105.64 - 34.90.22.166 - 34.147.36.213 - 34.32.137.113 - 34.91.238.184 - 35.204.101.241 - 35.204.48.32 **Observed egress IP (EU deployment)** - 34.90.213.236 Impact Outbound connections from LangSmith Cloud were blocked by upstream firewall because the IP wasn’t in the documented allowlist. This caused psycopg.OperationalError: server closed the connection unexpectedly and TCP timeouts until the IP was explicitly allowed. Request **Please update the documentation to include 34.90.213.236 or other IP adresses (or clarify how to reliably discover the actual egress IP per deployment).** Thanks!
yindo added the langsmithexternal labels 2026-02-17 17:19:35 -05:00
yindo closed this issue 2026-02-17 17:19:35 -05:00
yindo changed title from [langsmith]: Missing LangSmith Cloud egress IP in allowlist docs (EU): 34.90.213.236 to [GH-ISSUE #2404] [langsmith]: Missing LangSmith Cloud egress IP in allowlist docs (EU): 34.90.213.236 2026-06-05 17:26:09 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label external langsmith
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#298
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?