The allocation of Internet Protocol version 6 (IPv6) unicast address space is listed here. References to the various other registries detailing the use of the IPv6 address space can be found in the IPv6 Address Space registry [IANA registry ipv6-address-space].
The assignable Global Unicast Address space is defined in [RFC4291] as being the address block defined by the prefix 2000::/3. All address space in this block not listed in the table below is reserved by IANA for future allocation.
This registry is also available in XML and plain text formats.
| Prefix | Designation | Date | Whois | Status | Note |
|---|---|---|---|---|---|
| 2001:0000::/23 | IANA | 1999-07-01 | whois.iana.org | ALLOCATED | [1] |
| 2001:0200::/23 | APNIC | 1999-07-01 | whois.apnic.net | ALLOCATED | |
| 2001:0400::/23 | ARIN | 1999-07-01 | whois.arin.net | ALLOCATED | |
| 2001:0600::/23 | RIPE NCC | 1999-07-01 | whois.ripe.net | ALLOCATED | |
| 2001:0800::/23 | RIPE NCC | 2002-05-02 | whois.ripe.net | ALLOCATED | |
| 2001:0A00::/23 | RIPE NCC | 2002-11-02 | whois.ripe.net | ALLOCATED | |
| 2001:0C00::/23 | APNIC | 2002-05-02 | whois.apnic.net | ALLOCATED | [2] |
| 2001:0E00::/23 | APNIC | 2003-01-01 | whois.apnic.net | ALLOCATED | |
| 2001:1200::/23 | LACNIC | 2002-11-01 | whois.lacnic.net | ALLOCATED | |
| 2001:1400::/23 | RIPE NCC | 2003-02-01 | whois.ripe.net | ALLOCATED | |
| 2001:1600::/23 | RIPE NCC | 2003-07-01 | whois.ripe.net | ALLOCATED | |
| 2001:1800::/23 | ARIN | 2003-04-01 | whois.arin.net | ALLOCATED | |
| 2001:1A00::/23 | RIPE NCC | 2004-01-01 | whois.ripe.net | ALLOCATED | |
| 2001:1C00::/22 | RIPE NCC | 2001-05-04 | whois.ripe.net | ALLOCATED | |
| 2001:2000::/20 | RIPE NCC | 2001-05-04 | whois.ripe.net | ALLOCATED | |
| 2001:3000::/21 | RIPE NCC | 2001-05-04 | whois.ripe.net | ALLOCATED | |
| 2001:3800::/22 | RIPE NCC | 2001-05-04 | whois.ripe.net | ALLOCATED | |
| 2001:3C00::/22 | IANA | RESERVED | [3] | ||
| 2001:4000::/23 | RIPE NCC | 2004-06-11 | whois.ripe.net | ALLOCATED | |
| 2001:4200::/23 | AfriNIC | 2004-06-01 | whois.afrinic.net | ALLOCATED | |
| 2001:4400::/23 | APNIC | 2004-06-11 | whois.apnic.net | ALLOCATED | |
| 2001:4600::/23 | RIPE NCC | 2004-08-17 | whois.ripe.net | ALLOCATED | |
| 2001:4800::/23 | ARIN | 2004-08-24 | whois.arin.net | ALLOCATED | |
| 2001:4A00::/23 | RIPE NCC | 2004-10-15 | whois.ripe.net | ALLOCATED | |
| 2001:4C00::/23 | RIPE NCC | 2004-12-17 | whois.ripe.net | ALLOCATED | |
| 2001:5000::/20 | RIPE NCC | 2004-09-10 | whois.ripe.net | ALLOCATED | |
| 2001:8000::/19 | APNIC | 2004-11-30 | whois.apnic.net | ALLOCATED | |
| 2001:A000::/20 | APNIC | 2004-11-30 | whois.apnic.net | ALLOCATED | |
| 2001:B000::/20 | APNIC | 2006-03-08 | whois.apnic.net | ALLOCATED | |
| 2002:0000::/16 | 6to4 | 2001-02-01 | ALLOCATED | [4] | |
| 2003:0000::/18 | RIPE NCC | 2005-01-12 | whois.ripe.net | ALLOCATED | |
| 2400:0000::/12 | APNIC | 2006-10-03 | whois.apnic.net | ALLOCATED | [7] |
| 2600:0000::/12 | ARIN | 2006-10-03 | whois.arin.net | ALLOCATED | [8] |
| 2610:0000::/23 | ARIN | 2005-11-17 | whois.arin.net | ALLOCATED | |
| 2620:0000::/23 | ARIN | 2006-09-12 | whois.arin.net | ALLOCATED | |
| 2800:0000::/12 | LACNIC | 2006-10-03 | whois.lacnic.net | ALLOCATED | [6] |
| 2A00:0000::/12 | RIPE NCC | 2006-10-03 | whois.ripe.net | ALLOCATED | [5] |
| 2C00:0000::/12 | AfriNIC | 2006-10-03 | whois.afrinic.net | ALLOCATED | |
| 2D00:0000::/8 | IANA | 1999-07-01 | RESERVED | ||
| 2E00:0000::/7 | IANA | 1999-07-01 | RESERVED | ||
| 3000:0000::/4 | IANA | 1999-07-01 | RESERVED | [9] |
| [1] |
IANA Special Purpose Address Block [RFC4773]. See: [IANA registry iana-ipv6-special-registry] |
| [2] |
2001:0DB8::/32 has been assigned as a NON-ROUTABLE
range to be used for documentation purpose [RFC3849].
|
| [3] |
2001:3C00::/22 is reserved for possible future allocation
to the RIPE NCC.
|
| [4] |
2002::/16 is reserved for use in 6to4 deployments [RFC3056]. |
| [5] |
2A00:0000::/21 was originally allocated on 2005-04-19.
2A01:0000::/23 was allocated on 2005-07-14. 2A01:0000::/16 (incorporating
the 2A01:0000::/23) was allocated 2005-12-15. The more recent allocation
(2006-10-03) incorporates these previous allocations.
|
| [6] |
2800:0000::/23 was allocated on 17 Nov 05. The more recent
allocation (2006-10-03) incorporates the previous allocation.
|
| [7] |
2400:0000::/19 was allocated on 2005-05-20. 2400:2000::/19
was allocated on 2005-07-08. 2400:4000::/21 was allocated on 2005-08-08.
2404:0000::/23 was allocated on 2006-01-19. The more recent allocation
(2006-10-03) incorporates all these previous allocations.
|
| [8] |
2600:0000::/22, 2604:0000::/22, 2608:0000::/22 and
260C:0000::/22 were allocated on 2005-04-19. The more recent allocation
(2006-10-03) incorporates all these previous allocations.
|
| [9] |
3FFE:831F::/32 was used for Teredo in some old but widely
distributed networking stacks. This usage is deprecated in favour of 2001::/32,
which was allocated for the purpose in [RFC4380]
|