Skip to content
Fresh IPv4 news just dropped — 🎉 see what you’re missing

Vultr Prefix Onboarding: Plan Beyond the Approval Email

Marek Dvořák Marek Dvořák November 18, 2026
6 min read

Conceptual approval card beside an unfinished connection to a service, showing why prefix approval alone does not establish working traffic

Vultr prefix onboarding has more than one completion point. A request can pass review while another dependency still prevents the intended service from working. For a team bringing a leased IPv4 block, the useful question is not just “When will the prefix be approved?” It is “Which milestone is complete, who owns the next one, and what can we test now?”

This article helps you plan that handover. The provider details were checked on November 15, 2026. They do not establish acceptance of a particular lease or a completion commitment for your account.

Build a milestone plan, not one activation date

Vultr’s prefix-onboarding procedure describes prefix checks, registry-contact confirmation, further review and transit-filter updates. It also identifies a separate support step for Bare Metal server filters.1 Approval is therefore one dependency in a larger handover.

Use a shared record with these checkpoints:

MilestoneEvidence to requestDecision it supports
Proposed arrangement acceptedConfirmation of the exact prefix, product and origin modelWhether this block fits the destination
Holder and contact verification completeThe required registry contact has confirmed the requestWhether the authorization review can proceed
Account and server readyAccepted prefix and the intended server included in the relevant configurationWhether the chosen endpoint can participate
Routing dependencies readyProvider confirmation of the relevant filters and intended announcementWhether a controlled traffic test is useful
Workload acceptedRecorded application tests from representative source networksWhether the team can move production traffic

This table is a planning aid, not a representation of Vultr’s console states. Assign a named owner and a last-checked time to each row. An unanswered dependency remains open even when a different row has passed.

For example, consider a hypothetical hosting team with a working service elsewhere and a planned Vultr deployment. The account accepts the prefix, but the chosen endpoint has not been confirmed. The team can finish application preparation and evidence collection. It should keep the working service until it can test the intended destination. This avoids treating an administrative message as permission to retire the old path.

Confirm the public origin before changing records

A private ASN used in a customer BGP session can differ from the public origin used for authorization. The onboarding guide identifies AS20473 for Vultr’s private-ASN arrangement. Confirm the chosen model before the holder publishes records; a sample’s session ASN is not the answer by itself.

Write down three separate values: the customer session ASN, the provider neighbor ASN and the intended public origin. If two happen to be the same, record that explicitly. Ask which value the provider expects in each authorization rather than copying one number into every field. The ASN reference explains the underlying distinction.

For leased space, also identify who controls the registry and RPKI changes. The person operating the server may not have authority to publish them. A useful handover includes the requested prefix-origin pair, the approval owner and a way to correct a rejected request. The ROA workflow covers publication and validation; this article focuses on coordination before the change.

Find the dependency behind a timing estimate

Vultr’s onboarding guide describes 24–48 hours of further checks after contact confirmation, plus a distinct transit-filter process. It notes that manual filter changes may exceed 48 hours. These figures describe parts of its workflow, not a guaranteed end-to-end activation time.

Ask for the starting event behind any estimate. “After submission,” “after the registry contact confirms,” and “after corrected records become visible” describe different starting points. A change to the prefix, product or origin can introduce new review work. Ask the responsible party whether an earlier estimate still applies.

When a milestone stalls, make the next question specific:

  • Contact confirmation: who receives the verification request, and has that person completed it?
  • Authorization review: which prefix-origin pair was checked, and what exact record needs correction?
  • Server readiness: does the pending task concern the account or the intended machine?
  • Transit acceptance: which filter change is outstanding, and what evidence would show it has completed?
  • Workload failure: can the provider reproduce the same destination, protocol and time window?

Record the answer beside the milestone instead of repeatedly asking for a new overall date. This gives the address holder, provider and application team different tasks they can act on.

Match the plan to the actual server product

Vultr’s BGP configuration documentation describes different VM and Bare Metal peer settings, an existing-server reboot requirement through its control panel, and a minimum /24 for its IPv4 BGP workflow. Use the configuration supplied for the specific subscription rather than a copied example.

Before scheduling a change, confirm the product, machine identifiers and access to recovery tools. If a restart or network change is required, include its operational impact in the plan. Decide who can reach the server if the normal application path fails. These are preparation questions, not evidence that an arbitrary VPS or externally leased block will be approved.

A small address requirement deserves a separate decision. If the workload needs only a few additional public IPs, compare the hosting provider’s additional-address product with importing a full prefix. The IPv4 without an ASN article examines that purchasing choice. Once the delivery model is settled, the BYOIP overview provides the broader platform context.

Close the handover with observations and an exit plan

Define the acceptance test before switching production. Include the actual application protocol, expected origin, source networks that matter to users and a working comparison. A session can be established without showing that the service is reachable from every relevant network. Use the announcement runbook for technical checks and escalation evidence.

Keep two decisions separate: whether the network is ready to test, and whether the commercial arrangement meets the agreed acceptance criteria. A failed observation should lead to a specific investigation; it does not automatically establish a right to replacement, a refund or a service credit. Confirm the applicable conditions with the parties supplying the addresses and connectivity.

Finally, agree who will remove stale provider-created objects and temporary permissions when the arrangement ends. Avoid leaving that work to a future operator who cannot tell which entries are still needed. Do not remove records supporting a live service just because a new portal request is complete.

Before requesting an IPv4 lease for a Vultr deployment, prepare the intended product, origin model, verification contact and acceptance milestones. That gives both suppliers a concrete requirement to assess and gives your team a usable basis for the change window.


  1. Source: Vultr IP Prefix Onboarding Process and Timeline, checked November 15, 2026. ↩︎

Frequently asked questions

How long does Vultr prefix onboarding take?
There is no single completion time established for your deployment. Ask Vultr which milestone is pending and what starts its estimate. The provider’s published stage estimates are not a guaranteed total activation time.
Which origin should a ROA authorize when using a Vultr private ASN?
Use the confirmed public origin for the specific arrangement. Vultr’s onboarding guide identifies AS20473 for its private-ASN model; do not substitute a sample’s private session ASN for the intended public origin.
Does a prefix appearing in my account mean it is ready for production?
No. Treat account acceptance, server eligibility, transit-filter readiness, external route observations and workload tests as separate milestones. Keep a working alternative until the agreed acceptance checks pass.
Will Vultr accept any leased prefix?
Do not assume that generic BGP support establishes acceptance. Confirm the exact prefix, holder permission, registry-contact verification, product and origin model with Vultr and the address holder before ordering.