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

# BYOIP

> Bring your own IPv4 address prefixes to Latitude.sh infrastructure

BYOIP (Bring Your Own IP) lets you use your own IPv4 address prefixes on Latitude.sh infrastructure instead of Latitude.sh-assigned addresses.

## Use cases

* **IP reputation preservation:** Keep your established IP reputation when migrating to Latitude.sh.
* **Compliance requirements:** Meet regulatory requirements that mandate specific IP ranges.
* **Brand consistency:** Maintain IP addresses associated with your organization.
* **Migration flexibility:** Move workloads without changing public-facing IP addresses.

## Requirements

Before requesting BYOIP, you need:

* **IP address prefix:** A publicly routable IPv4 address range in CIDR notation (e.g., `203.0.113.0/24`).
* **RIR registration:** The prefix must be registered with a Regional Internet Registry (ARIN, RIPE NCC, APNIC, LACNIC, or AFRINIC).
* **Route objects:** Route objects created for all prefixes you want to announce.
* **RPKI validation:** RPKI should be valid for all prefixes.
* **Authorization:** You must be able to prove ownership of the IP prefix.

## Requesting BYOIP

<Steps>
  <Step title="Navigate to IP addresses">
    Select a project and go to **Network → IP addresses**, then select the **BYOIP** tab.
  </Step>

  <Step title="Click Request BYOIP">
    Click the **Request BYOIP** button to open the request form.
  </Step>

  <Step title="Enter prefix information">
    Provide details about the IP prefixes you want to bring to Latitude.sh:

    * **Regional Internet Registry (RIR):** Select where your prefix is registered.
    * **Announcement site:** Select the Latitude.sh site where the prefix should be announced.
    * **Already announced:** Indicate whether you already have a prefix announced on this site.
    * **Prefixes:** List all prefixes in CIDR notation, one per line (e.g., `203.0.113.0/24`).
    * **Route objects:** Confirm whether route objects are created for all prefixes.
    * **RPKI:** Confirm whether RPKI is valid for all prefixes.
  </Step>

  <Step title="Select a deploy type">
    Choose how the prefix should be deployed on Latitude.sh infrastructure:

    * **BGP Session:** Establishes a BGP session between your machine and our router.
    * **Static Route:** Creates a static route to your machine.
    * **VLAN (HSRP/VRRP):** Sets up the prefix gateway on Latitude.sh infrastructure using VLAN with HSRP/VRRP.

    See [Deploy types](#deploy-types) for details on each option.
  </Step>

  <Step title="Provide deployment details">
    Depending on your selected deploy type, provide the required deployment details:

    * **BGP Session:** Select the server for the BGP peer, choose a route preference (full route, default route, or both), and enter your ASN.
    * **Static Route:** Select the server for the static route destination, enter your ASN, and optionally upload a Letter of Authorization (LOA).
    * **VLAN:** List the machines that will use these prefixes, enter your ASN, and optionally upload a Letter of Authorization (LOA).
  </Step>

  <Step title="Submit the request">
    Optionally add a use case description, then click **Submit Request**.
  </Step>
</Steps>

After you submit your request, the Network Operations team will review it and contact you with next steps.

## Deploy types

Choose how your prefix will be deployed when requesting BYOIP.

### BGP Session

Establishes a BGP session between your machine and the Latitude.sh router.

**Advantages:**

* You can choose to receive full route or default route.
* You can control your incoming traffic using BGP communities.
* None of your IPs will be on any part of the Latitude.sh network.

**Limitations:**

* You can only use your prefix on the server where the BGP session is established.

### Static Route

Creates a static route pointing to your machine.

**Advantages:**

* Simple to configure.
* None of your IPs will be on any part of the Latitude.sh network.

**Limitations:**

* You can only use your prefix on the server that the static route points to.

### VLAN (HSRP/VRRP)

Sets up the prefix gateway on Latitude.sh infrastructure using a VLAN with HSRP/VRRP.

**Advantages:**

* Simple to configure.
* Multiple servers can use IPs from this prefix by tagging the VLAN on the server's interface.

**Limitations:**

* Latitude.sh requires 3 IPs from each prefix (x.x.x.1, x.x.x.2, and x.x.x.3) for the HSRP/VRRP gateway.