Uzbekistan (UZ) - IPv6 address delegations
Data from RIR websites as of: Mon Nov 25 2024
Column "Number" corresponds to the number of /48 blocks composing each IPv6 address delegation.
| RIPE NCC Delegations |
| Zone |
Country code |
Parameter |
Range start |
Prefix |
Number |
Date |
Status |
| RIPE NCC |
UZ |
IPv6 |
2a00:8840:: |
/29 |
524 288 |
2012-01-30 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a02:a98:: |
/32 |
65 536 |
2009-02-24 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a02:f10:: |
/32 |
65 536 |
2009-05-25 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a02:c8c0:: |
/29 |
524 288 |
2012-09-26 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a02:dec0:: |
/29 |
524 288 |
2024-01-16 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a02:f7c0:: |
/29 |
524 288 |
2015-10-06 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a03:540:: |
/32 |
65 536 |
2012-10-04 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a03:1020:: |
/32 |
65 536 |
2014-07-15 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a03:3240:: |
/32 |
65 536 |
2012-10-26 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a03:46e0:: |
/32 |
65 536 |
2014-10-22 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a03:8ee0:: |
/32 |
65 536 |
2015-03-23 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a04:1b80:: |
/32 |
65 536 |
2018-06-07 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a05:45c0:: |
/29 |
524 288 |
2014-10-20 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a06:88c0:: |
/32 |
65 536 |
2024-11-04 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a07:edc0:: |
/29 |
524 288 |
2018-07-06 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a09:5c00:: |
/29 |
524 288 |
2018-11-02 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a09:6700:: |
/29 |
524 288 |
2018-11-16 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a09:adc0:: |
/29 |
524 288 |
2019-03-06 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a09:c040:: |
/29 |
524 288 |
2019-03-13 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a09:f380:: |
/29 |
524 288 |
2018-12-28 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0a:bc0:: |
/29 |
524 288 |
2024-04-22 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0b:1c80:: |
/29 |
524 288 |
2016-12-29 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0b:4f80:: |
/29 |
524 288 |
2020-01-16 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0b:9540:: |
/29 |
524 288 |
2017-07-24 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0c:5d80:: |
/29 |
524 288 |
2018-01-04 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0c:fd40:: |
/29 |
524 288 |
2018-07-31 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0d:d140:: |
/29 |
524 288 |
2018-10-17 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0e:17c0:: |
/29 |
524 288 |
2019-06-28 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0e:9f00:: |
/29 |
524 288 |
2019-04-30 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0f:7f40:: |
/29 |
524 288 |
2019-11-14 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a0f:f440:: |
/32 |
65 536 |
2019-12-17 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a10:8ec0:: |
/32 |
65 536 |
2021-02-12 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a12:5080:: |
/29 |
524 288 |
2021-11-23 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a12:6b40:: |
/29 |
524 288 |
2022-02-07 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a13:98c0:: |
/29 |
524 288 |
2023-07-21 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a13:9fc0:: |
/29 |
524 288 |
2023-08-01 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a13:f100:: |
/29 |
524 288 |
2023-02-21 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a14:4a00:: |
/29 |
524 288 |
2023-10-31 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2a14:51c0:: |
/29 |
524 288 |
2024-05-21 |
Allocated |
| RIPE NCC |
UZ |
IPv6 |
2001:678:188:: |
/48 |
1 |
2016-05-02 |
Assigned |
| RIPE NCC |
UZ |
IPv6 |
2001:678:c3c:: |
/48 |
1 |
2021-02-09 |
Assigned |
| RIPE NCC |
UZ |
IPv6 |
2001:67c:db4:: |
/48 |
1 |
2024-01-31 |
Assigned |
| RIPE NCC |
UZ |
IPv6 |
2001:7f8:110:: |
/48 |
1 |
2023-02-24 |
Assigned |
| RIPE NCC |
UZ |
IPv6 |
2001:7f8:131:: |
/48 |
1 |
2022-08-02 |
Assigned |
| RIPE NCC |
UZ |
IPv6 |
2001:7f8:14f:: |
/48 |
1 |
2023-08-04 |
Assigned |
