Address block map

Every block the project collected from the five RIR delegation files, one page per first octet, each block sorted by start address with a link to all of its data. Grey rows inside a page are gaps: address space that no delegation record covers.

9,200 blocks covering 505,977,856 addresses. 4,403 gaps covering 3,218,170,880 addresses. 8,616 blocks are operator-held and 584 are not. 0 blocks hold at least one address that responded, refused, or reset, and 0 hold an isolated responder.

Status: allocated 7,116 assigned 1,500 available 97 reserved 487

RDAP state: object for the block 7,686 parent object 870 no object 27 unanswered 617

Flags: P RDAP answered with a parent object · 4 the registry holds no object · - RDAP unanswered · N no name in the RDAP object · A an address in the block responded · I an isolated responder · S the RDAP service is not the delegation registry's (544 blocks) · C delegation country and RDAP country differ (534 blocks)

Where to look

The irregularity classes, with a few examples each. Every block page carries the same flags.

By first octet

This page is generated from 02_ip_block.json by sources/ip_block_map.py. The registry's verbatim RDAP answer is not published: it carries registrant contact details, so it stays in the local work product.