Skip to content

Dedicated.com BYOIP Integration Overview

BYOIP SUPPORTER
ASN 63018
IPv4 support
IPv6 support
LOA support
ROA support
Process Manual
Locations supported
Other: Canada, United States

This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Dedicated.com (legal entity: US Dedicated LLC) and its North American hosting/colocation footprint. Dedicated.com productizes BYOIP as a ticket-provisioned service with three options: (1) Dedicated.com originates your prefixes as AS63018, (2) Dedicated.com originates the route to upstreams while presenting your ASN as the origin, or (3) you run a customer-managed BGP session. BYOIP is explicitly location-bound: Dedicated.com assigns your IP ranges to a VLAN for pooled use within a given location and states it does not provide anycast/internal backhaul to use the same range across multiple locations.

Provider Details

FieldInformation
Provider NameDedicated.com (US Dedicated LLC)
Website Dedicated.com Homepage | BYOIP Knowledgebase Article | Colocation (Locations) | Terms of Service (Legal Entity) | PeeringDB (AS63018)
ASN(s) Dedicated.com’s public network ASN is AS63018. PeeringDB lists IRR as-set/route-set AS63018:AS-ALL.
Regions Supported Dedicated.com markets North American locations across the United States and Canada. Public location navigation on Dedicated.com includes:
United States: Atlanta (GA), Chicago (IL), Dallas (TX), Los Angeles (CA), New York (NY), Seattle (WA).
Canada: Montreal (QC).
Support Contact Client Portal / Support Tickets | Contact | Public phone shown on site: +1-844-533-1300
Tech Article & Date Bringing Your Own IP Addresses / BYOIP – Dedicated.com Knowledgebase (no public publish date displayed on the page).
BYOIP Scope Dedicated.com states it can assign your IP ranges to your VLAN and you can use them in a “pool” manner within a given location. It also states it does not provide anycast/internal backhaul to use the same range across multiple locations. BYOIP can be used with dedicated servers, per-device colocation, and full-rack colocation, but is not available for VPS. BYOIP does not include custom carrier routing.
Supported Versions The BYOIP knowledgebase article describes bringing “IP ranges” but does not explicitly break out IPv4 vs IPv6 requirements or minimum prefix sizes. Confirm supported families and prefix sizing during onboarding.
Supported Services – Dedicated servers
– Per-device colocation
– Full-rack colocation
Not supported: VPS

Technical Requirements

RequirementDetails
Prefix Size Not explicitly specified in the BYOIP knowledgebase article. In practice, Internet-routable announcements typically require globally accepted minimums (commonly IPv4 /24+, IPv6 /48+), but you should confirm Dedicated.com’s acceptance criteria and any upstream constraints during onboarding.
ASN Ownership Required Option 1: No (Dedicated.com originates as AS63018).
Option 2: Yes (your ASN is used as origin, while Dedicated.com still advertises to upstreams).
Option 3: Yes (customer-managed BGP session; you must demonstrate BGP competence).
IRR / Route Objects Dedicated.com requires IRR objects to be set correctly and states it verifies via IRR Explorer.
Option 1: IRR objects must specify AS63018 as valid origin.
Option 2: IRR objects must specify your ASN as valid origin.
ROA (RPKI) or LOA LOA: Required for Options 1 and 2, on proper letterhead, signed, naming the prefix, authorizing AS63018, and including valid contact information for upstream confirmation.
RPKI/ROA: Not required, but Dedicated.com “strongly recommends” RPKI (and RADB).
Location Prerequisite For all three options, Dedicated.com states you must have an active or paid pending server or colocation service in the same location where BYOIP will be implemented.

Step-by-Step BYOIP Process

Estimated Setup Time: Dedicated.com publishes 2–4 US business days depending on the chosen option and assuming prerequisites (service-in-location, LOA/IRR hygiene) are met.

Tested By Us: Not yet

