Index of /apnic/stats/apnic

[ICO]NameLast modifiedSizeDescription

[DIR]Parent Directory   -  
[DIR]transfers/ 23-Jul-2024 04:00 -  
[   ]legacy-apnic-latest.md5 23-Jul-2024 01:15 61 MD5 signature
[TXT]legacy-apnic-latest.asc 23-Jul-2024 01:15 189 PGP signature
[   ]legacy-apnic-latest 23-Jul-2024 01:15 91K 
[   ]legacy-apnic-20240723.md5 23-Jul-2024 01:15 63 MD5 signature
[TXT]legacy-apnic-20240723.asc 23-Jul-2024 01:15 189 PGP signature
[   ]legacy-apnic-20240723 23-Jul-2024 01:15 91K 
[   ]delegated-apnic-latest.md5 23-Jul-2024 01:17 64 MD5 signature
[TXT]delegated-apnic-latest.asc 23-Jul-2024 01:17 189 PGP signature
[TXT]delegated-apnic-latest 23-Jul-2024 01:17 3.7MAPNIC delegated internet number resources
[   ]delegated-apnic-ipv6-assign..>23-Jul-2024 01:17 78 MD5 signature
[TXT]delegated-apnic-ipv6-assign..>23-Jul-2024 01:17 189 PGP signature
[TXT]delegated-apnic-ipv6-assign..>23-Jul-2024 01:17 256K 
[   ]delegated-apnic-ipv6-assign..>23-Jul-2024 01:17 80 MD5 signature
[TXT]delegated-apnic-ipv6-assign..>23-Jul-2024 01:17 189 PGP signature
[TXT]delegated-apnic-ipv6-assign..>23-Jul-2024 01:17 256K 
[   ]delegated-apnic-extended-la..>23-Jul-2024 01:17 73 MD5 signature
[TXT]delegated-apnic-extended-la..>23-Jul-2024 01:17 189 PGP signature
[TXT]delegated-apnic-extended-la..>23-Jul-2024 01:17 7.9M 
[   ]delegated-apnic-extended-20..>23-Jul-2024 01:17 75 MD5 signature
[TXT]delegated-apnic-extended-20..>23-Jul-2024 01:17 189 PGP signature
[TXT]delegated-apnic-extended-20..>23-Jul-2024 01:17 7.9M 
[   ]delegated-apnic-20240723.md5 23-Jul-2024 01:17 66 MD5 signature
[TXT]delegated-apnic-20240723.asc 23-Jul-2024 01:17 189 PGP signature
[TXT]delegated-apnic-20240723 23-Jul-2024 01:17 3.7M 
[TXT]assigned-apnic-latest 23-Jul-2024 01:17 78KAssignment summaries by economy
[TXT]assigned-apnic-20240723 23-Jul-2024 01:17 78K 
[DIR]2024/ 23-Jul-2024 04:30 -  
[DIR]2023/ 02-Jan-2024 07:48 -  
[DIR]2022/ 31-Dec-2022 04:30 -  
[DIR]2021/ 07-Jan-2022 09:25 -  
[DIR]2020/ 31-Dec-2020 04:30 -  
[DIR]2019/ 28-Jan-2020 10:24 -  
[DIR]2018/ 31-Dec-2018 04:30 -  
[DIR]2017/ 31-Dec-2017 04:30 -  
[DIR]2016/ 31-Dec-2016 04:30 -  
[DIR]2015/ 31-Dec-2015 04:30 -  
[DIR]2014/ 31-Dec-2014 04:30 -  
[DIR]2013/ 31-Dec-2013 04:30 -  
[DIR]2012/ 31-Dec-2012 04:30 -  
[DIR]2011/ 31-Dec-2011 04:30 -  
[DIR]2010/ 29-Sep-2014 14:23 -  
[DIR]2009/ 18-Sep-2018 09:37 -  
[DIR]2008/ 01-Oct-2014 13:59 -  
[DIR]2007/ 14-Apr-2009 11:40 -  
[DIR]2006/ 19-Sep-2018 09:23 -  
[DIR]2005/ 14-Apr-2009 11:40 -  
[DIR]2004/ 01-Oct-2014 15:57 -  
[DIR]2003/ 01-Oct-2014 13:36 -  
[DIR]2002/ 06-Jan-2004 10:29 -  
[DIR]2001/ 29-Sep-2014 16:24 -  

 (version 2.0 5 January 2004)


 1. About these reports
 2. Conditions of use
 3. Statistics format


The directory contains 
daily summary reports of the allocations and assignments of numeric 
Internet address resources within ranges originally delegated to 
APNIC and historical ranges transferred to APNIC by other 

