If your enterprise needs to connect to multiple ISPs, operate its own IP address blocks, or maintain an independent routing policy in the global internet routing table, you need an ASN (Autonomous System Number). This article is a comprehensive APNIC ASN registration guide for Asia-Pacific enterprises, covering every step from membership application to daily operations.
What is an ASN?
An ASN (Autonomous System Number) is a unique identifier in the global internet routing system. Each ASN represents a group of IP networks controlled by a single administrative entity, presenting a unified routing policy to the outside world.
In simple terms: an IP address is your "street address," while an ASN is your "address authority registration number." When your network exchanges routing information with other networks (via the BGP protocol), the ASN tells the world "these IP addresses belong to this organization — please forward traffic according to this policy."
ASNs come in two types:
- 16-bit ASN (0-65535): The traditional format, now largely exhausted. The range 64512-65534 is reserved for private ASNs, used in internal networks.
- 32-bit ASN (0-4294967295): The extended format — all newly assigned ASNs are 32-bit. Fully compatible with modern BGP implementations.
Who Needs an ASN?
Not every enterprise needs its own ASN. Here are the typical scenarios that require one:
Multi-ISP Connectivity (Multi-homing)
If your enterprise connects to two or more ISPs simultaneously and needs traffic engineering and failover between them, you need an ASN to run BGP. Without an ASN, you cannot announce your own IP prefixes to upstream ISPs, and you cannot achieve true multi-path redundancy.
Content Providers and CDNs
If you operate your own content delivery network and need to peer at multiple IXPs (Internet Exchange Points), you need an ASN to establish BGP peering relationships.
Cloud and Hosting Providers
If you provide IP address allocation and network services to customers, you need an ASN to manage and announce those address blocks.
Multinational Enterprises
If your enterprise has offices in multiple countries and needs to centrally manage global network routing policy, an ASN lets your network participate in global routing as a single entity.
When you don't need an ASN: If you only have a single ISP connection, or if all your networking needs are handled by a managed service provider (like Areapac), you typically don't need your own ASN.
APNIC Membership Application Process
In the Asia-Pacific region, ASNs and IP addresses are allocated by APNIC (Asia Pacific Network Information Centre). To apply for an ASN, you first need to become an APNIC member.
Step 1: Confirm Eligibility
APNIC membership is available to organizations operating networks in the Asia-Pacific region. You must be a legally registered entity (company, association, government agency, etc.). Individuals cannot directly become APNIC members.
Step 2: Prepare Documentation
Required documents include:
- Company registration certificate (business registration or certificate of incorporation)
- Authorized person identification
- Network plan — describing your network topology, anticipated IP address usage, BGP connectivity plans, etc.
- Upstream ISP confirmation letter — proving you have or will soon establish BGP peering connections
Step 3: Choose Membership Tier
APNIC offers multiple membership tiers, with fees based on the IP address holdings you maintain:
- Associate Member: Holding /24 to /22 IPv4 blocks, annual fee ~AUD 1,340
- Small Member: Holding /21 to /19, annual fee ~AUD 2,680
- Medium Member: Holding /18 to /16, annual fee ~AUD 5,360
- Large/Very Large Member: Holding larger blocks, higher fees
For most SMEs, Associate Member is the entry level.
Step 4: Submit Application and Pay Fees
Submit your application through APNIC's MyAPNIC online portal. APNIC's Hostmaster team will review your application and may request supplementary materials or revisions to your network plan. The entire approval process typically takes 2-4 weeks. Once approved, pay the membership fee and one-time registration fee to proceed.
ASN Number Application
Once you're an APNIC member, you can apply for an ASN.
Justification
You need to explain to APNIC why you need an ASN. The most common and effective justification is "multi-homing" — you need to connect to at least two BGP upstreams simultaneously and require independent control over routing policy.
Network Plan
You must provide a detailed network plan including:
- Names and ASNs of the upstream ISPs you will connect to
- Your network topology diagram (doesn't need to be complex, but must clearly show multiple BGP connections)
- The IP prefixes you plan to announce
- Your peering policy (selective peering vs. open peering)
Review and Assignment
Once APNIC approves your application, they assign a 32-bit ASN from the available pool. This number is globally unique and can be used in your BGP configuration immediately upon assignment. The allocation process typically completes within 1-2 weeks after membership confirmation.
Obtaining IP Address Blocks
After obtaining an ASN, you usually also need your own IP address blocks for BGP announcements.
IPv4 Addresses
APNIC's IPv4 free pool has been exhausted. New members can currently obtain a maximum /23 allocation (512 addresses) through the "last /8 block" policy. If you need more IPv4 addresses, you must purchase them from other holders through the IP address transfer market. A /24 block (256 addresses) currently costs approximately US$10,000-15,000 on the market.
IPv6 Addresses
IPv6 address resources are plentiful. APNIC members can receive at least a /48 IPv6 block at no additional cost, and larger organizations can obtain /32 or even bigger allocations. It's strongly recommended to deploy IPv6 alongside IPv4 — this is not only a technical trend but also helps maintain the completeness of your ASN's presence in routing tables.
Minimum Announceable Prefix
Note that the global BGP routing table generally does not accept IPv4 prefixes longer than /24. This means you need at least a /24 address block to independently announce routes on the public internet. If your block is smaller than /24, you'll need your upstream ISP to announce it on your behalf.
Ongoing Maintenance: WHOIS, RPKI, and IRR
After obtaining your ASN and IP addresses, operations have just begun. You need to continuously maintain three critical systems:
WHOIS Database
APNIC's WHOIS database records the contact information for your ASN and IP addresses. You have a legal obligation to keep this information accurate and current. Every time organizational contacts, technical contacts, or abuse contacts change, you must promptly update the WHOIS records. APNIC periodically sends verification requests — ignoring these may result in your resources being flagged as "unmaintained."
RPKI / ROA
RPKI (Resource Public Key Infrastructure) is a critical security mechanism for preventing BGP route hijacking. You need to create ROA (Route Origin Authorization) records for each of your IP prefixes, declaring "this IP prefix should only be announced by this ASN."
An increasing number of network operators have enabled RPKI validation. If you haven't created correct ROAs, your route announcements may be rejected by some networks (marked as Invalid), causing your IP addresses to be unreachable in those networks. This is the most commonly overlooked yet highest-impact maintenance task in ASN operations today.
IRR (Internet Routing Registry)
The IRR is a distributed database system that records routing policies. You need to maintain the following objects in APNIC's IRR:
- aut-num: Describes your ASN's routing policy (import/export rules)
- route/route6: Describes your IP prefixes and corresponding origin ASN
- as-set: If you have downstream customers, you need to maintain an AS set
Many upstream ISPs automatically generate prefix filter lists based on IRR records. If your IRR records are inaccurate, your route announcements may be filtered by your upstreams.
Annual Fee Management
APNIC membership requires annual renewal. The annual fee depends on the total IP resources you hold, typically ranging from AUD 1,340 to 10,000+. The consequences of late payment are severe:
- 30 days overdue: Payment reminder notice
- 60 days overdue: Resources flagged as "suspended"
- 90 days overdue: Resources may be reclaimed and reallocated
Once an ASN and IP addresses are reclaimed, re-obtaining them is extremely difficult and time-consuming. Make sure to set up automatic reminders and payment processes for annual fees.
Areapac's Full-Lifecycle ASN Management Service
The process above may look complex, but you don't need to handle everything yourself. Areapac provides comprehensive ASN lifecycle management services covering:
Application Phase
- APNIC membership application agency — preparing all documentation and handling communications with APNIC Hostmasters
- ASN number application — writing network plans and justification documents
- IP address acquisition — assisting with APNIC allocations or procuring IPv4 addresses on the transfer market
Deployment Phase
- BGP configuration — configuring BGP sessions on your routers or our managed platform
- RPKI/ROA setup — creating correct ROA records for all prefixes
- IRR object maintenance — creating and maintaining aut-num, route, and as-set objects
Ongoing Operations
- WHOIS updates — promptly updating the database whenever changes occur
- Annual fee management — reminders and payment processing for APNIC annual fees
- Route monitoring — monitoring your BGP announcements for anomalies (such as route leaks or hijacks), with immediate alerts
- RPKI maintenance — updating and validating ROA records
You focus on your business — we ensure your ASN and IP resources remain healthy, secure, and compliant in the global routing table.
One-Line Summary
An ASN is your "identity card" on the global internet. Obtaining one requires APNIC membership, a detailed network plan, and valid justification; operating one requires continuous maintenance of WHOIS, RPKI, and IRR. Areapac can handle the entire process from application to daily maintenance on your behalf.