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 Poland
920 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.41.199.0/24 | 256 | RIPE NCC |  PL | 14th Nov 2019 |
| 193.41.231.0/24 | 256 | RIPE NCC | PL | 16th Jan 2001 |
| 193.41.91.0/24 | 256 | RIPE NCC | PL | 14th Nov 2019 |
| 193.41.92.0/24 | 256 | RIPE NCC | PL | 14th Nov 2019 |
| 193.42.147.0/24 | 256 | RIPE NCC | PL | 17th Sept 2008 |
| 193.43.0.128/25 | 128 | RIPE NCC | PL | 31st May 2012 |
| 193.43.181.0/24 | 256 | RIPE NCC | PL | 10th Dec 2004 |
| 193.56.104.0/23 | 512 | RIPE NCC | PL | 10th Oct 2019 |
| 193.58.232.0/24 | 256 | RIPE NCC | PL | 4th Apr 2005 |
| 193.8.2.0/23 | 512 | RIPE NCC | PL | 4th Oct 2019 |
| 193.8.54.0/23 | 512 | RIPE NCC | PL | 4th Oct 2019 |
| 193.84.79.0/24 | 256 | RIPE NCC | PL | 16th Feb 2006 |
| 193.93.144.0/22 | 1k | RIPE NCC | PL | 6th Apr 2006 |
| 194.0.211.0/24 | 256 | RIPE NCC | PL | 6th Feb 2007 |
| 194.11.22.0/24 | 256 | RIPE NCC | PL | 3rd Jun 2008 |
| 194.110.26.0/24 | 256 | RIPE NCC | PL | 18th Jul 2007 |
| 194.116.134.0/23 | 512 | RIPE NCC | PL | 5th Jan 2005 |
| 194.116.252.0/23 | 512 | RIPE NCC | PL | 4th Mar 2005 |
| 194.117.240.0/23 | 512 | RIPE NCC | PL | 14th Sept 2005 |
| 194.126.210.0/24 | 256 | RIPE NCC | PL | 4th Feb 2005 |
| 194.126.221.0/24 | 256 | RIPE NCC | PL | 10th Feb 2005 |
| 194.126.254.0/24 | 256 | RIPE NCC | PL | 23rd Feb 2009 |
| 194.145.204.0/23 | 512 | RIPE NCC | PL | 30th Mar 2005 |
| 194.145.228.0/24 | 256 | RIPE NCC | PL | 9th Nov 2004 |
| 194.146.128.0/22 | 1k | RIPE NCC | PL | 7th Oct 2003 |
| 194.147.108.0/24 | 256 | RIPE NCC | PL | 29th Feb 2012 |
| 194.150.238.0/23 | 512 | RIPE NCC | PL | 6th Jul 2004 |
| 194.153.134.0/24 | 256 | RIPE NCC | PL | 19th Aug 2004 |
| 194.153.159.0/26 | 64 | RIPE NCC | PL | 22nd Aug 2002 |
| 194.169.127.0/24 | 256 | RIPE NCC | PL | 28th Nov 2006 |
| 194.176.101.0/24 | 256 | RIPE NCC | PL | 20th Jul 2006 |
| 194.176.102.0/24 | 256 | RIPE NCC | PL | 20th Jul 2006 |
| 194.180.220.0/22 | 1k | RIPE NCC | PL | 31st May 2018 |
| 194.180.226.0/26 | 64 | RIPE NCC | PL | 19th Dec 2025 |
| 194.180.226.64/26 | 64 | RIPE NCC | PL | 19th Dec 2025 |
| 194.187.116.0/24 | 256 | RIPE NCC | PL | 21st Jul 2021 |
| 194.187.180.0/22 | 1k | RIPE NCC | PL | 9th Sept 2005 |
| 194.187.52.0/23 | 512 | RIPE NCC | PL | 20th Jul 2005 |
| 194.213.26.0/24 | 256 | RIPE NCC | PL | 2nd Aug 2010 |
| 194.242.0.0/23 | 512 | RIPE NCC | PL | 27th Aug 2009 |
| 194.246.39.0/26 | 64 | RIPE NCC | PL | 19th Dec 2025 |
| 194.33.185.0/24 | 256 | RIPE NCC | PL | 6th Nov 2006 |
| 194.48.1.0/24 | 256 | RIPE NCC | PL | 7th Aug 2023 |
| 194.48.219.0/24 | 256 | RIPE NCC | PL | 24th Jan 2008 |
| 194.50.75.0/24 | 256 | RIPE NCC | PL | 21st Mar 2006 |
| 194.6.204.0/22 | 1k | RIPE NCC | PL | 17th Nov 2005 |
| 194.60.226.0/23 | 512 | RIPE NCC | PL | 2nd Nov 2011 |
| 194.61.57.0/24 | 256 | RIPE NCC | PL | 16th May 2012 |
| 195.128.112.0/21 | 2k | RIPE NCC | PL | 25th Jul 2003 |
| 195.13.46.0/25 | 128 | RIPE NCC | PL | 16th Jan 2001 |