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 Poland
920 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 91.198.80.0/24 | 256 | RIPE NCC | 31st Aug 2007 | |
| 91.199.106.0/24 | 256 | RIPE NCC | 10th Jan 2008 | |
| 91.202.172.0/22 | 1k | RIPE NCC | 25th Feb 2008 | |
| 91.203.104.0/24 | 256 | RIPE NCC | 8th Jul 2010 | |
| 91.203.248.0/22 | 1k | RIPE NCC | 20th May 2008 | |
| 91.206.172.0/23 | 512 | RIPE NCC | 4th Aug 2008 | |
| 91.206.90.0/24 | 256 | RIPE NCC | 24th Oct 2011 | |
| 91.207.70.0/24 | 256 | RIPE NCC | 16th Jan 2025 | |
| 91.208.10.0/24 | 256 | RIPE NCC | 1st Jul 2008 | |
| 91.208.106.0/24 | 256 | RIPE NCC | 4th Aug 2008 | |
| 91.208.176.0/23 | 512 | RIPE NCC | 3rd Oct 2019 | |
| 91.209.58.0/24 | 256 | RIPE NCC | 7th Nov 2019 | |
| 91.209.62.0/23 | 512 | RIPE NCC | 3rd Oct 2019 | |
| 91.210.40.0/24 | 256 | RIPE NCC | 1st Jun 2026 | |
| 91.212.135.0/24 | 256 | RIPE NCC | 8th Nov 2019 | |
| 91.212.170.0/24 | 256 | RIPE NCC | 27th Apr 2009 | |
| 91.212.9.0/24 | 256 | RIPE NCC | 27th Jan 2009 | |
| 91.213.206.0/24 | 256 | RIPE NCC | 7th Sept 2009 | |
| 91.213.255.0/24 | 256 | RIPE NCC | 28th Sept 2009 | |
| 91.213.73.0/26 | 64 | RIPE NCC | 2nd Apr 2026 | |
| 91.213.73.128/26 | 64 | RIPE NCC | 2nd Apr 2026 | |
| 91.213.73.192/26 | 64 | RIPE NCC | 2nd Apr 2026 | |
| 91.213.73.64/26 | 64 | RIPE NCC | 2nd Apr 2026 | |
| 91.215.228.0/22 | 1k | RIPE NCC | 27th Aug 2009 | |
| 91.217.204.0/24 | 256 | RIPE NCC | 9th Sept 2010 | |
| 91.218.242.0/23 | 512 | RIPE NCC | 23rd Aug 2010 | |
| 91.220.177.0/24 | 256 | RIPE NCC | 25th Nov 2010 | |
| 91.220.225.0/24 | 256 | RIPE NCC | 10th Dec 2010 | |
| 91.220.32.0/24 | 256 | RIPE NCC | 14th Oct 2010 | |
| 91.221.158.0/23 | 512 | RIPE NCC | 6th Dec 2010 | |
| 91.222.100.0/22 | 1k | RIPE NCC | 9th Dec 2010 | |
| 91.222.224.0/22 | 1k | RIPE NCC | 13th Jan 2011 | |
| 91.223.171.0/24 | 256 | RIPE NCC | 25th Feb 2011 | |
| 91.223.196.0/24 | 256 | RIPE NCC | 4th Mar 2011 | |
| 91.223.6.0/24 | 256 | RIPE NCC | 13th Jan 2011 | |
| 91.223.81.0/24 | 256 | RIPE NCC | 3rd Feb 2011 | |
| 91.224.38.0/23 | 512 | RIPE NCC | 27th Jan 2011 | |
| 91.227.115.0/24 | 256 | RIPE NCC | 2nd Apr 2012 | |
| 91.228.237.0/24 | 256 | RIPE NCC | 9th Jun 2011 | |
| 91.228.80.0/22 | 1k | RIPE NCC | 25th May 2011 | |
| 91.229.40.0/22 | 1k | RIPE NCC | 15th Jun 2011 | |
| 91.230.162.0/23 | 512 | RIPE NCC | 15th Jul 2011 | |
| 91.230.74.0/24 | 256 | RIPE NCC | 6th Jul 2011 | |
| 91.234.144.0/24 | 256 | RIPE NCC | 24th Jan 2012 | |
| 91.235.0.0/23 | 512 | RIPE NCC | 1st Feb 2012 | |
| 91.235.228.0/23 | 512 | RIPE NCC | 17th Feb 2012 | |
| 91.236.105.0/24 | 256 | RIPE NCC | 1st Mar 2012 | |
| 91.236.187.0/24 | 256 | RIPE NCC | 13th Mar 2012 | |
| 91.236.229.0/24 | 256 | RIPE NCC | 15th Mar 2012 | |
| 91.237.18.0/23 | 512 | RIPE NCC | 19th Mar 2012 |