ASN sponsorship explained: skip the €1,000 LIR fee
Direct ASN acquisition demands a one-time fee for LIR status, leaving sponsorship as the only realistic path for most entities. You need a specific dual transit architecture to satisfy RIPE NCC policy, valid maintainer objects to control your resources, and Idenfy document photos that meet rigid standards or face instant rejection.
Becoming a Local Internet Registry to bypass sponsors costs a one-time fee according to community discussions on the 2025 charging scheme, a barrier that forces reliance on established sponsors like Lagrange Cloud. Payment alone won't cut it. You must prove connectivity to two distinct upstream providers; single-homed configurations get rejected immediately. ServPerso data confirms applicants must submit direct AS numbers and contact emails for verification, with RIPE often contacting upstream operators directly to validate the transit relationship.
Technical execution requires submitting high-resolution identity photos through Idenfy with zero data masking. You also need to configure maintainer objects correctly in the registry database to authorize allocations like the standard /44 IPv6 prefix. Neglect infrastructure maintenance, such as keeping a virtual machine active in the RIPE region for a full year, and the sponsorship agreement terminates, taking your autonomous system number with it.
The Strategic Role of ASN Sponsorship in RIPE NCC Resource Management
ASN Sponsorship and the /44 Allocation Workflow
ASN sponsorship acts as a contractual workaround to direct LIR membership, letting organizations skip high entry fees while securing independent routing identity. In the RIPE NCC region, you need a contract with the registry, either via direct membership or a sponsoring Local Internet Registry. This route dodges the €1,000 sign-up fee and €1,800/year annual costs of becoming a LIR. The workflow starts with signing a sponsorship agreement and settling the bill, followed immediately by allocating a /44 IPv6 block. This prefix size isn't arbitrary; it ensures you have enough IPv6 space to announce before RIPE even sees the request.
InterLIR handles the heavy lifting, submitting the request to RIPE only after Idenfy validates your ID documents. This step locks down your legal identity, a mandatory gatekeeper distinct from the technical justifications other regions demand. Once RIPE confirms the exchange, you get your ASN. But there's a catch: the sponsor can terminate the agreement if you drop active service elements, like a dual-transit virtual machine, within the RIPE zone. You get the resource portability, but the sponsorship relationship demands continuous contractual compliance.
SERVPERSO Sponsorship Costs Versus Direct RIPE LIR Fees
Direct LIR membership hits you with a €1,000 sign-up fee plus €1,800/year, making sponsorship a lifeline for smaller networks. This financial barrier pushes operators toward intermediaries rather than direct registry contracts. ARIN takes a different approach, using a Registration Services Agreement model focused on technical justification instead of steep fixed fees. Choosing sponsorship shifts the administrative burden; you skip complex membership audits but inherit strict provider agreements.
| Feature | Direct RIPE LIR | SERVPERSO Sponsorship |
|---|---|---|
| Upfront Cost | €1,000 sign-up fee | Minimal setup charge |
| Annual Recurrence | €1,800/year | Subscription based |
| Contract Type | Direct with RIPE NCC | Third-party agreement |
| Resource Control | Full independent authority | Dependent on sponsor |
Going direct grants full autonomy over ASN delivery and database objects. Yet for entities needing just one autonomous system, the cost of independence often outweighs the benefit. You trade long-term asset portability for immediate savings; while resources stay portable, the initial sponsor dependency sticks. The market for sponsoring LIR services exists because direct acquisition remains prohibitive for small players. Picking the right sponsor lets you access global routing without the overhead of full registry membership.
Validating Legal Entities for RIPE NCC Resource Requests
Legal entity validation demands strict Idenfy verification before any resource allocation. Without direct membership, you need a sponsoring LIR to file requests on your behalf, bypassing the prohibitive €1,800/year direct membership fee. The workflow requires high-resolution photos of national IDs or passports with zero masking on critical data fields. Companies must provide official registration documents proving the manager's identity alongside a government link for existence confirmation.
You must maintain an active exchange with RIPE until final approval arrives, ensuring no unauthorized allocations slip through. Speed often clashes with compliance here; rushing document submission triggers rejection over minor formatting errors like cropped edges. Verify your sponsoring LIR status before billing to prevent service cancellation.
- Submit clear ID document photos showing all four edges.
- Provide company registration papers with manager names listed.
- Maintain active sponsorship agreement throughout the resource lifecycle.
- Ensure photos include both flash and non-flash variants for each document side.
- Avoid any masking of MRZ tapes or ID numbers during photo capture.
InterLIR simplifies this by managing all RIPE communications and document exchanges internally. This approach eliminates administrative rejection risks while securing your autonomous system identity efficiently.
BGP Multihoming and Dual Transit Architecture Requirements
Defining Dual Transit and Direct Upstream Requirements for RIPE ASNs
Dual transit requires a direct physical or logical link to two distinct upstream providers. Relying on an intermediary's peer doesn't count. Listing your upstream provider's supplier fails validation because the AS path must originate directly from your edge to satisfy RIPE NCC policy. Consequently, a single homed architecture triggers automatic rejection, regardless of your future expansion plans.
The registry verifies this by emailing your declared transit operators to confirm direct sessions. Unlike regions that have lifted strict justification hurdles, this zone maintains rigorous checks on multihoming topology before allocation.
| Configuration Type | Valid for ASN Request | Reason |
|---|---|---|
| Direct Link to Two ISPs | Yes | Meets redundancy criteria |
| Upstream's Upstream | No | Lacks direct peering session |
| Single Transit Provider | No | Automatic rejection trigger |
Virtual circuits must terminate as independent sessions, not shared reseller paths. InterLIR offers compliant dual-transit packages that satisfy these architectural demands immediately. Trying to bypass this with a single connection wastes administrative cycles and delays deployment. Securing valid upstream relationships remains the non-negotiable foundation for any successful ASN acquisition strategy in this region.
Deploying VM-Based Presence Proof for Non-RIPE Legal Entities
Operators with legal entities outside the RIPE NCC zone must technically detail their geographic presence. This targets applicants lacking a physical office in Europe or Russia, mandating a verifiable digital footprint within the region. For entities outside the zone, ordering a Virtual Machine from the service provider is required to technically detail presence in the area. Unlike physical servers, which demand complex logistics and hardware maintenance, a cloud-based instance offers immediate deployment for presence proof.
The rule is strict: the provisioned VM must remain active throughout the entire ASN lifetime. Fail to maintain this subscription, and the sponsorship agreement terminates as the resource justification vanishes.
| Feature | Physical Server | InterLIR VM Solution |
|---|---|---|
| Deployment Speed | Weeks | Minutes |
| Maintenance | High | Zero |
| Compliance Status | Valid if local | Valid globally |
| Risk Profile | Hardware failure | Contractual lapse |
Cost efficiency clashes with administrative continuity; while the VM costs less than real estate, cancelling it destroys ASN validity instantly. Most operators miss that geographic presence isn't a one-time check but a continuous state requirement. The VM acts as both a technical asset and a permanent compliance anchor. InterLIR ensures these instances integrate smoothly with required BGP sessions, securing the multihoming architecture against policy audits.
Risks of Terminated Sponsorship from Lapsed Dual Transit Subscriptions
If you use dual transit services to meet multihoming requirements, maintain the subscription for one year or risk cancellation. InterLIR enforces this because the sponsorship agreement relies on continuous service validation to satisfy registry rules. Let your subscription to our dual transit package expire prematurely, and the sponsorship arrangement faces potential cancellation.
The verification mechanism involves direct email correspondence between the RIPE registry and your declared upstream providers to confirm active sessions.
| Failure Scenario | Consequence |
|---|---|
| Service interruption under 12 months | Sponsorship may be canceled |
| Upstream denies relationship | Application rejection |
| Single active provider | Automatic disqualification |
Changing providers requires meticulous coordination to avoid gaps in AS path visibility. If you switch upstreams, edit the ASN object in the database while ensuring two distinct connections remain active. Maintaining these subscriptions keeps your network compliant with the contractual agreement required for requesting an AS number. Consistent uptime for your VM and transit links isn't optional; it's the core proof of your network's viability.
Executing the ASN Application via Maintainer Objects and Identity Validation
SERVPERSO Maintainer Object Requirements and MNT-BY Syntax
Operators create a maintainer object to secure specific rights for managing AS resources inside the RIPE database. A RIPE NCC account serves as the mandatory first step before any technical provisioning begins. SERVPERSO submissions demand that SERVPERSO-MNT sits strictly within the `mnt-by` parameter instead of `mnt-ref`. Existing objects become unusable without this exact syntax, forcing the creation of entirely new entries. Direct membership carries heavy costs, so accurate object creation remains vital for cost-efficient sponsorship paths. Precise syntax prevents wasted effort during the review period where staff might request extra details. Adhering to these parameter requirements ensures immediate acceptance of the object for use.
Identity Document Photography Standards for Idenfy Validation
Capturing two distinct photos of every document side starts the validation path, using one shot with flash and another without. The Idenfy system rejects scans outright, demanding original camera captures that show all four edges clearly. Images must stay uncropped, and no parts like the MRZ tape or ID numbers can remain masked. Physical photo realism defines the protocol, accepting only raw photos rather than digital scans. Some platforms allow redacted files, yet this process mandates full visibility for proper verification. Clear, unedited imagery satisfies the validation criteria effectively.
Applicants must also provide legal company registration papers listing a manager's name plus a verifiable government link. Minors under eighteen need additional authorization letters paired with a guardian's identity proof. Following these specific photographic guidelines simplifies the path to becoming a recognized network operator.
Minor Applicant Authorization and Legal Entity Documentation
Applicants under 18 years old must submit a parent's identity document alongside the letter of authorization. This legal guardian signs the sponsorship agreement to validate the request completely. These steps satisfy strict identity validation protocols within the RIPE region. Legal entities supply official registration papers confirming the manager's name as well. Operators verify that government links stay accessible to prove company existence instantly. Such documents form necessary components of the processing workflow.
The contractual requirement for a signed agreement differs notably from regions relying solely on technical justification. Certain jurisdictions focus on infrastructure proof, but the RIPE NCC region emphasizes this legal entity documentation as a primary requirement. Complete paperwork ensures the application proceeds based on technical readiness rather than getting stuck in administrative loops. Providing every requested file upfront avoids delays caused by missing information or unclear ownership structures.
Long-term Sponsorship Retention and Administrative Compliance
Cold Storage Duration and Invoice Payment Windows
Administrative continuity depends on strict document retention and precise invoice settlement. Identity documentation sits in cold storage for the entire sponsorship duration to identify the user throughout the life of the sponsorship. This archival method preserves the link between resource holder and sponsor without demanding repeated submission of sensitive materials. Payment discipline holds equal weight for maintaining active status. The first invoice requires settlement within 5 days to prevent service cancellation. A tighter window than standard billing cycles applies here. Subsequent invoices must clear within 10 work days to avoid administrative suspension. Accepted payment methods include Paypal or SEPA bank transfers, with specifics listed on the final invoice. Missing these deadlines interrupts the sponsorship agreement regardless of ASN technical stability. Operators should treat these timelines with the same urgency as BGP session maintenance. Technical configurations like dual transit guarantee routing availability. Timely payment secures the legal right to announce those routes. Neglecting the five-day initial window invalidates the entire application effort. Restarting the registration process becomes the only option.
Editing ASN Objects for Upstream Changes in RIPE Database
Modifying upstream providers post-delivery demands editing the specific ASN object directly inside the RIPE database. Network operators often adjust transit relationships to optimize latency or cut costs. Administrative procedure remains straightforward when policy constraints are met. Applicants must maintain at least two upstreams to stay in good standing with RIPE NCC policy. Dual-transit requirements prevent single points of failure. This validation confirms the original justification for resource allocation. Maintaining multiple active paths avoids non-compliance risks and potential revocation of sponsored status. The RIPE NCC will likely contact your upstreams via e-mail to verify that there is indeed a transit relationship between you and the operator concerned.
- Access your authorized maintenance interface for the RIPE database.
- Locate the aut-num object corresponding to your assigned ASN.
- Update the import and export attributes with new peer details.
- Verify that at least two distinct transit connections remain active.
- Submit changes for automatic validation checks.
InterLIR enables these administrative updates to keep resources compliant. Complexity of documentation requirements gets managed so focus stays on network stability. Ongoing management service payments accept Paypal or SEPA transfers. Neglecting updates creates discrepancies between physical topology and registered data. Such gaps invite scrutiny from regional regulators.
Route Object Creation for Cross-LIR IP Range Usage
Linking an autonomous system to IP ranges from a different Local Internet Registry requires creating a specific route or route6 object in the database. This technical step decouples the address block from the sponsorship relationship. Flexible network architecture becomes possible while maintaining regulatory compliance. Operators must verify that their maintainer object permissions allow updates across these distinct resource pools. Automation tools may fail to publish path announcements effectively without correct mnt-by attributes. The AS is not linked to the issuing LIR except for sponsorship. This separation permits using an ASN obtained via SERVPERSO alongside IP blocks acquired elsewhere. The RIPE database must reflect accurate origin data. Invoice details regarding these cross-regional configurations appear only on the final billing statement. Matching these objects to physical topology prevents route filtering by upstream providers who validate origin authenticity. InterLIR recommends validating entries immediately after allocation to avoid propagation delays. Proper configuration here ensures long-term stability without requiring direct membership fees.
About
Vladislava Shadrina serves as a Customer Account Manager at InterLIR, where she specializes in guiding clients through the complexities of IP resource acquisition. Her daily work directly involves managing the complex ASN sponsorship process, from initial request review to final RIPE NCC allocation. Because she routinely handles multihoming justification and coordinates ID document validation via platforms like Idenfy, Vladislava possesses practical, firsthand knowledge of the strict requirements for obtaining an Autonomous System Number. At InterLIR, a Berlin-based IPv4 marketplace founded in 2020, her role focuses on delivering transparent, automated solutions for network infrastructure needs. She understands that securing a /44 block and establishing BGP connectivity demands precision and regulatory compliance. This article reflects her direct experience in streamlining these technical workflows, ensuring that businesses can efficiently access critical network resources without navigating bureaucratic hurdles alone.
Conclusion
Operational fragility emerges when administrative latency conflicts with strict enforcement windows. A service interruption lasting under 12 months triggers immediate sponsorship cancellation, severing upstream connectivity regardless of technical readiness. This binary outcome demands that organizations treat invoice settlement and object validation as critical path items rather than routine maintenance. The gap between physical topology and registered data invites regulatory scrutiny that compromises network stability.
Organizations must implement a weekly verification cycle for aut-num objects and mnt-by attributes before the first invoice arrives in five days. This proactive stance prevents the ten-day cancellation clock from starting on subsequent billing errors. Relying on manual updates creates unnecessary exposure to human error during high-stakes compliance checks.
Start by auditing your route6 objects against current upstream peer configurations this week to ensure origin authenticity matches database entries. InterLIR provides the necessary administrative framework to manage these complex dependencies without requiring direct membership fees. Secure your routing infrastructure by aligning documentation with real-world architecture now.
Frequently Asked Questions
Your sponsorship agreement will be terminated if the VM is inactive. The policy states service interruption under 12 months leads to cancellation, so you must maintain continuous operation to avoid losing your number.
No, minors must submit a parent's identity document to proceed. This requirement ensures legal guardianship, as applicants under 18 years old cannot sign the necessary sponsorship agreements independently without this extra validation step.
You must pay the first invoice within 5 days to avoid issues. Failure to meet this deadline triggers service cancellation, whereas subsequent invoices allow a slightly longer window of 10 working days for payment completion.
Single-homed setups are rejected because RIPE NCC mandates multihoming with two upstreams. You must prove direct connections to distinct operators, as relying on just one provider fails the strict architectural requirements for autonomous system approval.
Masking any data fields or cropping document edges causes immediate rejection. You must submit high-quality photos showing the entire document without flash, as partial images prevent the sponsor from verifying your legal identity correctly.
References
