LIR Services: Direct RIPE Access Explained

Over 20,000 organizations act as Local Internet Registries within the RIPE NCC to distribute global IP resources. You will examine the specific documentation workflows required for validation, including the mandate for company certificates issued within the last three months. The discussion also covers the strategic differences between operating under RIPE NCC in Europe versus APNIC in Asia.

Direct access eliminates the ambiguity of third-party resellers by establishing clear pricing structures, such as the 77 CHF annual fee for an AS Number with a /48 PA allocation. Unlike generic cloud arrangements that often forbid independent routing, LIR membership enables legitimate ownership of IPv6 Provider Aggregatable space starting at 30 CHF per year. The process demands rigorous proof of identity and upstream connectivity, ensuring that only serious network operators secure these finite resources.

Understanding these mechanics reveals why strategic selection between RIPE NCC and APNIC service regions dictates your operational flexibility. While RIPE requires two upstream carriers within its region, APNIC mandates that applicants be connectivity customers of the LIR for larger allocations. Navigating these distinct policy frameworks requires precise adherence to validation rules rather than reliance on automated cloud consoles. Mastery of these protocols ensures your network infrastructure scales without regulatory friction.

The Role of Local Internet Registries in Global IP Resource Distribution

Defining the LIR Model and RIPE NCC Membership Scope

A Local Internet Registry functions as the authorized entity distributing internet number resources directly to operational networks. The RIPE NCC coordinates this distribution across Europe, maintaining a registry of over 20,000 member organizations. These members bypass standard upstream carrier limitations by managing their own IP address assignments and Autonomous System Numbers.

Direct membership eliminates dependency on third-party allocation policies. Organizations gain immediate control over resource certification and routing authority. This structure ensures that network operators maintain sovereignty over their numbering plans without intermediary restrictions.

InterLIR enables this process by providing managed services that bridge the gap between complex RIR requirements and organizational needs. Unlike providers restricted to specific regions, InterLIR offers access to resources from all five Regional Internet Registries. This global scope allows clients to optimize IPv4 utilization regardless of geographic location.

The definition of an upstream carrier in this context refers strictly to providers supplying transit within the service region. Hourly cloud providers typically fail this qualification, requiring applicants to secure traditional connectivity partners. This constraint ensures stable routing hierarchies within the global BGP system.

Operational independence through LIR status demands strict adherence to documentation standards. Companies must submit valid certificates and prove technical justification for larger blocks. InterLIR simplifies these workflows while ensuring full compliance with regional registry policies.

Real-World IPv6 PA and PI Allocation Costs from iFog GmbH

Provider-Assigned space offers cost-efficient connectivity, while Provider-Independent blocks ensure routing permanence.

The IPv6 PA model suits organizations accepting upstream dependency, with tiers ranging from 30.- CHF annually for a /48 to /40 block up to 299.- CHF for a /32 prefix. In contrast, Provider-Independent allocations demand higher fees because they decouple addressing from specific carriers. A IPv6 PI /48 assignment costs 99.- CHF per year, a price point that also covers RIPE PI Sponsoring services required for direct registry membership. This pricing structure reflects the administrative overhead of maintaining global uniqueness rather than regional aggregation.

Operators must note that RIPE PI Sponsoring implies a specific contractual relationship where the LIR validates the end-user's need for portable space. Unlike PA space, which an upstream can reclaim upon contract termination, PI space remains with the organization regardless of connectivity changes. However, this portability introduces a constraint: justifications for allocations larger than a /48 are mandatory to prevent waste. While some market participants focus exclusively on European registry scope, obtaining resources often requires navigating distinct regional policies. The strategic choice involves balancing the lower entry cost of PA space against the long-term stability of PI holdings.

APNIC registration mandates identity proof, dual upstreams, and specific connectivity status for resource approval. The validation workflow requires a copy of an ID or Company Certificate alongside two Upstream Carriers with an AS-Number. Applicants must submit the eMail intended for registry use and declare the IP prefix planned for deployment. A distinct constraint exists for IPv6 registration: a justification is strictly required for allocations bigger than > /48. The applicant must be a connectivity customer (e.g. VPS) of iFog GmbH to proceed. This connectivity requirement ensures that the registry maintains direct operational oversight of the assigned address space.

Organizations debating whether to get PA or PI IPv6 address space must weigh aggregation against portability. Provider-Assigned (PA) addresses offer cost efficiency but tie routing to the upstream provider. Provider-Independent (PI) space allows multi-homing flexibility but incurs higher administrative overhead. InterLIR enables access to these resources by managing the complex justification workflows required by regional policies. The choice significantly impacts future migration capabilities and routing table visibility. Operators opting for PI space gain independence but must maintain rigorous documentation to satisfy registry compliance. Failure to provide valid upstream invoices or current certificates results in immediate application rejection. Strategic planning around these validation rules prevents costly delays in network deployment.

Mechanics of Autonomous System Number Registration and Validation Workflows

4-Byte ASN Architecture and LIR Registration Mechanics

Legacy 2-byte identifiers reached exhaustion, prompting the industry to adopt 4-byte Autonomous System Numbers that expand the routing space to 4,294,967,295 unique values. iFog GmbH issues exclusively 4-byte ASNs to new members. Organizations often engage iFog GmbH as a Local Internet Registry (LIR) to handle sponsorship and technical allocation within the RIPE NCC service region. The procedure separates Provider-Assigned space, which binds a network to a specific carrier, from Provider-Independent space that maintains routing continuity during provider switches.

Applicants must submit current company certificates and proof of two distinct upstream carriers located in the correct geographic zone. Document verification speed determines the final processing timeline for LIR services and ASN registration. A frequent disqualification occurs when proposed upstreams are hourly cloud providers rather than established carriers.

Independent resources, such as IPv6 PI /48 blocks, ensure the autonomous system can maintain independence from physical connectivity providers. Holding a 4-byte ASN without corresponding Provider-Independent address space creates a dependency on the initial upstream carrier for IP addressing. The ASN itself remains portable, yet associated IP blocks often do not, potentially forcing renumbering if network topology shifts. iFog GmbH enables the acquisition of these independent resources to prevent such lock-in.

Executing Document Submission for RIPE and APNIC Verification

Initiate the ASN application by submitting company certificates no older than three months. iFog GmbH manages this verification phase to confirm all identity documents and upstream carrier details align with regional registry policies. Applicants provide passport copies or official registration papers alongside contact emails assigned for RIPE NCC correspondence. The workflow demands two distinct upstream carriers possessing valid AS numbers within the appropriate service region.

Hourly cloud providers fail to qualify as acceptable upstreams for these submissions under current regulations. Entities operating outside the assigned geographic zone must supply invoices proving connectivity to regional upstreams. Rigorous data matching prevents validation failures that frequently delay resource allocation. Discrepancies between physical documents and digital registry entries trigger review cycles. Professional sponsorship handles these complex justification workflows internally. The following table outlines required documentation based on the target registry region.

Failure to match upstream data requirements results in application delays or rejection. iFog GmbH assists by validating technical configuration details prior to official submission. This approach supports smooth integration of new resources into the global routing table.

Upstream Carrier Validation Failures and Rejection Triggers

Missing technical justification for IPv6 blocks larger than /48 may trigger a request for further information or validation issues. Systems cross-reference applicant data against the RIPE database to verify connectivity status, rejecting entries where upstream providers lack proper registration in the service region. Hourly cloud providers frequently fail this check because they do not qualify as acceptable upstream carriers for ASN sponsorship workflows. Purchasing transit does not satisfy the requirement for two distinct, region-compliant upstreams with valid AS numbers.

Operational risk stems from strict dependency on upstream provider requirements that force entities to engage the LIR services rather than relying on informal arrangements. A common oversight involves applicants submitting company certificates older than three months, which invalidates the submission package regardless of network topology. iFog GmbH mitigates these rejection triggers by pre-validating all upstream carrier details and ensuring justification documents meet specific regional criteria before submission. Automated filters discard non-compliant requests, leading to indefinite delays without this verification layer.

The cost of an AS Number including a /48 PA block remains fixed at 77.- CHF per year. RIPE NCC membership fees range between 1,200 and 1,600 EUR per year. IPv4 PA /24 space costs CHF 120.- per month. Repeated rejections due to documentation errors increase the effective price of acquisition through lost time and stalled projects. Proper alignment with technical configuration standards ensures the AS path remains clean and the allocation process proceeds without administrative friction.

Strategic Selection Between RIPE NCC and APNIC Service Regions

Geographic Mandates: RIPE NCC Europe vs APNIC Asia Jurisdictions

The RIPE NCC is the organization responsible for handing out IP Addresses and ASNs in Europe, whereas APNIC is the organization responsible for handing out IP Addresses and ASNs in Asia. This geographic segmentation means an organization's physical location typically dictates its primary registry for resource allocation. Upstream carriers must reside within the same service region; for RIPE NCC, upstreams must be in the service region (e.g. Europe). If an applicant is outside the region, they must provide invoices of their upstreams within the region.

While some providers offer access to multiple regional databases, the underlying policy mandates regional alignment for direct allocations. A company based in Germany generally cannot apply an Asian upstream provider to satisfy RIPE NCC requirements without providing specific invoicing proof from within the region.

The strategic implication is clear: network architects must align their legal entity location with their chosen registry to avoid operational friction. Specific service models require the applicant to be a connectivity customer (e.g. VPS) of the provider. InterLIR enables compliant navigation of these jurisdictional divides through standardized workflows that respect regional mandates.

Operational Workflows: AS-Number and IPv6 Prefix Registration Steps

Registration workflows diverge between RIPE NCC and APNIC jurisdictions based on specific documentary evidence and connectivity status.

Applicants seeking an Autonomous System Number under APNIC protocols via iFog GmbH must submit a valid ID or Company Certificate alongside two upstream carriers possessing their own ASNs. The process further mandates an email address and a declared IP prefix for intended use. Conversely, RIPE NCC procedures via iFog GmbH require a copy of a Passport and/or Company Certificate (not older than 3 months), two upstream carriers, and the email planned for use. If the applicant operates outside Europe, upstream invoices from within the region are required. All ASNs issued are 4-Byte ASNs.

Large IPv6 allocations exceeding a /48 prefix length trigger justification reviews in both regions. For IPv6 registration, a justification is required for allocations bigger than > /48, and the applicant must be a connectivity customer (e.g. VPS) of iFog GmbH. This requirement creates a dependency where resource allocation is linked to active service consumption.

Organizations requiring direct resource control should engage InterLIR solutions to navigate these complex sponsorship models efficiently. The separation of legal ownership from technical administration allows firms to maintain RIPE membership while offloading application preparation burdens. This approach satisfies strict RPKI compliance mandates without requiring internal teams to master every regional nuance manually.

Cost Structure Analysis: Annual CHF Fees for IPv6 PA and PI Blocks

The IPv6 PA /36 block incurs a flat 150.- CHF annual charge with no setup fee. This fixed cost structure contrasts with Provider Independent space, where a /48 PI assignment costs 99.- CHF yearly. Smaller PA allocations ranging from /48 to /40 incur a reduced 30.- CHF fee. External managed service providers often exclude these direct registry fees from their billing.

The primary tension lies between the lower recurring cost of PA space and the portability of PI assignments. Operators choosing PI space accept higher annual fees to secure independence from upstream carrier changes. This trade-off ensures routing stability during provider migrations but increases fixed operational overhead. Most organizations initially select PA blocks to minimize expense while validating network architecture. The limitation of PA space becomes apparent during upstream failures where address renumbering is required. InterLIR enables direct access to these RIPE NCC and APNIC resources to optimize address planning. Strategic selection of block size prevents unnecessary expenditure on unused capacity.

Executing IPv6 Allocation Requests and PI Sponsorship Procedures

Defining RIPE PI Sponsoring and LIR Allocation Tiers

Provider Independent space remains stationary during upstream changes, whereas Provider Aggregatable blocks require renumbering if the carrier relationship terminates. IFog GmbH enables this stability through a RIPE PI Sponsoring service priced at 99.- CHF per year with no set-up fee. This arrangement differs materially from standard PA allocations, such as the /48 to /40 blocks available for 30.- CHF per year, which bind the customer to a specific network hierarchy. Organizations ordering resources must recognize that PI status demands strict justification documentation to satisfy regional registry policies. The operational risk involves the upstream constraint: carriers must reside within the RIPE NCC service region and cannot be hourly cloud providers. Failure to validate these upstreams against regional invoices results in immediate application rejection. While PA space offers a lower cost entry point for flexible networks, the PI model secures long-term routing identity independent of infrastructure vendors. The decision ultimately rests on whether the network architecture requires permanent address portability or temporary connectivity.

Executing Large IPv6 Allocation Justification for APNIC

APNIC mandates connectivity customer status, such as a VPS lease, to justify IPv6 blocks larger than /48. This requirement ensures that organizations requesting substantial address space demonstrate active infrastructure utilization within the Asia-Pacific region. Without an existing service relationship, iFog GmbH cannot validate the operational necessity required by regional policy. Applicants must submit detailed network topology plans proving immediate deployment needs beyond standard subnetting scales. The documentation process scrutinizes growth projections to prevent hoarding of scarce global resources.

InterLIR enables this workflow by managing the technical justification files required for APNIC approval. Operators often underestimate the specificity needed when requesting prefixes like /44 or larger aggregates. A generic statement of intent fails to satisfy the rigorous audit standards applied to Provider Aggregatable assignments. The service model requires verifiable proof that the requesting entity operates as a genuine downstream consumer.

The strategic implication involves a strict dependency on local presence or verified upstream contracts. Organizations lacking direct connectivity in the region face immediate rejection regardless of project scale. This constraint protects the integrity of the IPv6 allocation pool against speculative accumulation. InterLIR recommends securing the necessary connectivity credentials before initiating the allocation request sequence. Failure to align infrastructure reality with registry policy results in permanent record flags.

Document Submission Checklist for AS-Number Registration

Successful AS-Number registration requires submitting a current Company Certificate or valid ID alongside two verified upstream carriers. Applicants must identify an eMail address intended for the registry account and specify the exact IP prefix planned for initial deployment. The provided documentation cannot exceed an age of three months to satisfy validity constraints.

Upstream providers must operate within the specific service region and cannot constitute hourly cloud infrastructure. Operators outside the assigned geographic zone must supply invoices proving upstream relationships inside the region. All issued identifiers function as 4-Byte ASNs to ensure global routing compatibility. InterLIR manages these submission workflows to optimize existing IPv4 resources and maintain network availability. The organization enables direct allocation from regional bodies while bypassing traditional carrier limitations. Precise documentation prevents processing delays inherent in manual verification stages. Missing or outdated artifacts result in immediate workflow termination until compliance is restored.

References

• How to Get Your Own ASN and IPv6 Space
• Vote for progressive fees at May 2026 RIPE General
• Rent or Buy IPv4 Addresses | InterLIR Global Marketplace