ServerSP BYOIP Integration Overview
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) concepts with ServerSP infrastructure (Bare Metal / Dedicated Servers, VPS, and Virtual Data Center). ServerSP productizes BYOIP as “Bring Your Own IP (BYOIP) – IP Announcement BGP Peering”, enabling customers to use their own IPv4/IPv6 prefixes on ServerSP resources while maintaining IP portability and reputation.
ServerSP’s BYOIP model is Miami-only: prefixes are announced and routed exclusively through ServerSP’s Miami, Florida data center, but with global reachability via multiple upstream providers. ServerSP supports customers that either (a) bring their own ASN and announce prefixes using BGP, or (b) do not have an ASN and have ServerSP originate the routes under AS214456 (provider-origin model).
In practice, BYOIP with ServerSP is realized in three common patterns:
1. Customer-owned prefixes advertised using the customer’s ASN (BGP peering / classic BYOIP);
2. Customer-owned prefixes originated via ServerSP ASN (AS214456) when the customer does not have an ASN (sponsored-origin / provider-origin model);
3. Leased IPv4 resources (e.g., IPXO-leased blocks) announced through ServerSP once delegated correctly and accompanied by the required authorization artifacts (LOA + RPKI/IRR validity).
Provider Details
| Field | Information |
|---|---|
| Provider Name | ServerSP (BYOIP – IP Announcement BGP Peering) |
| Website | BYOIP – Bring Your Own IP | Miami Data Center | About Us (Legal / Company) | Contact / Support | Terms of Service (AUP / SLA) |
| Legal Entity | ServerSP LLC (Wyoming, USA). ServerSP states services are provided through its U.S. entity, with global operations. |
| ASN(s) |
AS214456 (SERVERSP-AS). ServerSP states customers may announce using their own ASN or have ServerSP announce under AS214456 when the customer lacks an ASN. PeeringDB lists SERVERSP-AS as a global-scope network with an open peering policy and a Looking Glass URL. |
| BYOIP Location / PoP | Miami, Florida (USA). ServerSP states all BYOIP and BGP announcement infrastructure is located in Miami and routes are announced/routed exclusively via this data center. |
| Data Center / Facility |
ServerSP states its infrastructure is hosted in Digital Realty MI1 (Downtown Miami). Address listed by ServerSP: 36 NE 2nd Street, Miami, FL 33132. ServerSP also publishes facility posture statements (e.g., Tier 1 provider connectivity, hurricane resilience) and compliance/security claims. |
| Looking Glass / Network Test |
Looking Glass: lg.serversp.com Network test endpoints published by ServerSP: – IPv4: 103.230.142.1– IPv6: 2a14:7581:c01:1::1
|
| Regions Supported |
Provisioning: United States (Miami PoP). Reachability: Global routing via multiple upstream providers (ServerSP describes “global BGP connectivity” and multiple upstreams), but the control-plane / origination is Miami-only. |
| Supported Services | ServerSP states BYOIP ranges can be used across: Bare Metal / Dedicated Servers, VPS, and Virtual Data Center. BYOIP prefixes can be routed to any ServerSP instance. |
| Support Contact |
Contact / Support (24/7 technical support) |
Submit Ticket (Client Portal) ServerSP also publishes a support-response target (infra issues handled within ~30 minutes) and states services are unmanaged (client responsible for management). |
| SLA (Published) | ServerSP publishes a 99.9% monthly uptime target for network and power, with a credit schedule in its Terms of Service. |
| Tech Article(s) ; Date |
BYOIP – Bring Your Own IP — BYOIP scope, ASN options, validation requirements, activation timeline, IPXO-leased block support. Miami Data Center — facility location, MI1 reference, address, network posture notes. PeeringDB: AS214456 (SERVERSP-AS) — peering policy, LG, scope metadata. |
Technical Requirements
| Requirement | Details |
|---|---|
| IP Version Support | IPv4 and IPv6 are supported for BYOIP. ServerSP states it will review ownership and routing-validity before announcement. |
| Prefix Size |
ServerSP does not publish a minimum prefix size on the BYOIP page. Industry baseline for global routability is typically /24 (IPv4) and /48 (IPv6); confirm exact acceptance and filtering with ServerSP during onboarding. |
| ASN Ownership Required |
Not strictly required. ServerSP states that if you don’t have an ASN, ServerSP can announce your prefixes using AS214456. If you do have your own ASN, ServerSP states you can announce using your ASN (classic BYOIP model). |
| IRR / Route Objects | ServerSP states it reviews IRR data as part of ownership/routing validation. You should ensure IRR objects correctly reflect prefix-to-origin authorization (your ASN or ServerSP ASN, depending on your model). |
| RPKI (ROA) | ServerSP states the IP space must be properly registered in RPKI. Practically, that means maintaining valid ROAs consistent with the intended origin ASN (your ASN or AS214456). |
| LOA (Letter of Authorization) | Required. ServerSP states BYOIP requires a valid LOA and that activation occurs after ownership validation + LOA receipt. |
| Routing Scope Constraint | Miami-only / ServerSP-only. ServerSP states BYOIP is available only within ServerSP’s network and prefixes are announced and routed exclusively through the Miami data center. |
| Abuse / Reputation Controls | ServerSP publishes Acceptable Use constraints (e.g., spam/phishing, malicious activity prohibitions) and states it applies security filtering on email ports 25/465/587 to protect network reputation (exceptions require support review). |
Step-by-Step BYOIP Process
Estimated Setup Time:ServerSP states BYOIP is typically activated within 1–2 business days after ownership validation and receipt of the required LOA.Tested By Us:Not yet
A) Customer-owned prefixes with customer ASN (classic BYOIP / BGP peering)
Provision or identify the ServerSP service…
Prepare the onboarding packet
prefix list (IPv4/IPv6), your public ASN, and intended origin policy. Ensure your IRR route objects and RPKI ROAs are consistent with your ASN as origin.
Provide a valid LOA authorizing ServerSP…
Coordinate BGP parameters with ServerSP
Announce your prefixes and validate propagation
Operationalize
monitor BGP session health and prefix visibility, document your intended origin/ROA/IRR state, and use ServerSP support for changes (add/remove prefixes, routing adjustments, withdrawal).
Open a BYOIP onboarding request with…
Provide the prefix list
After activation, assign the IPs to…
If you later obtain your own…
Lease the IPv4 block from IPXO…
Use IPXO’s delegated RPKI capabilities
Choose origin model
announce using your ASN (if you have one) or have ServerSP originate via AS214456; align IRR and ROA maximum-length/origin accordingly to avoid invalid announcements.
Once active, deploy the leased addresses…
1
Provision or identify the ServerSP service…
Provision or identify the ServerSP service where the addresses will be used (Bare Metal, VPS, or Virtual Data Center) and open a technical support request to start BYOIP onboarding.
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| Fees | ServerSP does not publish a standalone BYOIP price list on the BYOIP page; onboarding is support-assisted and typically commercialized as part of ServerSP infrastructure services (Dedicated/Bare Metal, VPS, VDC). Use the ServerSP contact/support channel for pricing and feasibility. |
| BYOIP Geography | Miami-only. BYOIP prefixes are announced and routed exclusively through ServerSP’s Miami data center; BYOIP is not available “outside ServerSP’s infrastructure.” |
| Operational Model | Semi-manual onboarding. ServerSP validates RPKI/IRR + LOA, then activates configurations (stated 1–2 business days after validation/LOA). Day-2 control is via BGP (customer-origin model) and/or support requests (provider-origin model). |
| SLA / Availability | ServerSP publishes a 99.9% monthly uptime target for network/power (credit schedule in ToS). This does not eliminate your responsibility to design redundancy (multi-server, multi-region, backups). |
| AUP / Abuse Limitations | ServerSP ToS includes strong prohibitions against spam/phishing, malicious activity, botnets, DDoS participation, proxies/TOR relays (among others). ServerSP also states it applies filtering on outbound email ports 25/465/587 to protect reputation; approvals require review. |