A) BYOIP Onboarding (Options 1 and 2 — Dedicated.com-managed announcements)

  • Confirm scope and location. Ensure you have an active or paid pending Dedicated.com dedicated server or colocation service in the target location where the prefix will be used.
  • Prepare authorization artifacts. Draft an LOA on proper letterhead, signed, explicitly authorizing AS63018 to announce the specified prefix, and include valid contact details for upstream verification.
  • Fix IRR hygiene. Create/update IRR route objects so they specify the correct origin: AS63018 for Option 1, or your ASN for Option 2. Dedicated.com states it validates via IRR Explorer.
  • (Recommended) Align RPKI/ROA. Although not required, publish ROAs that authorize the intended origin ASN to reduce the risk of invalid-route filtering.
  • Open a BYOIP ticket. Submit your prefix details, target location, desired option (1 or 2), and any VLAN/location routing requirements. Batch changes per location where possible to reduce change-fee events.
  • Validate production routing. After implementation, confirm visibility/reachability of the route (and that traffic lands in the intended Dedicated.com location). Establish monitoring and a change-control process for future moves, VLAN changes, de-announcements, or additional ranges.

B) BGP Session (Option 3 — customer-managed announcements)

  • Confirm whether Option 3 is appropriate. Dedicated.com states BGP sessions are not covered by its SLA, and issues caused by improper customer configuration are handled during US business hours only.
  • Ensure prerequisites. Have an active or paid pending service in the target location and be prepared to demonstrate BGP competence (e.g., ability to configure sessions and advertise routes without Dedicated.com consulting/design).
  • Open an Option 3 ticket. Request the BGP session for the location and obtain peering IPs/parameters from Dedicated.com.
  • Configure your router/stack (e.g., FRR/BIRD) and announce the authorized prefixes. Keep IRR/RPKI data aligned with your intended origin and ensure route stability to avoid dampening or filtering by upstreams.
  • Operate with heightened monitoring. Because routing is customer-managed, implement continuous validation (route collectors, probes, alerting) and strict change management to prevent outages or accidental withdrawals.

Cost and Limitations

ItemDetails
Fees Dedicated.com publishes the following BYOIP fees:
Option 1 (origin AS63018): $25 setup per announcement; $25 per change request; $0/month.
Option 2 (origin your ASN): $100 setup per location; $25 per change request; $25/month per location.
Option 3 (BGP session): $250 setup per location; $25 per change request; $100/month per location.
Setup-fee waiver note: customers paying more than $2,000/month can request a waiver of setup fees.
Bundled or Standalone BYOIP is provisioned in support of Dedicated.com services in the same location (dedicated servers and colocation). Dedicated.com states you must have an active or paid pending service in-location for implementation.
Traffic/Peering Restrictions – Dedicated.com states BYOIP does not include custom network routing (e.g., choosing specific carriers).
– BYOIP is explicitly location-bound: Dedicated.com states it does not provide anycast/internal backhaul to use the same range across multiple locations.
Other LimitationsNo VPS: Dedicated.com states BYOIP is not available for VPS services.
Option 3 support posture: Dedicated.com states BGP sessions are not covered by its SLA, and issues caused by improper customer configuration are handled during US business hours only.
– Operational changes (moving a range, VLAN assignment, CIDR division changes, de-announcement with active services) are explicitly treated as chargeable change events under the published change-fee policy.

Automation & Developer Access

  • Ticket-based onboarding: Dedicated.com describes BYOIP as a support-provisioned service (LOA/IRR validation + implementation) with published lead times rather than a self-serve portal flow.
  • Change-control planning: Because many operational actions (e.g., moving a prefix between locations, changing VLAN assignment, CIDR division changes) are processed as chargeable change requests, treat BYOIP operations as part of your formal network change process.
  • BGP automation is customer-side only (Option 3): Dedicated.com does not describe a BYOIP API; for BGP session scenarios, automation typically comes from your own router stack and infrastructure-as-code controlling your configuration and monitoring.

