---
title: Networking & IP Ranges
description: Networking details for Langfuse Cloud.
---

# Networking

## AWS PrivateLink

**Where is this feature available?**

| Plan | Availability |
| --- | --- |
| Hobby | Not Available |
| Core | Not Available |
| Pro | Not Available |
| Enterprise | Available |
| Self Hosted | Not Available |

Langfuse Cloud uses public regional endpoints by default. AWS PrivateLink is an optional feature available to Enterprise customers with a committed contract, subject to regional availability and onboarding requirements. [Talk to our sales team](/talk-to-us) to discuss availability for your region.

If you require private connectivity and infrastructure fully controlled by your organization, consider [self-hosting Langfuse](/self-hosting). [Book time with us](/talk-to-us) to discuss the best solution for your security needs.

## Langfuse Cloud Egress IP Addresses

Langfuse Cloud makes outbound API calls from our infrastructure on behalf of users for features like LLM-as-a-judge evaluations or blob storage exports. For enhanced security, you may want to whitelist these IP addresses in your firewall or security group settings to allow these specific connections.

**The IP addresses are as follows:**

| Region   | IP Addresses                                      |
| -------- | ------------------------------------------------- |
| US-HIPAA | 35.82.248.193<br/>34.211.191.155<br/>52.43.164.18 |
| US       | 35.81.129.167<br/>44.232.137.35<br/>52.34.39.144  |
| EU       | 54.77.243.21<br/>52.30.45.150<br/>54.216.18.112   |
| JP       | 13.158.173.105<br/>3.114.153.88<br/>52.198.13.188 |

## Contact

For questions regarding networking, please [talk to us](/talk-to-us).

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/security/networking.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.