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 Czechia
299 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 109.107.158.0/24 | 256 | RIPE NCC | 22nd Oct 2021 | |
| 153.76.176.0/23 | 512 | RIPE NCC | 23rd Sept 1991 | |
| 153.76.180.0/22 | 1k | RIPE NCC | 23rd Sept 1991 | |
| 153.76.184.0/21 | 2k | RIPE NCC | 23rd Sept 1991 | |
| 171.25.176.0/24 | 256 | RIPE NCC | 12th Jan 2012 | |
| 171.33.136.0/21 | 2k | RIPE NCC | 3rd Jul 2012 | |
| 176.106.136.0/21 | 2k | RIPE NCC | 19th Apr 2012 | |
| 176.107.120.0/21 | 2k | RIPE NCC | 31st Jan 2012 | |
| 176.123.184.0/22 | 1k | RIPE NCC | 30th Jul 2012 | |
| 176.97.201.0/24 | 256 | RIPE NCC | 22nd Oct 2021 | |
| 185.0.20.0/23 | 512 | RIPE NCC | 20th Jan 2023 | |
| 185.1.173.0/24 | 256 | RIPE NCC | 9th Jun 2020 | |
| 185.1.25.0/24 | 256 | RIPE NCC | 30th Apr 2014 | |
| 185.1.34.0/24 | 256 | RIPE NCC | 9th Dec 2014 | |
| 185.1.83.0/24 | 256 | RIPE NCC | 31st Jan 2017 | |
| 185.130.209.0/24 | 256 | RIPE NCC | 10th Dec 2015 | |
| 185.130.210.0/23 | 512 | RIPE NCC | 10th Dec 2015 | |
| 185.133.144.0/22 | 1k | RIPE NCC | 5th Jan 2016 | |
| 185.139.218.0/23 | 512 | RIPE NCC | 22nd Feb 2016 | |
| 185.144.176.0/22 | 1k | RIPE NCC | 29th Mar 2016 | |
| 185.152.152.0/22 | 1k | RIPE NCC | 19th May 2016 | |
| 185.153.72.0/22 | 1k | RIPE NCC | 23rd May 2016 | |
| 185.153.80.0/22 | 1k | RIPE NCC | 23rd May 2016 | |
| 185.159.132.0/22 | 1k | RIPE NCC | 14th Jul 2016 | |
| 185.161.252.0/22 | 1k | RIPE NCC | 3rd Aug 2016 | |
| 185.162.4.0/22 | 1k | RIPE NCC | 4th Aug 2016 | |
| 185.167.64.0/22 | 1k | RIPE NCC | 9th Sept 2016 | |
| 185.167.68.0/22 | 1k | RIPE NCC | 9th Sept 2016 | |
| 185.170.240.0/22 | 1k | RIPE NCC | 3rd Oct 2016 | |
| 185.174.92.0/22 | 1k | RIPE NCC | 24th Oct 2016 | |
| 185.181.184.0/22 | 1k | RIPE NCC | 13th Dec 2016 | |
| 185.181.56.0/22 | 1k | RIPE NCC | 8th Dec 2016 | |
| 185.183.8.0/22 | 1k | RIPE NCC | 20th Dec 2016 | |
| 185.187.140.0/22 | 1k | RIPE NCC | 27th Jan 2017 | |
| 185.187.200.0/22 | 1k | RIPE NCC | 30th Jan 2017 | |
| 185.188.184.0/22 | 1k | RIPE NCC | 23rd Feb 2018 | |
| 185.190.89.0/24 | 256 | RIPE NCC | 16th Sept 2020 | |
| 185.194.12.0/24 | 256 | RIPE NCC | 28th Sept 2020 | |
| 185.207.168.0/22 | 1k | RIPE NCC | 9th Jun 2017 | |
| 185.220.28.0/22 | 1k | RIPE NCC | 8th Sept 2017 | |
| 185.255.240.0/22 | 1k | RIPE NCC | 16th Apr 2018 | |
| 185.31.203.0/24 | 256 | RIPE NCC | 5th Dec 2023 | |
| 185.38.188.0/22 | 1k | RIPE NCC | 24th Oct 2013 | |
| 185.44.188.0/22 | 1k | RIPE NCC | 9th Jan 2014 | |
| 185.48.7.0/24 | 256 | RIPE NCC | 11th Aug 2025 | |
| 185.52.174.0/23 | 512 | RIPE NCC | 2nd Apr 2014 | |
| 185.52.96.0/22 | 1k | RIPE NCC | 31st Mar 2014 | |
| 185.54.0.0/23 | 512 | RIPE NCC | 15th Apr 2014 | |
| 185.66.214.0/24 | 256 | RIPE NCC | 27th Jun 2024 | |
| 185.78.56.0/22 | 1k | RIPE NCC | 21st Nov 2014 |