IANA earlier assigned AS7467 - 7722 to APNIC and APNIC assigned it to their members or other legal entities.

% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object

refer:        whois.apnic.net

as-block:     7467-7722
organisation: Assigned by APNIC

whois:        whois.apnic.net
descr:        Assigned by APNIC

source:       IANA

Recently, Jason decided to change their network service provider. It’s mean they didn’t need multihoming, so he decided to transfer AS Number to me.

Action transfer

Step 0. Confirm Transfer Policies

Step 1. Make a request to APNIC

According to the Transfer Template in APNIC Inter-RIR transfer of unused IPv4 addresses and/or AS numbers , send an email to start the Inter-RIR ASN Transfer Request.

APNIC will send an email to you to confirm the request.

Step 2. Transfer process to RIPE NCC

Once APNIC approved the transfer request, the process will transfer to RIPE NCC.

Since it was a Friday when RIPE NCC received the transfer request, they were very busy. So the transfer was not processed until the weekend. (As an aside, the English of RIPE NCC’s Dutch office staff is very fast, which is not at the same level as APNIC XD)

Since my ORG is not an LIR, the resource will be transferred to the EndUser as the Sponsor LIR.

  • In general, if ORG is non-LIR, we have to look for LIR as Sponsor LIR

RIPE requested a lot of information from me in the first email and handles transfer requests in accordance with the following policies:

Questions list:

  • Initial information
  • Documentation
  • ID Validation via iDenfy​
  • ASNs already registered to Tsung-Yi Yu (ORG-TY18-RIPE)

Section 1 - Initial information

Is to confirm with me if you want to agree to this transfer request and become a Sponsor LIR. The next step is to confirm that there are Infras and routing policies in the RIPE NCC service area.

Section 2 - Documentation

Due to resource transfer and sponsorship LIR. So two documents need to be signed.

Section 3 - ID Validation via iDenfy​

Since the resource is registered to a natural person, ID and other information need to be verified. This part is the same as opening a bank account, which requires KYC.

Section 4 - ASNs already registered to Tsung-Yi Yu (ORG-TY18-RIPE)

Since I already have two AS Numbers, RIPE NCC would like to confirm with me if I want to transfer the Sponsor LIR of the existing ASN.

  • Probably asking this because I’m making a request on behalf of both LIR and EndUser XD.

After all documents are signed and submitted, RIPE NCC will make final confirmation with APNIC, update WHOIS and other documents, and complete the transfer procedures.


steveyiyo@SteveYis-MacBook-Pro ~ % whois -r as7480
as-block:       AS7480 - AS7480
descr:          RIPE NCC ASN block
remarks:        These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by:         RIPE-NCC-HM-MNT
created:        2022-03-01T17:14:47Z
last-modified:  2022-03-01T17:14:47Z
source:         RIPE

% Information related to 'AS7480'

% Abuse contact for 'AS7480' is 'abuse@steveyi.net'

aut-num:        AS7480
as-name:        STEVEYI-NETWORK
org:            ORG-TY18-RIPE
admin-c:        YT1698-RIPE
tech-c:         YT1698-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         STEVEYI-MNT
created:        2022-03-01T17:15:53Z
last-modified:  2022-03-02T08:35:19Z
source:         RIPE
sponsoring-org: ORG-KL272-RIPE

organisation:   ORG-TY18-RIPE
descr:          SteveYi Network Service
org-name:       Tsung-Yi Yu
org-type:       OTHER
address:        No. 6, Aly. 3, Ln. 108, Fushan St., Changhua City, Changhua County 50036 , Taiwan (R.O.C.)
abuse-c:        YT1698-RIPE
mnt-ref:        STEVEYI-MNT
mnt-by:         STEVEYI-MNT
created:        2020-01-26T17:35:48Z
last-modified:  2022-02-16T11:12:19Z
source:         RIPE # Filtered

role:           Tsung-Yi Yu
address:        No. 6, Aly. 3, Ln. 108, Fushan St., Changhua City, Changhua County 50036 , Taiwan (R.O.C.)
abuse-mailbox:  abuse@steveyi.net
nic-hdl:        YT1698-RIPE
mnt-by:         STEVEYI-MNT
created:        2020-01-26T19:09:13Z
last-modified:  2022-02-24T20:17:37Z
source:         RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.102.2 (BLAARKOP)

At the same time, you can also see the assignment record of this ASN in the assignment file of RIPE NCC.

steveyiyo@SteveYis-MacBook-Pro ~ % curl https://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest -s | grep 'asn|7480'

Step 3. Next steps

After completing the transfer, I need to update the records of other third-party platforms (Eg: PeeringDB)

Since I initiated the ownership Transfer to PeeringDB, APNIC has not yet deleted the record.

This caused their administrators to think that the owner of this ASN was not me.

After explaining, they confirmed the RIPE NCC’s WHOIS record and moved.


Step 4. Migrate the network

Before AS7480, my blackholes used AS60614 to peer with others.

We contacted the administrators of STUIX, ARIX, and Lambda-IX respectively, and replaced the Sessions of ASN and RS.

After the replacement was completed, we then contacted the NOC of Peer Sessions and also replaced the ASN together.

At the same time, we also updated the RPKI and IRR records to prevent prefix(es) from being filtered.


  • 2022-02-16 Initiate a transfer request to APNIC
  • 2022-02-18 APNIC Approved
  • 2022-02-22 RIPE Start transfer process
  • 2022-03-01 RIPE created aut-num object
  • 2022-03-02 APNIC confirmed the complete transfer process
  • 2022-03-02 PeeringDB transfer ownership
  • 2022-03-02 change Lambda-IX ASN
  • 2022-03-03 change STUIX ASN
  • 2022-03-04 change ARIX ASN
  • 2022-03-05 change upstream ASN
  • 2022-03-08 change all, deleted Session(s)