Colocation America BYOIP Integration Overview
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Colocation America (Colocation America Inc.) using BGP-based IP announcement and IP transit services. Colocation America publicly states that it will announce customer IP space (i.e., originate or re-announce your prefixes) as long as a valid Letter of Authorization (LOA) is provided, and that it can also provide BGP sessions for customers—positioning BYOIP as a support-led workflow rather than a self-service portal feature. Operationally, onboarding is typically manual / support-assisted: you provide LOA + prefix details, Colocation America verifies ownership/authorization, then implements routing (and, where applicable, IRR/RADB updates) and brings up BGP according to the agreed design.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Colocation America (Colocation America Inc.) |
| Website | Homepage | Colocation Services | IP Transit Services | Example LOA for IP Announcement | Data Center Map (22 locations) | Legal / Terms |
| ASN(s) |
Public ASN associated with Colocation America’s network footprint is commonly referenced as: – AS21769 (Colocation America Corporation / AS-COLOAM). Public route-observation sources commonly show AS35916 (Multacom) as an observed peer/upstream for AS21769 (verification recommended for production designs). Note: BYOIP may be implemented either by having Colocation America originate your prefixes on their ASN (LOA-based), or by establishing BGP sessions for your own routing policy—confirm the intended origin ASN and routing policy during onboarding. |
| Regions Supported |
Colocation America advertises 22 U.S. data center locations across major connectivity hubs/metros, including: – Los Angeles, CA (multiple facilities, including One Wilshire footprint), San Francisco, CA – Chicago, IL (multiple facilities) – New York, NY (60 Hudson / 111 8th Ave footprint + NY metro), New Jersey (Clifton / Secaucus) – Philadelphia, PA (multiple facilities), Boston, MA, Connecticut (Waterbury/Hartford area) – Miami, FL (NAP of the Americas connectivity messaging) BYOIP/BGP capability is tied to these U.S. facilities and the selected connectivity product (colocation + transit, cross-connects, etc.). |
| Support Contact |
Contact & Sales Phone: +1-213-928-6929 | +1-888-505-COLO Email: Sales@ColocationAmerica.com | Support@ColocationAmerica.com |
| Tech Article & Date |
Colocation Services (FAQ includes IP announcement + BGP sessions + IPv6 /64) (no publish date shown). IP Transit Services (no publish date shown). Example Letter of Authorization for Announcing IPs (no publish date shown). Last verified: January 16, 2026. |
| BYOIP Scope |
Colocation America’s BYOIP is primarily delivered as IP announcement (BGP origination/re-origination) plus optional BGP sessions and IP transit for customer-owned prefixes. Public documentation states that, with a valid LOA, Colocation America will announce customer IPs and can provide BGP sessions without extra fees specifically for “announcing your own IP space” / “providing BGP sessions.” The LOA template also indicates the upstream/provider may modify IRR (e.g., RADB) to ensure correct route announcement. |
| Supported Versions | IPv4 and IPv6. Colocation America markets IP transit for both IPv4 and IPv6, and states that colocation plans include a /64 IPv6 allocation at no extra charge (separate from customer-owned BYO prefixes). |
| Supported Services |
– Colocation (single server through rack-scale), with optional BGP bandwidth / direct connectivity options. – IP Transit Services (100 Mbps up to 10 Gbps messaging; carrier-neutral + cross-connect options). – Dedicated servers (may be used as a platform for BGP/transit depending on contract and design). |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | Not publicly standardized on Colocation America’s website for BYO announcements. In practice, global routing constraints typically apply (e.g., IPv4 /24+ and IPv6 /48+ for broad Internet propagation). Confirm acceptable prefix lengths, max-prefix limits, and per-site policy during onboarding. |
| ASN Ownership Required | Not strictly required if Colocation America originates your prefix on their ASN via LOA-based announcement. If you intend to run your own routing policy (your own origin ASN), you must control a public ASN and coordinate BGP session parameters and policy with Colocation America. |
| IRR / Route Objects | The published LOA template indicates the upstream/provider may update IRR (e.g., RADB) to ensure correct route announcement. Ensure you have clean routing registry data (route/route6 objects, as-set where appropriate) aligned with the intended origin and max-length. |
| ROA or LOA | Colocation America explicitly documents LOA as required for announcing customer IP space. RPKI/ROA requirements are not clearly described in the public BYOIP/announcement workflow; however, maintaining correct ROAs is strongly recommended—especially if Colocation America will originate your prefixes (you would authorize the chosen origin ASN and max-length). |
| RIR / Ownership Validation | LOA guidance states your company letterhead and company information should match the information your RIR/LIR has for the address space (e.g., ARIN or another registry), and that additional proof may be required if registration information changed. |
Step-by-Step BYOIP Process
Estimated Setup Time:Typically ranges from 1–10 business days depending on LOA verification speed, RIR/IRR/RPKI hygiene, change-control windows, and whether you are deploying a simple single-site announcement or a multi-site design.Tested By Us:Not yet
Define your BYOIP routing intent
Validate prefix ownership and registration accuracy
Prepare a Letter of Authorization
Submit onboarding request to Colocation America…
Complete routing registry alignment
Bring up BGP session and announce…
Operate and monitor
1
Define your BYOIP routing intent
Define your BYOIP routing intent. Decide whether Colocation America will originate your prefixes (LOA-based announcement on their ASN) or whether you will run your own origin ASN over a BGP session. Clarify desired sites/metros and whether you need multi-site announcements.
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Colocation America states there are no extra fees specifically for announcing your own IP space or for providing BGP sessions (assuming service eligibility and an accepted LOA). Transit ports, bandwidth, cross-connects, and colocation/dedicated-server service charges still apply per quote/contract. |
| Bundled or Standalone | BYOIP is typically delivered as part of a broader connectivity package (colocation + transit and/or dedicated server + transit). Confirm whether your specific plan includes BGP/transit and what physical handoff (cross-connect, blended transit, etc.) is required. |
| Geographic Constraints | Colocation America’s facilities are U.S.-based. International “coverage” is achieved via Internet routing and upstream connectivity rather than non-U.S. POPs. |
| Other Limitations | Requirements (prefix-length acceptance, max-prefix, IRR/RPKI expectations, routing policy features, DDoS options) are not fully standardized in public docs and should be confirmed during onboarding for your selected location and product tier. |