Dedicated.com BYOIP Integration Overview
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
| Field | Information |
|---|---|
| Provider Name | Dedicated.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
| Requirement | Details |
|---|---|
| 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
Prepare authorization artifacts
Fix IRR hygiene
(Recommended) Align RPKI/ROA. Although not required,…
Open a BYOIP ticket
Validate production routing
Confirm whether Option 3 is appropriate
Ensure prerequisites
Open an Option 3 ticket
Configure your router/stack
Operate with heightened monitoring
1
Confirm scope and location
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.
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| 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 Limitations | - No 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.