Skip to content

docs: Link to current hosted-agent egress ranges #924

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bnavetta merged 2 commits into from
Oct 15, 2026
Merged

docs: Link to current hosted-agent egress ranges #924

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8e4d4d
docs: Link to current hosted-agent egress ranges
warp-agent-staging[bot] Oct 15, 2026
ad3b1d3
docs: Clarify hosted-agent traffic allowlisting
warp-agent-staging[bot] Oct 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 1 addition & 14 deletions src/content/docs/factories/warp-hosting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,20 +33,7 @@ To fairly allocate resources across all Warp users, concurrency of Warp-hosted a

### Networking

Warp's hosted agents have network egress enabled by default. Outgoing requests may come from the following IP addresses:

* `64.6.38.192/26`
* `64.6.39.192/26`
* `104.128.70.192/26`
* `104.128.71.192/26`
* `216.176.224.192/26`
* `185.212.186.0/24`
* `50.31.178.128/26`
* `50.31.146.192/26`
* `75.102.37.208/28`
* `44.253.165.189/32`
* `16.145.188.113/32`
* `16.145.133.251/32`
Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp agents, such as in a firewall policy, get Warp's IP address ranges from the "Warp-hosted agent networking" settings for your team. Find it on your team's **Platform** page in the [Admin Panel](https://app.warp.dev/admin/) or on <a href={`${VARS.FACTORY_WEB_APP_URL}/settings`}>User settings in the {VARS.FACTORY_WEB_APP}</a>.

@warp-for-oss warp-for-oss Bot Oct 15, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] Keep the traffic scope tied to Warp-hosted agents; “Warp agents” could be read as including local or self-hosted agents, whose egress does not use these hosted ranges.

Suggested change
Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp agents, such as in a firewall policy, get Warp's IP address ranges from the "Warp-hosted agent networking" settings for your team. Find it on your team's **Platform** page in the [Admin Panel](https://app.warp.dev/admin/) or on <a href={`${VARS.FACTORY_WEB_APP_URL}/settings`}>User settings in the {VARS.FACTORY_WEB_APP}</a>.
Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp-hosted agents, such as in a firewall policy, get the IP address ranges from the "Warp-hosted agent networking" settings for your team. Find it on your team's **Platform** page in the [Admin Panel](https://app.warp.dev/admin/) or on <a href={`${VARS.FACTORY_WEB_APP_URL}/settings`}>User settings in the {VARS.FACTORY_WEB_APP}</a>.


---

Expand Down
Loading