Allocated but unannounced space
Every block here was allocated or assigned by a regional internet registry, and none of them appeared in any routing table we collected at our last snapshot — neither as a route of their own, nor covered by a larger announcement, nor carved up into more specifics.
“Unannounced” does not mean “unused”
Plenty of allocated space is deliberately kept off the public internet: private interconnects, lab and lawful-intercept ranges, networks reachable only inside one operator, and space held in reserve. Some of it is announced somewhere our collectors cannot see, which is a limit of our vantage points rather than a fact about the block.
It is also a snapshot, not a history: a block announced yesterday and withdrawn this morning appears here today. Nothing on this page means a block is unallocated, available, or free to announce.
Browse by registry
Browse by country
Countries with unannounced space registered through RIPE NCC, largest first.
Unannounced blocks in Netherlands
1,668 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2001:960::/32 | 4.3B × /64 | RIPE NCC | 21st Oct 2002 | |
| 2001:990::/32 | 4.3B × /64 | RIPE NCC | 28th Oct 2002 | |
| 204.152.98.0/24 | 256 | RIPE NCC | 12th Nov 1996 | |
| 205.132.144.0/21 | 2k | RIPE NCC | 2nd May 1995 | |
| 209.16.159.0/24 | 256 | RIPE NCC | 31st Jan 1997 | |
| 209.177.176.0/23 | 512 | RIPE NCC | 4th Jun 2008 | |
| 212.115.104.0/22 | 1k | RIPE NCC | 5th Nov 2018 | |
| 212.16.112.0/20 | 4.1k | RIPE NCC | 13th Aug 1999 | |
| 212.19.232.0/23 | 512 | RIPE NCC | 18th Oct 1999 | |
| 212.19.237.0/24 | 256 | RIPE NCC | 18th Oct 1999 | |
| 212.19.238.0/23 | 512 | RIPE NCC | 18th Oct 1999 | |
| 212.19.240.0/20 | 4.1k | RIPE NCC | 18th Oct 1999 | |
| 212.211.0.0/17 | 32.8k | RIPE NCC | 21st Jul 1998 | |
| 212.47.48.0/24 | 256 | RIPE NCC | 16th Feb 2026 | |
| 212.53.16.0/20 | 4.1k | RIPE NCC | 3rd Apr 1998 | |
| 212.84.0.0/19 | 8.2k | RIPE NCC | 30th Sept 1998 | |
| 212.92.120.0/22 | 1k | RIPE NCC | 3rd Nov 1999 | |
| 213.162.160.0/19 | 8.2k | RIPE NCC | 10th May 2001 | |
| 213.185.86.0/23 | 512 | RIPE NCC | 24th Mar 2000 | |
| 213.185.88.0/21 | 2k | RIPE NCC | 24th Mar 2000 | |
| 213.187.144.0/22 | 1k | RIPE NCC | 18th Feb 2000 | |
| 213.193.193.0/24 | 256 | RIPE NCC | 28th Jun 2002 | |
| 213.193.195.0/24 | 256 | RIPE NCC | 28th Jun 2002 | |
| 213.193.237.0/24 | 256 | RIPE NCC | 28th Jun 2002 | |
| 213.219.40.0/21 | 2k | RIPE NCC | 9th Feb 2000 | |
| 213.222.0.0/19 | 8.2k | RIPE NCC | 4th Nov 1999 | |
| 213.232.216.0/24 | 256 | RIPE NCC | 27th Oct 2020 | |
| 213.239.144.0/21 | 2k | RIPE NCC | 19th Sept 2000 | |
| 213.239.154.0/24 | 256 | RIPE NCC | 19th Sept 2000 | |
| 217.115.224.0/20 | 4.1k | RIPE NCC | 5th Feb 2001 | |
| 217.16.32.0/20 | 4.1k | RIPE NCC | 11th Sept 2000 | |
| 217.18.83.0/24 | 256 | RIPE NCC | 8th Mar 2023 | |
| 217.22.3.0/24 | 256 | RIPE NCC | 26th Jun 2026 | |
| 217.28.135.0/24 | 256 | RIPE NCC | 13th Apr 2022 | |
| 217.28.138.0/24 | 256 | RIPE NCC | 13th Apr 2022 | |
| 217.75.32.0/20 | 4.1k | RIPE NCC | 22nd Dec 2000 | |
| 2a00:1048::/32 | 4.3B × /64 | RIPE NCC | 24th Jun 2009 | |
| 2a00:1388::/32 | 4.3B × /64 | RIPE NCC | 18th Sept 2009 | |
| 2a00:1668::/32 | 4.3B × /64 | RIPE NCC | 13th Nov 2009 | |
| 2a00:1720::/32 | 4.3B × /64 | RIPE NCC | 25th Nov 2009 | |
| 2a00:1848::/32 | 4.3B × /64 | RIPE NCC | 9th Dec 2009 | |
| 2a00:18b0::/29 | 34.4B × /64 | RIPE NCC | 17th Dec 2009 | |
| 2a00:19f0::/32 | 4.3B × /64 | RIPE NCC | 22nd Jan 2010 | |
| 2a00:1c58::/32 | 4.3B × /64 | RIPE NCC | 2nd Mar 2010 | |
| 2a00:4e20::/32 | 4.3B × /64 | RIPE NCC | 28th Feb 2013 | |
| 2a00:4e40::/32 | 4.3B × /64 | RIPE NCC | 2nd Dec 2011 | |
| 2a00:52c0::/32 | 4.3B × /64 | RIPE NCC | 7th Dec 2011 | |
| 2a00:5960::/32 | 4.3B × /64 | RIPE NCC | 15th Mar 2013 | |
| 2a00:5be0::/32 | 4.3B × /64 | RIPE NCC | 19th Mar 2013 | |
| 2a00:5ea0::/29 | 34.4B × /64 | RIPE NCC | 21st Mar 2013 |