RIR Resource Allocation Data Inconsistencies

Updated: 28/11/2022 04:12

Full Report     APNIC     ARIN     RIPE     LACNIC     AFRINIC

ARIN Report

This report examines the consistency of data published by arin, comparing the stats reports with other reports describing allocations. If the data sets were fully consistent the report would be empty.

This is a report of the various inconsistencies noted in the reports published by ARIN. The underlying assumption in these reports is that ARIN stats files contain a complete record of all allocated numbers, and that all other reports (including WHOIS databases, issued and latest files) should refer to number ranges described in the stats files. It is also assumed that the stats files do not overlap, and that a whois entry published by each RIR refers to allocated numbers described in that RIRs stats file.

Reasons:

• Not in Stats: the entry exists in the named RIR file, but no corresponding entry can be located in the stats file.
• Extends Stats: the entry is an aggregate of one or more entries in the RIR stats file, but also encompasses space not recorded in the stats file.
• Stats Overlap: the entry exists in the data records of two (or more) RIR data files
• Data Overlap: the entry exists in the database data records of an RIR's database report, and in the registry report stats file in another RIR at the same time
• IANA Reserved Block: the entry encompasses space that the IANA registry describes as reserved.

Data-Type Registry File         Reason                 Entry

IPv4      arin     arin.db      Not in Stats           SHARED-ADDRESS-SPACE-RFC6598-IANA-RESERVED: 100.64.0.0/10 
                   arin.db      Not in Stats           DS-LITE-RFC-6333-11-IANA-RESERVED: 192.0.0.0/29