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,590 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 77.95.230.0/24 | 256 | RIPE NCC |  NL | 9th Aug 2011 |
| 77.95.231.0/24 | 256 | RIPE NCC | NL | 9th Aug 2011 |
| 78.111.84.0/22 | 1k | RIPE NCC | NL | 6th Sept 2007 |
| 78.27.0.0/18 | 16.4k | RIPE NCC | NL | 5th Sept 2007 |
| 78.31.48.0/21 | 2k | RIPE NCC | NL | 26th Sept 2007 |
| 78.41.200.0/24 | 256 | RIPE NCC | NL | 23rd Aug 2007 |
| 78.41.201.0/24 | 256 | RIPE NCC | NL | 23rd Aug 2007 |
| 78.41.202.0/24 | 256 | RIPE NCC | NL | 23rd Aug 2007 |
| 78.41.203.0/24 | 256 | RIPE NCC | NL | 23rd Aug 2007 |
| 78.41.204.0/23 | 512 | RIPE NCC | NL | 23rd Aug 2007 |
| 78.41.206.0/24 | 256 | RIPE NCC | NL | 23rd Aug 2007 |
| 79.171.192.0/21 | 2k | RIPE NCC | NL | 17th Oct 2007 |
| 80.247.192.0/20 | 4.1k | RIPE NCC | NL | 13th Nov 2001 |
| 80.247.208.0/21 | 2k | RIPE NCC | NL | 14th Jan 2002 |
| 80.73.136.0/21 | 2k | RIPE NCC | NL | 18th Jun 2001 |
| 80.75.216.0/24 | 256 | RIPE NCC | NL | 9th Jan 2024 |
| 80.75.222.0/24 | 256 | RIPE NCC | NL | 9th Jan 2024 |
| 80.85.88.0/21 | 2k | RIPE NCC | NL | 19th May 2003 |
| 81.173.5.0/24 | 256 | RIPE NCC | NL | 19th Feb 2003 |
| 81.31.216.0/21 | 2k | RIPE NCC | NL | 10th Aug 2012 |
| 81.85.100.0/24 | 256 | RIPE NCC | NL | 30th May 2002 |
| 81.85.52.0/22 | 1k | RIPE NCC | NL | 30th May 2002 |
| 81.85.96.0/22 | 1k | RIPE NCC | NL | 30th May 2002 |
| 83.138.61.0/24 | 256 | RIPE NCC | NL | 3rd Jan 2020 |
| 83.68.0.0/19 | 8.2k | RIPE NCC | NL | 29th Apr 2004 |
| 83.98.160.0/22 | 1k | RIPE NCC | NL | 14th Jan 2004 |
| 83.98.165.0/24 | 256 | RIPE NCC | NL | 14th Jan 2004 |
| 84.252.107.0/24 | 256 | RIPE NCC | NL | 20th Jan 2020 |
| 84.54.40.0/22 | 1k | RIPE NCC | NL | 15th Nov 2018 |
| 85.137.236.0/24 | 256 | RIPE NCC | NL | 3rd Nov 2004 |
| 85.208.132.0/22 | 1k | RIPE NCC | NL | 21st Feb 2019 |
| 86.104.127.0/24 | 256 | RIPE NCC | NL | 18th Apr 2005 |
| 86.48.128.0/18 | 16.4k | RIPE NCC | NL | 14th Apr 2005 |
| 87.236.163.0/24 | 256 | RIPE NCC | NL | 19th Aug 2021 |
| 89.106.204.0/24 | 256 | RIPE NCC | NL | 25th Jan 2022 |
| 89.207.129.0/24 | 256 | RIPE NCC | NL | 5th Dec 2008 |
| 89.207.132.0/24 | 256 | RIPE NCC | NL | 5th Dec 2008 |
| 89.207.133.0/24 | 256 | RIPE NCC | NL | 5th Dec 2008 |
| 89.207.134.0/23 | 512 | RIPE NCC | NL | 5th Dec 2008 |
| 89.32.42.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.35.72.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.36.73.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.40.211.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.40.69.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.47.1.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 91.102.123.0/24 | 256 | RIPE NCC | NL | 13th Apr 2026 |
| 91.108.191.0/24 | 256 | RIPE NCC | NL | 7th Jan 2025 |
| 91.123.240.0/20 | 4.1k | RIPE NCC | NL | 14th May 2007 |
| 91.142.131.0/24 | 256 | RIPE NCC | NL | 8th Apr 2010 |
| 91.142.132.0/24 | 256 | RIPE NCC | NL | 8th Apr 2010 |