Abuse & Reputation Management

  • Authorization chain: Dedicated.com requires an LOA for Options 1 and 2 and requires valid contact information for upstream verification. Maintain reachable, monitored contacts to prevent delays or route withdrawals.
  • Routing trust hygiene: Dedicated.com strongly recommends RPKI (and RADB). Keeping ROAs and IRR objects correct reduces the risk of invalid-route filtering or hijack exposure when advertising your space.
  • Customer responsibility: Dedicated.com’s Terms of Service emphasize client responsibility for account actions and service usage. For BYO prefixes, you remain responsible for abuse handling and IP reputation management associated with your address space.

Dedicated.com Knowledgebase: Bringing Your Own IP Addresses / BYOIP
Colocation Locations (USA & Canada)
Example Location Page: Los Angeles Datacenter
Example Location Page: Montreal Datacenter
Terms of Service (US Dedicated LLC)
PeeringDB: US Dedicated / Dedicated.com (AS63018)

FAQ

BYOIP, or Bring Your Own IP, is a service that enables organizations to bring their own public IP addresses—whether owned outright or leased from an IP provider—into a service provider’s network infrastructure. Instead of relying on IP addresses assigned by the provider, BYOIP allows businesses to retain control over their IP resources. This ensures continuity, particularly for organizations with established IP-based reputations, branding, or dependencies on specific address blocks. IP providers can assist in streamlining this process, making it easy to integrate your IPs into the desired network environment.

BYOIP offers several compelling advantages. By using your own IPs, you can maintain continuity in your network’s identity, reduce the risk of disruptions to email deliverability or service recognition, and avoid reputational concerns associated with shared IPs. Additionally, BYOIP provides enhanced flexibility and control over your IP resources.

BYOIP is ideal for organizations that either own public IP addresses or lease them from a trusted IP provider with explicit BYOIP support. This includes enterprises, cloud providers, content delivery networks (CDNs), and businesses with compliance requirements or IP reputation needs. Working with a reputable IP provider ensures that leased IPs can be seamlessly integrated into another provider’s infrastructure without ownership concerns.

You must either legally own the IP addresses or have explicit authorization from a leasing IP provider to route and manage them. IP providers who offer BYOIP-ready IP addresses simplify this process, providing documentation and support to ensure compliance with regional internet registry (RIR) policies and service provider requirements. This collaboration ensures smooth implementation without any legal or operational issues.

To use BYOIP, you’ll typically need to present documentation verifying your authority over the IP block. This can include official records from a regional internet registry (RIR) such as ARIN, RIPE NCC, or APNIC. If you are leasing IPs, the IP provider should supply proof of their ownership and grant you permission for BYOIP. Providers that specialize in IP leasing often handle this paperwork for you, reducing administrative burden and ensuring compliance.

Yes, BYOIP is designed to be a secure and reliable solution. Reputable service providers and IP providers implement robust safeguards to prevent unauthorized use or hijacking of IP addresses. Security measures include BGP filtering, route validation, and advanced protocols like Resource Public Key Infrastructure (RPKI). By collaborating with a trusted IP provider, businesses can benefit from additional layers of protection, ensuring that only authorized traffic is routed through their IP blocks.

The setup process for BYOIP varies by provider, typically taking anywhere from a few hours to a few days. Factors include the complexity of your network, the verification process for IP ownership or authorization, and the time needed for global BGP route propagation. IP providers often expedite the preparation and validation stages, ensuring a smooth and timely integration into the desired infrastructure.

Absolutely. Many providers, in partnership with IP providers, support routing IPs across multiple data centers or geographic regions. This feature optimizes performance for global businesses by reducing latency and improving service availability. When working with an IP provider, you can also ensure that your leased or owned IPs are aligned with your geographic requirements for compliance and efficiency.

If you choose to discontinue BYOIP with a provider, your IP addresses will be released from their network, and routing will cease. You can then reallocate these IPs for use with a different service provider or project.