> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Does outbound traffic have a stable public IP?

Yes. Outbound traffic from your Pods leaves the cluster through a NAT that uses a documented set of public IP ranges per Availability Zone. Use those ranges when allowlisting CoreWeave-originated traffic in external services such as MongoDB Atlas, partner APIs, or firewalled databases.

The current `NAT Egress` ranges for each AZ are listed in the **Network information** table on each region page. See [Regions and Availability Zones](https://docs.coreweave.com/platform/regions/about-regions-and-azs.md) for an overview, or go directly to a specific region:

* [US-EAST](https://docs.coreweave.com/platform/regions/us-east.md)
* [US-CENTRAL](https://docs.coreweave.com/platform/regions/us-central.md)
* [US-WEST](https://docs.coreweave.com/platform/regions/us-west.md)
* [CA-EAST](https://docs.coreweave.com/platform/regions/ca-east.md)
* [EU-NORTH](https://docs.coreweave.com/platform/regions/eu-north.md)
* [EU-SOUTH](https://docs.coreweave.com/platform/regions/eu-south.md)
* [EU-WEST](https://docs.coreweave.com/platform/regions/eu-west.md)

For VPC and CIDR fundamentals, see [About VPCs](https://docs.coreweave.com/products/networking/vpc/about-vpcs.md).

***

[Administrator](https://docs.coreweave.com/support/networking/tags/administrator.md)
