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 the most unannounced blocks, largest first.
Unannounced blocks in Netherlands
1,704 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 195.234.173.0/24 | 256 | RIPE NCC |  NL | 26th Sept 2002 |
| 195.234.88.0/23 | 512 | RIPE NCC | NL | 10th Sept 2019 |
| 195.238.68.0/23 | 512 | RIPE NCC | NL | 6th Nov 2019 |
| 195.238.78.0/23 | 512 | RIPE NCC | NL | 6th Nov 2019 |
| 195.242.96.0/23 | 512 | RIPE NCC | NL | 15th Dec 2004 |
| 195.245.246.0/24 | 256 | RIPE NCC | NL | 25th Nov 2019 |
| 195.246.197.0/24 | 256 | RIPE NCC | NL | 25th Nov 2019 |
| 195.248.84.0/24 | 256 | RIPE NCC | NL | 25th Nov 2019 |
| 195.35.67.0/24 | 256 | RIPE NCC | NL | 22nd Nov 2019 |
| 195.35.97.0/24 | 256 | RIPE NCC | NL | 22nd Nov 2019 |
| 195.39.204.0/23 | 512 | RIPE NCC | NL | 4th Nov 2019 |
| 195.42.134.0/23 | 512 | RIPE NCC | NL | 13th Feb 2008 |
| 195.43.158.0/24 | 256 | RIPE NCC | NL | 17th Jun 2008 |
| 195.51.0.0/16 | 65.5k | RIPE NCC | NL | 10th Dec 1996 |
| 195.60.82.128/26 | 64 | RIPE NCC | NL | 5th Feb 2010 |
| 195.60.83.224/27 | 32 | RIPE NCC | NL | 16th Mar 2011 |
| 195.60.85.128/26 | 64 | RIPE NCC | NL | 18th Mar 2026 |
| 195.60.87.0/25 | 128 | RIPE NCC | NL | 26th Jun 2007 |
| 195.78.84.0/23 | 512 | RIPE NCC | NL | 8th Sept 2006 |
| 195.8.47.0/24 | 256 | RIPE NCC | NL | 18th May 2020 |
| 195.88.212.0/24 | 256 | RIPE NCC | NL | 2nd Sept 2024 |
| 195.88.226.0/23 | 512 | RIPE NCC | NL | 5th Nov 2019 |
| 195.95.192.0/22 | 1k | RIPE NCC | NL | 4th Nov 2004 |
| 195.95.196.0/23 | 512 | RIPE NCC | NL | 4th Nov 2004 |
| 195.95.244.0/24 | 256 | RIPE NCC | NL | 19th Nov 2004 |
| 195.96.96.0/19 | 8.2k | RIPE NCC | NL | 12th Mar 1997 |
| 198.17.180.0/24 | 256 | RIPE NCC | NL | 12th Jan 1993 |
| 198.17.181.0/24 | 256 | RIPE NCC | NL | 12th Jan 1993 |
| 198.17.182.0/24 | 256 | RIPE NCC | NL | 12th Jan 1993 |
| 198.200.0.0/24 | 256 | APNIC | NL | 21st Jun 1993 |
| 198.200.4.0/24 | 256 | APNIC | NL | 21st Jun 1993 |
| 198.200.5.0/24 | 256 | APNIC | NL | 10th Aug 1993 |
| 198.200.6.0/23 | 512 | APNIC | NL | 10th Aug 1993 |
| 198.200.8.0/23 | 512 | APNIC | NL | 10th Aug 1993 |
| 198.228.101.0/24 | 256 | RIPE NCC | NL | 25th Feb 2025 |
| 198.228.102.0/23 | 512 | RIPE NCC | NL | 25th Feb 2025 |
| 199.103.12.0/24 | 256 | RIPE NCC | NL | 11th Jan 1994 |
| 199.212.91.0/24 | 256 | ARIN | NL | 23rd Mar 1994 |
| 2.56.192.0/22 | 1k | RIPE NCC | NL | 15th Mar 2019 |
| 2.57.12.0/22 | 1k | RIPE NCC | NL | 15th Mar 2019 |
| 2001:1668::/32 | 4.3B × /64 | RIPE NCC | NL | 3rd Dec 2003 |
| 2001:1be8::/32 | 4.3B × /64 | RIPE NCC | NL | 1st Jun 2004 |
| 2001:3f00::/32 | 4.3B × /64 | RIPE NCC | NL | 6th Aug 2024 |
| 2001:4120::/32 | 4.3B × /64 | RIPE NCC | NL | 16th Sept 2004 |
| 2001:4128::/29 | 34.4B × /64 | RIPE NCC | NL | 21st Sept 2004 |
| 2001:504:34::/48 | 65.5k × /64 | ARIN | NL | 13th Dec 2013 |
| 2001:504:38::/48 | 65.5k × /64 | ARIN | NL | 11th Mar 2014 |
| 2001:504:3d::/48 | 65.5k × /64 | ARIN | NL | 26th Jun 2014 |
| 2001:678:1078::/48 | 65.5k × /64 | RIPE NCC | NL | 21st May 2025 |
| 2001:678:10c0::/48 | 65.5k × /64 | RIPE NCC | NL | 4th Jul 2025 |