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 |
|---|---|---|---|---|
| 77.88.128.0/18 | 16.4k | RIPE NCC |  PL | 15th Mar 2007 |
| 78.108.117.0/24 | 256 | RIPE NCC | PL | 23rd Jun 2026 |
| 78.31.209.0/24 | 256 | RIPE NCC | PL | 10th Sept 2012 |
| 79.139.96.0/20 | 4.1k | RIPE NCC | PL | 22nd Oct 2007 |
| 80.238.64.0/19 | 8.2k | RIPE NCC | PL | 8th May 2006 |
| 83.142.176.0/21 | 2k | RIPE NCC | PL | 25th Nov 2004 |
| 83.142.56.0/21 | 2k | RIPE NCC | PL | 16th Aug 2004 |
| 83.143.160.0/21 | 2k | RIPE NCC | PL | 27th Jun 2005 |
| 83.143.96.0/21 | 2k | RIPE NCC | PL | 30th May 2005 |
| 83.175.136.0/23 | 512 | RIPE NCC | PL | 16th Feb 2006 |
| 83.175.161.0/24 | 256 | RIPE NCC | PL | 10th Jun 2004 |
| 83.175.163.0/24 | 256 | RIPE NCC | PL | 10th Jun 2004 |
| 83.175.164.0/24 | 256 | RIPE NCC | PL | 10th Jun 2004 |
| 84.205.167.0/24 | 256 | RIPE NCC | PL | 3rd Feb 2005 |
| 84.205.180.0/23 | 512 | RIPE NCC | PL | 3rd Feb 2005 |
| 84.234.0.0/20 | 4.1k | RIPE NCC | PL | 6th Jul 2004 |
| 84.234.117.0/24 | 256 | RIPE NCC | PL | 24th Nov 2004 |
| 84.234.32.0/20 | 4.1k | RIPE NCC | PL | 16th Aug 2004 |
| 84.38.96.0/20 | 4.1k | RIPE NCC | PL | 22nd May 2006 |
| 85.202.208.0/20 | 4.1k | RIPE NCC | PL | 6th Feb 2008 |
| 85.204.198.0/24 | 256 | RIPE NCC | PL | 13th Jan 2005 |
| 85.209.36.0/22 | 1k | RIPE NCC | PL | 25th Feb 2019 |
| 86.104.210.0/24 | 256 | RIPE NCC | PL | 18th Apr 2005 |
| 86.105.187.0/24 | 256 | RIPE NCC | PL | 18th Apr 2005 |
| 86.105.215.0/24 | 256 | RIPE NCC | PL | 18th Apr 2005 |
| 87.199.112.0/21 | 2k | RIPE NCC | PL | 28th Jun 2006 |
| 87.199.144.0/22 | 1k | RIPE NCC | PL | 28th Jun 2006 |
| 87.199.156.0/22 | 1k | RIPE NCC | PL | 28th Jun 2006 |
| 87.199.96.0/20 | 4.1k | RIPE NCC | PL | 28th Jun 2006 |
| 87.236.36.0/24 | 256 | RIPE NCC | PL | 8th Mar 2023 |
| 87.239.72.0/21 | 2k | RIPE NCC | PL | 24th Nov 2005 |
| 89.187.224.0/19 | 8.2k | RIPE NCC | PL | 28th Apr 2006 |
| 89.200.152.0/21 | 2k | RIPE NCC | PL | 22nd May 2006 |
| 89.40.21.0/24 | 256 | RIPE NCC | PL | 29th Nov 2005 |
| 89.42.162.0/24 | 256 | RIPE NCC | PL | 29th Nov 2005 |
| 89.44.188.0/24 | 256 | RIPE NCC | PL | 29th Nov 2005 |
| 91.142.137.0/24 | 256 | RIPE NCC | PL | 12th Apr 2010 |
| 91.142.192.0/20 | 4.1k | RIPE NCC | PL | 19th Oct 2006 |
| 91.145.128.0/18 | 16.4k | RIPE NCC | PL | 3rd Oct 2006 |
| 91.146.192.0/18 | 16.4k | RIPE NCC | PL | 24th Oct 2006 |
| 91.150.128.0/19 | 8.2k | RIPE NCC | PL | 19th Dec 2006 |
| 91.192.225.0/24 | 256 | RIPE NCC | PL | 15th Mar 2007 |
| 91.192.248.0/22 | 1k | RIPE NCC | PL | 20th Mar 2007 |
| 91.192.88.0/22 | 1k | RIPE NCC | PL | 13th Feb 2007 |
| 91.193.144.0/22 | 1k | RIPE NCC | PL | 16th Apr 2007 |
| 91.195.250.0/23 | 512 | RIPE NCC | PL | 29th Oct 2007 |
| 91.195.42.0/23 | 512 | RIPE NCC | PL | 21st Aug 2007 |
| 91.198.111.0/24 | 256 | RIPE NCC | PL | 13th Sept 2007 |
| 91.198.222.0/24 | 256 | RIPE NCC | PL | 25th Oct 2007 |
| 91.198.226.0/24 | 256 | RIPE NCC | PL | 26th Oct 2007 |