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 |
|---|---|---|---|---|
| 193.177.167.0/24 | 256 | RIPE NCC |  NL | 9th Aug 1995 |
| 193.177.183.0/24 | 256 | RIPE NCC | NL | 8th Dec 1993 |
| 193.177.184.0/22 | 1k | RIPE NCC | NL | 4th Aug 1993 |
| 193.177.2.0/23 | 512 | RIPE NCC | NL | 3rd May 1993 |
| 193.177.224.0/21 | 2k | RIPE NCC | NL | 2nd Nov 1993 |
| 193.177.248.0/21 | 2k | RIPE NCC | NL | 30th Oct 1995 |
| 193.177.32.0/19 | 8.2k | RIPE NCC | NL | 3rd May 1993 |
| 193.177.4.0/22 | 1k | RIPE NCC | NL | 3rd May 1993 |
| 193.177.64.0/18 | 16.4k | RIPE NCC | NL | 3rd May 1993 |
| 193.177.8.0/21 | 2k | RIPE NCC | NL | 3rd May 1993 |
| 193.178.189.0/24 | 256 | RIPE NCC | NL | 29th Jul 2002 |
| 193.187.124.0/22 | 1k | RIPE NCC | NL | 26th Oct 2018 |
| 193.188.134.0/26 | 64 | RIPE NCC | NL | 15th May 1996 |
| 193.200.174.0/24 | 256 | RIPE NCC | NL | 14th May 2007 |
| 193.200.198.0/24 | 256 | RIPE NCC | NL | 23rd May 2007 |
| 193.200.70.0/23 | 512 | RIPE NCC | NL | 1st Mar 2007 |
| 193.201.104.0/24 | 256 | RIPE NCC | NL | 20th Jun 2002 |
| 193.201.147.64/27 | 32 | RIPE NCC | NL | 4th Jul 2003 |
| 193.201.148.192/26 | 64 | RIPE NCC | NL | 27th Aug 2010 |
| 193.201.157.128/26 | 64 | RIPE NCC | NL | 29th Jan 2025 |
| 193.201.47.0/24 | 256 | RIPE NCC | NL | 18th Aug 2026 |
| 193.202.104.0/24 | 256 | RIPE NCC | NL | 21st Jun 1993 |
| 193.219.116.0/24 | 256 | RIPE NCC | NL | 29th Sept 2006 |
| 193.22.102.0/24 | 256 | RIPE NCC | NL | 17th Nov 2003 |
| 193.222.132.0/24 | 256 | RIPE NCC | NL | 18th Aug 2005 |
| 193.238.161.0/24 | 256 | RIPE NCC | NL | 6th Apr 2005 |
| 193.239.116.0/22 | 1k | RIPE NCC | NL | 11th Jul 2005 |
| 193.24.112.0/24 | 256 | RIPE NCC | NL | 2nd Jul 2024 |
| 193.242.119.0/24 | 256 | RIPE NCC | NL | 22nd Dec 2004 |
| 193.26.29.0/24 | 256 | RIPE NCC | NL | 29th Sept 2004 |
| 193.27.16.0/23 | 512 | RIPE NCC | NL | 7th Oct 2019 |
| 193.27.226.0/23 | 512 | RIPE NCC | NL | 19th Jan 2004 |
| 193.27.74.0/23 | 512 | RIPE NCC | NL | 12th Feb 2004 |
| 193.27.76.0/23 | 512 | RIPE NCC | NL | 7th Oct 2019 |
| 193.28.206.0/24 | 256 | RIPE NCC | NL | 23rd Mar 2004 |
| 193.28.220.0/22 | 1k | RIPE NCC | NL | 25th Apr 2018 |
| 193.28.42.0/24 | 256 | RIPE NCC | NL | 12th Feb 2004 |
| 193.29.248.0/23 | 512 | RIPE NCC | NL | 7th Oct 2019 |
| 193.29.26.0/24 | 256 | RIPE NCC | NL | 13th Nov 2019 |
| 193.32.19.0/24 | 256 | RIPE NCC | NL | 3rd Oct 2006 |
| 193.33.157.0/24 | 256 | RIPE NCC | NL | 3rd May 2023 |
| 193.33.35.0/24 | 256 | RIPE NCC | NL | 20th Feb 2023 |
| 193.33.97.0/24 | 256 | RIPE NCC | NL | 31st May 2021 |
| 193.34.199.0/25 | 128 | RIPE NCC | NL | 20th Aug 2010 |
| 193.36.152.0/21 | 2k | RIPE NCC | NL | 8th Mar 1993 |
| 193.36.160.0/23 | 512 | RIPE NCC | NL | 8th Mar 1993 |
| 193.36.75.0/24 | 256 | RIPE NCC | NL | 8th Mar 1993 |
| 193.36.87.0/24 | 256 | RIPE NCC | NL | 3rd Mar 1993 |
| 193.42.212.0/24 | 256 | RIPE NCC | NL | 4th Jan 2005 |
| 193.43.89.0/24 | 256 | RIPE NCC | NL | 15th Dec 2004 |