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 Romania
513 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 188.215.3.0/24 | 256 | RIPE NCC | 8th May 2009 | |
| 188.215.4.0/24 | 256 | RIPE NCC | 8th May 2009 | |
| 188.240.221.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.155.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.16.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.18.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.180.0/23 | 512 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.195.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.2.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.252.0/22 | 1k | RIPE NCC | 23rd Jun 2009 | |
| 188.241.38.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.69.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.241.85.0/24 | 256 | RIPE NCC | 23rd Jun 2009 | |
| 188.65.16.0/22 | 1k | RIPE NCC | 5th Jul 2018 | |
| 188.92.27.0/24 | 256 | RIPE NCC | 9th Jan 2024 | |
| 192.144.24.0/22 | 1k | RIPE NCC | 23rd Nov 2018 | |
| 192.145.100.0/22 | 1k | RIPE NCC | 10th Dec 2018 | |
| 193.104.106.0/24 | 256 | RIPE NCC | 15th Aug 2011 | |
| 193.104.21.0/24 | 256 | RIPE NCC | 5th Oct 2009 | |
| 193.105.140.0/24 | 256 | RIPE NCC | 18th Feb 2010 | |
| 193.105.78.0/24 | 256 | RIPE NCC | 15th Aug 2011 | |
| 193.106.149.0/24 | 256 | RIPE NCC | 19th Oct 2022 | |
| 193.106.44.0/22 | 1k | RIPE NCC | 3rd Dec 2009 | |
| 193.111.232.0/24 | 256 | RIPE NCC | 15th May 2002 | |
| 193.111.68.0/23 | 512 | RIPE NCC | 24th Nov 2005 | |
| 193.142.205.0/24 | 256 | RIPE NCC | 18th Nov 2019 | |
| 193.142.223.0/24 | 256 | RIPE NCC | 18th Nov 2019 | |
| 193.142.234.0/24 | 256 | RIPE NCC | 18th Nov 2019 | |
| 193.17.195.0/24 | 256 | RIPE NCC | 1st Oct 2004 | |
| 193.176.35.0/24 | 256 | RIPE NCC | 6th Aug 2025 | |
| 193.189.70.0/23 | 512 | RIPE NCC | 11th Apr 2005 | |
| 193.201.146.128/25 | 128 | RIPE NCC | 14th Jul 2010 | |
| 193.201.154.128/25 | 128 | RIPE NCC | 11th Apr 2005 | |
| 193.201.161.0/24 | 256 | RIPE NCC | 2nd Jul 2002 | |
| 193.203.114.0/23 | 512 | RIPE NCC | 3rd Jun 2008 | |
| 193.228.12.0/22 | 1k | RIPE NCC | 9th May 2018 | |
| 193.239.138.0/23 | 512 | RIPE NCC | 8th Apr 2008 | |
| 193.26.136.0/21 | 2k | RIPE NCC | 11th Mar 1993 | |
| 193.26.7.0/24 | 256 | RIPE NCC | 14th Sept 2004 | |
| 193.27.64.0/23 | 512 | RIPE NCC | 6th Feb 2004 | |
| 193.30.28.0/24 | 256 | RIPE NCC | 7th May 2012 | |
| 193.34.156.0/23 | 512 | RIPE NCC | 23rd Oct 2006 | |
| 193.37.52.0/22 | 1k | RIPE NCC | 12th Sept 2018 | |
| 193.38.240.0/22 | 1k | RIPE NCC | 23rd Oct 2018 | |
| 193.39.117.0/24 | 256 | RIPE NCC | 31st Oct 2006 | |
| 193.39.73.0/24 | 256 | RIPE NCC | 26th Oct 2006 | |
| 193.39.88.0/22 | 1k | RIPE NCC | 13th Jul 2018 | |
| 193.46.91.0/24 | 256 | RIPE NCC | 9th Aug 2007 | |
| 193.47.144.0/24 | 256 | RIPE NCC | 20th Jul 2005 | |
| 193.47.236.0/22 | 1k | RIPE NCC | 30th Apr 2018 |