> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/security/ip-addresses.md).

# IP Addresses

Pylon's static outbound IP addresses, for allowlisting Pylon in your firewall

Pylon sends requests to your systems from a fixed set of static IP addresses. If your firewall, database, or API only accepts traffic from known sources, allowlist the addresses for your Pylon region.

## Find your region

* If you sign in at `app.usepylon.com`, you're in the **US** region.
* If you sign in at `app.eu.usepylon.com`, you're in the **EU** region.

## Outbound IP addresses

{% tabs %}
{% tab title="US" %}

```
13.56.120.80
13.52.31.65
16.146.217.176
52.37.21.171
54.203.91.47
54.69.118.15
```

{% endtab %}

{% tab title="EU" %}

```
3.122.74.28
35.158.56.176
63.176.205.110
```

{% endtab %}
{% endtabs %}

{% hint style="warning" %}
Allowlist every address for your region, not just one. Requests can leave from any of them, and two requests for the same feature (for example, a test webhook and a live webhook) can come from different addresses.
{% endhint %}

## What uses these addresses

Any request Pylon's servers make to your systems comes from these addresses, including:

* [Outgoing webhooks](/pylon-docs/developer/webhooks.md), including test webhooks
* [Data warehouse](/pylon-docs/integrations/data-warehouse.md) syncs to Snowflake, Redshift, and BigQuery, and the connection checks during setup
* Product data syncs
* [Custom app](/pylon-docs/developer/custom-apps.md) requests to your API endpoint, including endpoint verification
* Calls to the integrations you connect, such as your CRM or self-hosted tools
* MCP connectors and API tools used by AI agents

## What doesn't use these addresses

* [Embedded iframes](/pylon-docs/developer/embedded-iframes.md) load in your team's browser, so those requests come from your team's own network.
* Traffic you send to Pylon. These addresses are only the source of Pylon's outbound requests, not the address of the Pylon app or API. Connect to Pylon by hostname.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/security/ip-addresses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.