IPTP Networks BYOIP Integration Overview
Location
This page summarizes how IPTP Networks positions “Bring Your Own IP (BYOIP)” for customers that want to keep using their own public IPv4/IPv6 address space while consuming IPTP’s network services. Unlike hyperscaler BYOIP (where the cloud provider originates your prefix inside a cloud region), IPTP’s BYOIP messaging is centered on network delivery and routing: (1) BYOIP Content Delivery, where your company’s IP blocks are used across IPTP’s global CDN edge and advertised via Anycast, and (2) IP Transit / Global routing, where you can announce your prefixes and reach the full Internet routing table via IPTP’s backbone and upstream connectivity. The same “IP Address Services” portfolio also covers IPv4 acquisition/transfer, IPv4 leasing, IPv6 allocations / PI assignments, plus operational add-ons such as RPKI ROAs, WHOIS object management, reverse DNS, and abuse/reputation handling.
Provider Details
| Field | Information |
|---|---|
| Provider Name | IPTP Networks (IPTP Networks Group of Companies) |
| Website | IP Address Services (IPv4/IPv6) — includes “BYOIP Content Delivery” and BYOIP FAQ | IP Transit — BGP full table, global routing | About IPTP Networks (ASNs, global footprint) | Contacts (global offices) | Privacy Notice (holding company / data controller details) |
| ASN(s) |
IPTP publicly references multiple ASNs across its backbone/operations. On its “About Us” and “IP Transit” pages it lists: – AS3356 (referenced as “Tier-1 single-homed network”) – Backbone / ISP ASNs: AS41095, AS263681, AS51601, AS140951, AS135993 Note: for BYOIP routing/Anycast, confirm with IPTP which origin ASN(s) will be used for your specific prefix/service, to ensure ROAs and routing objects are correct. |
| Regions Supported | IPTP describes a global footprint (examples cited on its site): 228 Points of Presence worldwide and presence across 37 countries (64 cities). For “BYOIP Content Delivery” specifically, IPTP states you can use your own IP addresses across 200+ global edge locations on its CDN. Where an explicit country-by-country BYOIP list is required for compliance, confirm coverage with IPTP during design (edge/PoP placement and any in-country constraints). |
| Support Contact | Contacts / regional offices | Help Center (service request / live support references) | Commercial onboarding typically begins via Request a Quote. |
| Tech Article & Date |
Primary technical references are IPTP product pages (no clear publication date is shown on-page): – IP Address Services (IPv4/IPv6) — includes BYOIP Content Delivery + BYOIP FAQ – IP Transit — full BGP table, global routing + upstream notes Legal/identity reference (for holding / data controller): Privacy Notice. |
| BYOIP Scope |
IPTP’s BYOIP messaging is focused on network delivery rather than “attach prefix to VMs” cloud BYOIP: 1) BYOIP Content Delivery (CDN): Use your company’s IP addresses across IPTP’s 200+ global edge locations; IPTP describes this as announcing your IP blocks from its edge via Anycast to preserve portability and “brand identity.” 2) IP Transit (BGP routing): Traditional BGP-based transit where customers can announce their prefixes and receive a full BGP table, with IPTP noting upstream connectivity and peering relationships as part of its transit architecture. 3) IP resource enablement: IPv4 purchase/transfer, IPv4 leasing, IPv6 allocations/PI assignments, plus operational lifecycle tooling (RPKI, WHOIS, rDNS, reputation monitoring). |
| Supported Versions | The IP Address Services portfolio explicitly covers IPv4, IPv6, and ASN services. For BYOIP Content Delivery, IPTP states “use your own IP addresses” but does not explicitly separate IPv4 vs IPv6 in the BYOIP snippet; validate dual-stack (IPv4/IPv6) feasibility and prefix sizing with IPTP for your intended CDN/Anycast design. |
| Supported Services |
BYOIP-related capabilities appear across multiple IPTP offerings: – CDN / edge delivery: BYOIP Content Delivery (Anycast at the edge). – Connectivity: IP Transit (BGP full table) for announcing your prefixes and reaching the Internet. – IP operations: Managed RPKI (ROAs), WHOIS object management, reverse DNS, and reputation/abuse handling to support long-lived BYOIP use. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix / Block Size |
For BYOIP CDN (Anycast) and IP Transit, IPTP’s BYOIP sections do not publish an explicit minimum prefix size on the referenced page; confirm requirements during onboarding (design depends on global routability, Anycast topology, and ROA policy). For IPv6 services, IPTP’s IP Address Services page describes standard IPv6 allocations (e.g., /32 with expansion) and IPv6 PI assignments (e.g., /48 to /36) as part of its IPv6 resource portfolio. |
| Customer ASN Ownership | For IP Transit, customers commonly use their own ASN for BGP announcements; IPTP markets full-table BGP transit and global routing connectivity. For BYOIP CDN (Anycast), validate whether IPTP originates your prefix under an IPTP ASN, supports customer-origin announcements, or offers both models; this impacts ROA/IRR configuration and operational responsibility. |
| RPKI (ROAs) | IPTP explicitly offers managed RPKI as part of its lifecycle tooling, describing ROA creation “in minutes” via web or API and automated handling to reduce operational overhead. In practice, for BYOIP you should expect to maintain ROAs authorizing the final origin ASN(s) used for your route announcements. |
| IRR / Routing Objects | IPTP includes WHOIS / routing object maintenance and cross-registry record consistency as a managed function. For BYOIP, ensure route/route6 and related objects align with the origin ASN model chosen for Anycast/CDN and/or Transit. |
| Reverse DNS (rDNS) | IPTP describes reverse DNS as a core operational requirement and offers delegation/hosted management, with PTR record setup typically referenced in a 24–48 hour window and update mechanisms via portal/API (per the same IP services page). |
| Abuse / Reputation Operations | IPTP’s IP leasing/services messaging includes reputation screening and a 24/7 abuse desk with rapid response expectations, plus ongoing blacklist monitoring and delisting assistance. For BYOIP, clarify which parties (customer vs IPTP) handle abuse desk interactions and delisting in each operating model (Transit vs CDN). |
Step-by-Step BYOIP Process
Estimated Setup Time: IPTP’s IP Address Services page positions onboarding as fast (it uses a “Go Live” message indicating you can be online in ~48 hours), but real BYOIP timelines depend on prefix validation, ROA/IRR updates, Anycast design, and acceptance testing.
Tested By Us: Not yet
A) BYOIP Content Delivery (CDN / Anycast)
B) BYOIP via IP Transit (BGP routing)
References: IP Address Services (includes BYOIP Content Delivery + BYOIP FAQ), IP Transit, About IPTP Networks, Contacts, Privacy Notice.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Public BYOIP pricing is not published on the referenced IPTP pages. Commercial enablement is positioned via Request a Quote flows. Expect pricing to vary by service (CDN edge delivery vs IP Transit), edge footprint, commit levels/ports, and operational add-ons (RPKI/WHOIS/rDNS/reputation services). |
| Bundled or Standalone | BYOIP appears as an enabling capability across multiple IPTP services (CDN delivery, IP Transit, IP address lifecycle tooling). In practice, you should scope BYOIP as part of a solution bundle aligned to your use case (delivery vs routing vs address acquisition) rather than as a single feature toggle. |
| Other Limitations | Key limitations are typically design-driven rather than purely contractual: global Anycast behavior, geolocation expectations, required minimum prefix sizes, ROA/IRR correctness, and abuse/reputation responsibilities. Validate (1) minimum routable block size per service, (2) origin ASN model, and (3) the operational split of responsibilities (customer vs IPTP) during onboarding. |
Automation & Developer Access
Abuse & Reputation Management
Related Resources
IPTP Networks Homepage
IP Address Services (IPv4/IPv6) — BYOIP Content Delivery section + BYOIP FAQ
IP Transit
About IPTP Networks
Contacts
Help Center
Request a Quote
Privacy Notice
Legal Docs and Policies