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 |
|---|---|---|---|---|
| 87.58.0.0/19 | 8.2k | RIPE NCC |  NL | 20th May 2005 |
| 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.30.240.0/20 | 4.1k | RIPE NCC | NL | 1st Sept 2006 |
| 89.32.42.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.33.81.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.193.115.0/24 | 256 | RIPE NCC | NL | 15th May 2020 |
| 91.194.218.0/23 | 512 | RIPE NCC | NL | 16th Jul 2007 |
| 91.195.160.0/23 | 512 | RIPE NCC | NL | 25th Sept 2007 |
| 91.195.236.0/23 | 512 | RIPE NCC | NL | 23rd Oct 2007 |
| 91.198.151.0/24 | 256 | RIPE NCC | NL | 25th Sept 2007 |
| 91.198.152.0/24 | 256 | RIPE NCC | NL | 25th Sept 2007 |
| 91.199.135.0/24 | 256 | RIPE NCC | NL | 24th Jan 2008 |
| 91.203.148.0/22 | 1k | RIPE NCC | NL | 22nd Apr 2008 |
| 91.203.76.0/22 | 1k | RIPE NCC | NL | 19th Apr 2018 |
| 91.204.83.0/24 | 256 | RIPE NCC | NL | 4th Jun 2008 |
| 91.206.232.0/23 | 512 | RIPE NCC | NL | 28th Aug 2008 |
| 91.206.94.0/24 | 256 | RIPE NCC | NL | 13th Mar 2023 |
| 91.207.182.0/24 | 256 | RIPE NCC | NL | 23rd Jan 2023 |
| 91.208.110.0/24 | 256 | RIPE NCC | NL | 7th Aug 2008 |
| 91.208.196.0/24 | 256 | RIPE NCC | NL | 9th Sept 2008 |
| 91.208.241.0/24 | 256 | RIPE NCC | NL | 26th Sept 2008 |
| 91.208.49.0/24 | 256 | RIPE NCC | NL | 11th Jul 2008 |
| 91.208.67.0/24 | 256 | RIPE NCC | NL | 27th Sept 2023 |
| 91.208.77.0/24 | 256 | RIPE NCC | NL | 15th May 2023 |
| 91.209.117.0/24 | 256 | RIPE NCC | NL | 25th Aug 2025 |
| 91.209.164.0/24 | 256 | RIPE NCC | NL | 1st Oct 2010 |
| 91.209.43.0/24 | 256 | RIPE NCC | NL | 21st Aug 2024 |
| 91.211.162.0/23 | 512 | RIPE NCC | NL | 20th Apr 2018 |
| 91.211.72.0/22 | 1k | RIPE NCC | NL | 5th Dec 2008 |
| 91.212.122.0/24 | 256 | RIPE NCC | NL | 25th Jan 2022 |
| 91.212.14.0/24 | 256 | RIPE NCC | NL | 27th Jan 2026 |
| 91.212.222.0/24 | 256 | RIPE NCC | NL | 27th May 2009 |
| 91.213.111.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |
| 91.213.211.128/26 | 64 | RIPE NCC | NL | 3rd Jun 2026 |
| 91.213.72.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |
| 91.213.93.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |
| 91.213.94.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |