€89 vs €2,850: The Real Cost of Running Your Own ASN

Introduction

Getting an Autonomous System Number (ASN) in Europe looks simple on paper.

You submit an application, wait for approval, and you are ready to run your own BGP network.

But in reality, the ASN itself is not the expensive part.

The real cost comes from everything required to obtain, operate, and maintain it.

In this article, we break down the actual cost structure behind ASN ownership in Europe — and why different pricing models exist.

What an ASN Actually Gives You

An Autonomous System Number (ASN) allows you to:

• Run BGP routing with your own network identity
• Connect to multiple upstream providers (multi-homing)
• Control inbound and outbound traffic paths
• Build redundancy across regions or providers
• Operate independent network infrastructure

In simple terms:

An ASN gives you routing autonomy on the internet.

Without it, your infrastructure is always dependent on a single upstream provider's routing decisions.

Two Ways to Get an ASN in Europe

There are two legitimate paths to obtaining an ASN via RIPE NCC.

1. Direct RIPE NCC Membership (LIR Model)

The first option is becoming a Local Internet Registry (LIR) under RIPE NCC.

This means your organization directly participates in RIPE as a member.

Typical cost structure includes:

• One-time sign-up fee (RIPE NCC: €1,000 in 2026)
• Annual membership fee (RIPE NCC: €1,800 per LIR account in 2026)
• Annual ASN charge (RIPE NCC: €50 per ASN in 2026)
• Administrative overhead (internal engineering + compliance time)
• Ongoing policy and documentation responsibilities

But the cost is not only financial.

You are also responsible for:

• Understanding RIPE allocation policies
• Maintaining registry compliance
• Handling IP resource requests
• Managing audit and reporting requirements

This is effectively running a small registry operation.

2. LIR Sponsorship Model (~€89/year)

The second option is using an LIR sponsorship model.

In this case:

• You do NOT become a RIPE LIR yourself
• You operate under an existing LIR
• The LIR handles RIPE interaction and compliance
• If approved, the ASN is assigned to your organization and SKNK provides an IPv6 PA /48 from its LIR allocation
• You remain responsible for arranging an accepting upstream and operating BGP

SKNK's current price:

€89/year, including SKNK's current RIPE NCC sponsored-ASN charge

If you are weighing RIPE NCC membership against sponsorship and want a detailed breakdown, read our full comparison: RIPE NCC vs LIR Sponsorship.

Why the Price Difference Exists

The difference between €89 and €2,850 is not about the ASN itself.

It is about responsibility distribution.

You are not paying for the ASN.

You are paying for:

• Legal entity structure (LIR status)
• Administrative overhead
• Compliance responsibility
• Operational workload inside RIPE ecosystem

In other words:

One model gives you infrastructure access. The other gives you infrastructure ownership responsibility.

The Hidden Cost Nobody Talks About: Time

Beyond financial cost, the biggest hidden cost is operational time.

Direct RIPE membership requires:

• Learning RIPE policy documentation
• Handling allocation workflows
• Responding to registry requirements
• Managing internal compliance processes

For small teams or startups, this becomes:

Engineering time spent on administration instead of infrastructure.

Real-World Engineering Scenario

Consider a startup running infrastructure in Europe:

• Primary region: Frankfurt (Hetzner)
• Secondary region: Amsterdam (OVH)

They want:

• Multi-region deployment
• BGP-based failover
• Redundant upstream connectivity
• Stable latency routing across providers

Without ASN ownership, they are limited by:

• Single-provider routing decisions
• Lack of control over path selection
• Limited failover flexibility

What they actually need is:

• An ASN
• IPv6 /48 prefix
• Ability to announce routes via BGP
• Multi-homing capability

Not RIPE administrative complexity.

What Happens After You Get an ASN

Most explanations stop at "you receive an ASN".

In reality, the operational steps include:

• Establishing BGP sessions with upstream providers
• Configuring route announcements
• Defining traffic policies (local preference, MED, AS-path filtering)
• Managing failover behavior across providers
• Monitoring routing stability

This is where ASN ownership becomes real infrastructure work.

When Direct RIPE Membership Makes Sense

Direct membership may be appropriate if you:

• Operate large-scale infrastructure networks
• Manage multiple ASNs or IP allocations
• Need to operate and administer a RIPE NCC LIR account directly
• Already have networking expertise in-house

For a team that only needs one sponsored ASN, direct membership may add cost and registry administration that the project does not require. Compare the two models against your actual resource, policy, and operational needs.

Why LIR Sponsorship Exists

LIR sponsorship exists because most organizations do not need registry operations.

They need network capability.

It removes:

• Administrative burden
• Policy complexity
• Onboarding friction
• Registry maintenance overhead

While preserving:

• An ASN assigned to the End User
• Use of an IPv6 PA /48 while sponsorship remains active
• The ability to operate BGP when an upstream accepts the ASN and prefix

What You Actually Get

With a sponsorship model, you get:

• ASN allocation for BGP routing
• IPv6 /48 prefix (Provider Aggregatable space)
• Multi-provider routing capability
• Simplified onboarding process
• A documented application and status-tracking process

Conclusion

The difference between €89 and €2,850 is not pricing.

It is complexity distribution.

One model optimizes for ownership.

The other optimizes for simplicity.

For a team that needs one ASN, compare the lower administrative burden of sponsorship with the independence and responsibilities of running its own LIR. Neither model removes the need to arrange upstream connectivity and operate BGP.