DataPacket BYOIP Integration Overview
Worth Knowing
Client-panel BYOIP workflow announced 8 October 2026. Exact IPv4/IPv6 family flags, prefix length bounds, provider origin ASN, and fees are not established in the public notice.
Searching for the best IP providers? DataPacket supports customer IP space through its client panel. Customers can request DataPacket-managed prefix announcements or use their own BGP speakers. The managed option lets customers supply prefix parameters, subdivide the space and select subnet delivery arrangements. The alternative retains the customer's BGP speaker as the next hop while routes propagate through DataPacket's network.
Provider Details
| Field | Information |
|---|---|
| Provider Name | DataPacket |
| Website | DataPacket |
| ASN(s) | Not established by the primary source; confirm the required origin ASN with DataPacket before creating ROAs. Customer ASN configuration is supported. |
| Tech Article & Date | DataPacket Q3 2026 summary - client-panel BYOIP workflow announced 8 October 2026 |
| BYOIP Scope | Customer-prefix announcement (DataPacket-managed) and customer-managed BGP sessions through the DataPacket client panel |
| Supported Versions | Confirm exact IPv4 / IPv6 address-family coverage and prefix length limits with DataPacket |
Caveats and Gotchas
- The 8 October 2026 product update announces the client-panel BYOIP workflow; it does not establish exact address-family bounds, minimum/maximum prefix lengths, or a single default origin ASN.
- Onboarding combines client-panel configuration with provider router setup (classified here as semi-automatic/assisted).
- Customer ASN configuration is documented for the customer-managed BGP option, while a universal mandatory ASN ownership requirement is not established.
- Do not assume DataPacket's entire general datacenter footprint has identical BYOIP terms without confirming deployment locations and commercial terms in the client panel.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | Not established in the public release summary; confirm accepted prefix lengths in the DataPacket client panel. |
| Routing Modes | DataPacket-managed prefix announcement (with prefix subdivision and subnet delivery options) or customer BGP speaker retained as next hop. |
| LOA / ROA / IRR | Not specified in the public announcement; confirm required routing authorization objects during panel submission. |
| Fees | Not published in the announcement; confirm any prefix or BGP session fees with DataPacket. |
Step-by-Step BYOIP Process
Step 1
Choose between a DataPacket-managed prefix announcement or announcing routes from your own BGP speaker in the DataPacket client panel.
Step 2
For managed announcements, submit your prefix parameters, desired subdivision and subnet delivery arrangement in the panel.
Step 3
For customer-managed BGP, configure your ASN and BGP speaker parameters so your speaker remains the next hop while routes propagate through DataPacket's network.
Step 4
Coordinate any required routing authorization and router turn-up steps with DataPacket before shifting production traffic.
Related Resources
Published 6 November 2026