CONTROL
Prefix control
Provide evidence that your organization controls the prefix or is authorized to use it.
Status
Evidence required
BYOIP Program
Import your IPv4 blocks on AS210699
BYOIP (Bring Your Own IP) lets you keep your existing IP ranges while routing them on the Infrawire network with security, resilience and full technical assistance.
The exact documents depend on the registry, the prefix holder and the delivery architecture. Eligibility is confirmed by the network team.
Illustrative workflow
Documentation prefix
203.0.113.0/24
Prefix control
- CONTROL
- Prefix control
- To validate
- LOA
- Authorization
- Required depending on the case
- IRR
- Routing objects
- To verify
- ROA
- RPKI authorization
- To verify
- ORIGIN
- Origin ASN
- AS210699 after validation
Client prefix
Validation
AS210699 edge
Target service
Keep your addresses
Keep your current addresses to avoid heavy changes and preserve the same online identity.
Publish your addresses
We put your addresses online on our network so they can be used easily across your services.
Continuous support
A team follows your service daily and helps quickly whenever you need it.
Eligibility file
Prepare your prefix import
A complete, consistent file lets the network team verify the announcement path without making assumptions about your resources.
LOA
LOA
Prepare a letter of authorization matching the holder, prefix and intended routing.
Status
Case-dependent
IRR
IRR
Keep route and maintainer objects consistent with the selected origin.
Status
Must be consistent
ROA
ROA / RPKI
Publish an authorization consistent with the origin ASN retained after validation.
Status
Must be consistent
POLICY
POLICY
Describe target services, sites, routing constraints and any custom policy.
Status
To be defined
The exact documents depend on the registry, the prefix holder and the delivery architecture. Eligibility is confirmed by the network team.
Submit my prefix detailsDeployment path
From qualification to supervised routing
Each phase removes an operational uncertainty before the prefix is announced.
01
Qualification
We identify the prefix, holder, target services, sites and expected routing model.
02
Technical validation
LOA, IRR, ROA/RPKI, compatibility and routing policy are reviewed together.
03
Network integration
We prepare announcement on AS210699, security filters and the right distribution strategy for your constraints.
04
Activation and supervision
Your prefix is announced and continuously monitored, with guidance for future addressing changes.
Delivery targets
Route your prefix to the right Infrawire service
One validated prefix can support several infrastructure models. The final path depends on the service, location and technical design.
VPS
VPS
Route BYOIP on your virtual instances to keep your historical IPs without changing usage.
DEDICATED
Dedicated Servers
Announce your blocks on bare metal machines with filtering and network controls managed by our NOC.
Infrawire edge · AS210699
Compatibility and availability are confirmed for each service and location during technical validation.
Operating model
Clear control on both sides of the route
BYOIP does not transfer ownership of your addresses. Responsibilities remain explicit throughout the integration.
PREFIX OWNER
You retain control
You remain responsible for the resources and business intent attached to the prefix.
- Ownership or authorization to use the prefix
- Addressing plan and target services
- Required reverse DNS changes
- Administrative information under your control
NETWORK OPERATOR
Infrawire operates the integration
The network team implements the accepted routing design on Infrawire infrastructure.
- Technical eligibility review
- Announcement preparation through AS210699
- Applicable filters and delivery parameters
- Operational supervision and routing assistance
Infrawire does not become the owner of the prefix and cannot replace obligations belonging to its holder.
Network identity
Edit your reverse DNS
Keep PTR records aligned with your services while retaining a stable addressing identity during infrastructure changes.
- Keep control of your IP address identity across your services.
- Set reverse DNS entries aligned with your business domains.
- Improve trust around your application and email flows.
Reverse DNS supports technical consistency but does not by itself guarantee email deliverability or reputation.
Operating scenarios
BYOIP use cases
BYOIP fits advanced operations needs: migration, multi-site and service continuity.
MIGRATE
Seamless migration
Keep the same public IPs during infrastructure migrations to avoid application interruptions.
Confirm destination compatibility before migration.
DR
DR and multi-site
Distribute your block across multiple Infrawire environments to improve continuity and recovery.
Validate announcement policy and failover design.
IDENTITY
Compliance and reputation
Keep your IP reputation history, reverse DNS and existing access rules.
Keep registry and reverse DNS data current.
Technical operation
Included guarantees
Beyond routing, we provide secure operations and long-term technical support.
FILTER
Protection and filtering
Abuse filtering and network security rules adapted to your addressing plan.
NOC
24/7 NOC supervision
Proactive monitoring of BGP announcements with continuous operational assistance.
ROUTE
High-performance backbone
Routing through the Infrawire network with an integration adapted to the selected service.
CHANGE
Routing changes
Technical assistance for accepted routing and reverse DNS changes over time.
Filtering, protection and delivery options depend on the accepted architecture and service.
Network resources
Continue designing your routing architecture
Use the related network services and observation tools to prepare the right delivery model.
BGP
Establish BGP sessions or IP transit for an advanced routing architecture.
Looking Glass
Observe AS210699 routes and reachability from the Infrawire network.
IPv4 prefixes
Compare BYOIP with Infrawire-provided IPv4 prefixes.
Frequently asked questions
Technical answers before submitting a prefix for qualification.
BYOIP routes addresses that you already control. Renting a prefix uses addresses provided by Infrawire. A BGP session is a routing mechanism that may form part of a BYOIP architecture after validation.