The resources reported are:

	- IPv4 address ranges (IPv4)
	- IPv6 address ranges (IPv6)
	- Autonomous System Numbers (ASNs)

These reports are produced as part of a joint Regional Internet 
Registry (RIR) project to provide consistent and accessible 
Internet resource statistics to the global community. It is hoped
these reports will lead to increased research and analysis of the 
global use of address resources. 

For detailed information on the RIR statistics exchange format, 


The files are freely available for download and use on the condition 
that APNIC will not be held responsible for any loss or damage 
arising from the use of the information contained in these reports.

APNIC endeavours to the best of its ability to ensure the accuracy 
of these reports; however, APNIC makes no guarantee in this regard.

In particular, it should be noted that these reports seek to 
indicate where resources were first allocated or assigned. It is not
intended that these reports be considered as an authoritative 
statement of the location in which any specific resource may 
currently be in use.



3.1 	File names

Each file is named using the format:


The most recent file will also be available under the name:


3.2	File format

The file consists of: 

	- comments
	- file header lines
	- records

Header and record lines are structured as 'comma separated fields'
(CSV). Leading and trailing blank text in fields not meaningful.

The vertical line character '|' (ASCII code 0x7c) is used as the
CSV field separator.

After the header lines, records are not sorted.


Comments are denoted by # at the beginning of a line. No
line-embedded comments are permitted. Comments may occur at
any place in the file.


	#optional comments.
	#   any number of lines.

	#another optional comment.

Blank lines are permitted, and may occur at any place in the file.

3.2.2 	File header

The file header consists of the version line and the summary
lines for each type of record. 

Version line




	version  	format version number of this file, 
			currently 2;

	registry   	as for records and filename (see below);

	serial     	serial number of this file (within the
			creating RIR series);

	records    	number of records in file, excluding blank
			lines, summary lines, the version line and 

	startdate  	start date of time period, in yyyymmdd 

	enddate    	end date of period in yyyymmdd format;
	UTCoffset  	offset from UTC (+/- hours) of local RIR
			producing file.

Summary line

The summary lines count the number of record lines of each type in 
the file.




	registry   	as for records (see below);
	*          	an ASCII '*' (unused field, retained for
			spreadsheet purposes);
	type       	as for records (defined below);
	count      	sum of the number of record lines of this 
			type in	the file.
	summary    	the ASCII string 'summary' (to distinguish 
			the record line);

Note that the count does not equate to the total amount of resources
for each class of record. This is to be computed from the records

3.2.3 	Records

After the defined file header, and excluding any space or comments,
each line in the file represents a single allocation (or assignment)
of a specific range of Internet number resources (IPv4, IPv6 or
ASN), made by the RIR identified in the record.

IPv4  records may represent non-CIDR ranges or CIDR blocks, and 
therefore the record format represents the beginning of range, and a
count. This can be converted to prefix/length using simple algorithms.

IPv6 records represent the prefix and the count of /128 instances 
under that prefix.




	registry  	The registry from which the data is taken.
			For APNIC resources, this will be:


	cc        	ISO 3166 2-letter code of the organisation to
	                which the allocation or assignment was made. 

	type      	Type of Internet number resource represented
			in this record. One value from the set of 
			defined strings:


	start     	In the case of records of type 'ipv4' or
			'ipv6' this is the IPv4 or IPv6 'first
			address' of the	range.

			In the case of an 16 bit AS number, the
			format is the integer value in the range:
			    0 - 65535
			In the case of a 32 bit ASN,  the value is
			in the range:
			    0 - 4294967296
		    	No distinction is drawn between 16 and 32
		    	bit ASN values in the range 0 to 65535.

	value     	In the case of IPv4 address the count of
			hosts for this range. This count does not 
			have to represent a CIDR range.

			In the case of an IPv6 address the value 
			will be the CIDR prefix length from the 
			'first address'	value of <start>.
			In the case of records of type 'asn' the 
			number is the count of AS from this start 

	date      	Date on this allocation/assignment was made
			by the RIR in the format:

			Where the allocation or assignment has been
			transferred from another registry, this date
			represents the date of first assignment or
			allocation as received in from the original

			It is noted that where records do not show a 
			date of	first assignment, this can take the 
			0000/00/00 value.

    	status    	Type of allocation from the set:

                            {allocated, assigned}

                	This is the allocation or assignment made by 
                	the registry producing the file and not any
                	sub-assignment by other agencies.

   	extensions 	In future, this may include extra data that 
   			is yet to be defined.

3.3 	Historical resources

Early Registration Transfers (ERX) and AUNIC legacy records do not
have any special tagging in the statistics reports. 


If you any questions or comments about these reports, please contact