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

# Revenium Outbound IP Addresses

The outbound IP addresses Revenium connects from, for allow lists on GitHub, GitLab and other systems that restrict access by IP address.

When Revenium connects to one of your systems, such as a GitHub enterprise or a self-managed GitLab instance, it connects from a fixed set of outbound addresses. If that system restricts access by IP address, add these addresses to its allow list.

This page is the single list of these addresses. Integration pages link here rather than repeating them, so check this page when you set up or review an allow list.

## US production environment (`revenium.ai`)

```
18.235.50.20
34.202.200.107
44.210.6.197
```

Allow all three. Revenium's requests rotate across them, so approving only one or two causes intermittent failures.

## Other regions

If your account is hosted in the EU region, contact support for that region's addresses.

## Where to add them

* **GitHub:** see [Network requirements](/track-and-control-costs/analyze-ai-tooling-spend/github-integration.md#network-requirements) on the GitHub integration page for where an enterprise or organization owner adds the addresses.
* **GitLab:** see [Network requirements](/track-and-control-costs/analyze-ai-tooling-spend/gitlab-integration.md#network-requirements) on the GitLab integration page for self-managed instances behind a firewall.


---

# 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.revenium.io/integrations/outbound-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.