Skip to main content

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.

Bring Your Own IP (BYOIP) allows you to use your own addresses on CoreWeave Cloud. This feature is useful for customers who have existing IP address space and want to use it for their workloads. Before using BYOIP on CoreWeave Cloud, you must:
  • submit a Letter of Authorization (LOA) to CoreWeave,
  • pay a one-time setup fee,
  • meet the requirements outlined below, and
  • agree to CoreWeave’s Reservation of Rights, Terms of Service, and Acceptable Use Policy.

​
How to submit a Letter of Authorization (LOA)

Before advertising routes for your prefix, you must submit a written Letter of Authorization (LOA) to CoreWeave. The LOA must:
  • be on the Customer’s entity letterhead,
  • contain the entity’s full legal name, principal address, and phone number,
  • authorize CoreWeave to announce the Customer-owned IP space on Customer’s behalf, and
  • be signed by an authorized representative of the Customer entity.
The LOA should state the following:
“We [Customer] at AS[ASN] authorize CoreWeave at AS33425 to announce our IP block [x.x.x.x/yy] for an indefinite period of time.”
The LOA must include the name and title of the person signing the LOA, and the date signed. The LOA is a legally binding document and must contain a wet signature. It must be in .pdf format.
LOAs submitted as .jpeg or .png files will not be accepted.

​
Pricing

Please contact your CoreWeave Account Manager for detailed pricing information or refer to the CoreWeave Cloud Pricing page.

​
Addressing details

  • CoreWeave’s AS Number is 33425.
  • CoreWeave only supports IPv4 addressing.
You must supply CoreWeave with a valid, maintained abuse email contact for any abuse related mail. Each subnet that you request CoreWeave to advertise must not currently be in the global Internet routing table. The subnet must be solely owned and controlled by the Customer, and must be portable space. The addresses in the IP address range supplied to CoreWeave must have a clean history. CoreWeave may investigate the reputation of the IP address range, and reserves the right to reject or remove any IP address range from service if it contains an IP address that has a poor reputation or is associated with malicious behavior. The minimum supported subnet size is a /24 block. Each subnet block requested must have a route object in one of the mainstream route object registries such as ARIN, RIPE, RADB. This route object must also list CoreWeave’s AS Number (33425) as an origin. If you don’t have a routing registry that can be updated, CoreWeave can register the object at your request. If the block has been RPKI signed, then as with the route object, CoreWeave’s AS must be added to a new ROA request. Here is an example of a route object: 
route:    216.153.48.0/20
origin:   AS33425
descr:    CoreWeave, Inc.
admin-c:  SALAN13-ARIN
tech-c:   BJB20-ARIN
remarks:  https://coreweave.com
notify:   noc@coreweave.com
mnt-by:   MAINT-AS33425
changed:  bbianchi@coreweave.com 20211021  #21:29:43Z
source:   RADB

​
Reservation of Rights

The BYOIP Requirements are part of CoreWeave’s Terms of Service (TOS). By requesting BYOIP from CoreWeave, you agree to be bound by these Requirements, and you acknowledge and agree to all of CoreWeave’s reservations of rights.
CoreWeave is not responsible for, and does not provide, any DDoS protections for your blocks. If your block is the victim of a cyberattack, CoreWeave expressly reserves any and all rights to take whatever measures are necessary, in its sole discretion, to protect the security, integrity and availability of the CoreWeave platform, including but not limited to, at any time, withdrawing the announcement of your blocks. CoreWeave will notify the abuse contact on file. If a Customer’s advertised block is suspected, in CoreWeave’s sole discretion, or found to be in use for malicious or harmful purposes, CoreWeave expressly reserves the right to withdraw all of the Customer’s route advertisement. CoreWeave will notify the abuse contact on file. Continued participation in this configuration constitutes your acceptance of the TOS, and any other applicable policies. These CoreWeave Requirements for BYOIP are subject to change, in CoreWeave’s sole discretion. Please check back regularly to ensure you are satisfying all of the requirements. Failure to meet any requirement may result in the immediate suspension of your BYOIP subnet advertisements.
Last modified on April 2, 2026