CoreWeave BYOIP Integration Overview
Location
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with CoreWeave Cloud. CoreWeave currently supports a provider-announced BYOIP model: your IPv4 prefixes are originated by CoreWeave (AS33425) and attached to workloads via CoreWeave networking (VPCs, public IPv4, CKS clusters).
Provider Details
| Field | Information |
|---|---|
| Provider Name | CoreWeave |
| Website | Bring Your Own IP (BYOIP) | Networking overview | Public IPv4 | Networking pricing (BYOIP) |
| ASN(s) | Primary cloud ASN: AS33425 (CoreWeave, Inc.) — origin for BYOIP prefixes. |
| Regions Supported | CoreWeave operates multiple Regions and AZs across the US and Europe (e.g. US-EAST-01, US-WEST-01 with multiple AZs). BYOIP is a networking feature tied to CoreWeave’s public IP/VPC fabric; concrete Region availability should be confirmed with CoreWeave account/support based on your deployment. |
| Support Contact | Contact Sales | Support via Cloud Console / email |
| Tech Article & Date | Bring Your Own IP (CoreWeave networking docs; accessed 2025-11) and Network Pricing (BYOIP section). |
| BYOIP Scope | Provider-announced: CoreWeave advertises your IPv4 /24+ prefixes from AS33425. BYOIP is used to map your space to CoreWeave workloads via public IPv4/VPC; no customer-run BGP sessions are involved in the BYOIP feature. |
| Supported Versions | IPv4 only for BYOIP. CoreWeave’s BYOIP requirements explicitly state that only IPv4 addressing is supported; IPv6 BYOIP is not currently documented. |
| Supported Services | BYOIP prefixes are consumed wherever public IPv4 is used on CoreWeave (e.g. services exposed via Public IPv4, load-balanced endpoints, and internet-facing workloads in VPCs and CKS clusters). Exact patterns are deployment-specific and configured via the Cloud Console / APIs. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | BYOIP currently supports IPv4 only. Minimum subnet size is a /24 (256 IPv4 addresses) per the BYOIP requirements. Smaller prefixes are not supported. |
| ASN Ownership Required | No customer ASN/BGP session is required for BYOIP. CoreWeave originates the prefixes from AS33425 on your behalf. The LOA template includes your ASN if you have one, but the routing is performed by CoreWeave’s ASN, not via your own BGP sessions. |
| IRR / Route Objects | Each subnet you request CoreWeave to advertise must have a route object in a mainstream IRR (e.g. ARIN, RIPE, RADB) that lists AS33425 as the origin. If you cannot update IRR yourself, CoreWeave can create the route object on your behalf upon request. |
| ROA or LOA | LOA: A Letter of Authorization is mandatory. It must be on your organization’s letterhead, explicitly authorize CoreWeave (AS33425) to announce the specified IPv4 block(s), include your organization details (and ASN if applicable), name/title of the signatory, date, and a handwritten (“wet”) signature. The LOA must be supplied as a PDF; image formats (JPEG/PNG) are not accepted. ROA (RPKI): If the block is RPKI-signed, you must update/add a ROA that includes AS33425 as a valid origin before CoreWeave can advertise the prefix. |
| RIR Limitations | Prefixes must be portable IPv4 space that is solely owned and controlled by you and registered in a RIR with accurate contact information. Each subnet: – Must not currently be present in the global Internet routing table when you hand it to CoreWeave. – Must have a clean reputation. CoreWeave may investigate and can reject or remove ranges if they contain IPs associated with abuse or malicious behavior. A maintained abuse contact email is required for the space. |
Step-by-Step BYOIP Process
Estimated Setup Time: Not explicitly documented by CoreWeave; practically, expect several business days for LOA review, IRR/RPKI validation, and internal provisioning, plus normal Internet BGP propagation time (often < 24 hours once advertisements start).
Tested By Us: Not yet
Provider-announced BYOIP (CoreWeave originates your IPv4 prefixes)
References: Bring Your Own IP, About Networking, Public IPv4, Create and Manage VPCs.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | BYOIP setup fee: Each IPv4 address has a one-time, non-refundable setup fee of $4.00, payable upon CoreWeave’s acceptance of your LOA. Standard Public IPv4 monthly pricing applies where these addresses are bound as public IPs, plus normal compute/storage charges. |
| Bundled or Standalone | BYOIP is a networking feature integrated with CoreWeave’s VPC and Public IPv4 products. It can be used alongside services like Direct Connect (DX) for hybrid connectivity, but BYOIP onboarding itself is driven via support and not a self-service API toggle. |
| Traffic/Peering Restrictions | Prefixes must have a clean reputation. CoreWeave may investigate IP reputation and can reject or later remove ranges that contain abusive or malicious activity. All usage must comply with CoreWeave’s Terms of Service and Acceptable Use Policy. Routing/peering specifics follow CoreWeave’s upstream/backbone policies and are not customer-tunable via BYOIP. |
| Other Limitations |
|
Automation & Developer Access
Abuse & Reputation Management
Related Resources
CoreWeave Homepage
Bring Your Own IP (BYOIP)
About Networking on CoreWeave
Public IPv4
Create and Manage VPCs
Network Pricing (Public IP & BYOIP)
Support & Contact (Docs)