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 Bulgaria
275 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 109.160.104.0/21 | 2k | RIPE NCC |  BG | 27th Aug 2009 |
| 109.206.236.0/24 | 256 | RIPE NCC | BG | 12th Oct 2018 |
| 121.127.36.0/24 | 256 | RIPE NCC | BG | 9th Oct 2007 |
| 141.226.84.0/23 | 512 | RIPE NCC | BG | 5th Aug 1990 |
| 141.226.86.0/24 | 256 | RIPE NCC | BG | 5th Aug 1990 |
| 171.22.19.0/24 | 256 | RIPE NCC | BG | 30th Jan 2019 |
| 178.215.224.0/24 | 256 | RIPE NCC | BG | 4th Sept 2018 |
| 185.0.28.0/24 | 256 | RIPE NCC | BG | 26th May 2023 |
| 185.1.137.0/24 | 256 | RIPE NCC | BG | 5th Jun 2019 |
| 185.1.156.0/24 | 256 | RIPE NCC | BG | 13th Dec 2019 |
| 185.1.30.0/24 | 256 | RIPE NCC | BG | 2nd Sept 2014 |
| 185.1.40.0/24 | 256 | RIPE NCC | BG | 27th Feb 2015 |
| 185.148.60.0/22 | 1k | RIPE NCC | BG | 19th Apr 2016 |
| 185.186.112.0/22 | 1k | RIPE NCC | BG | 18th Jan 2017 |
| 185.188.228.0/22 | 1k | RIPE NCC | BG | 7th Feb 2017 |
| 185.201.170.0/24 | 256 | RIPE NCC | BG | 22nd Jan 2026 |
| 185.208.48.0/22 | 1k | RIPE NCC | BG | 13th Jun 2017 |
| 185.209.80.0/24 | 256 | RIPE NCC | BG | 5th Nov 2020 |
| 185.214.248.0/22 | 1k | RIPE NCC | BG | 26th Jul 2017 |
| 185.236.236.0/22 | 1k | RIPE NCC | BG | 14th Dec 2017 |
| 185.240.152.0/22 | 1k | RIPE NCC | BG | 10th Jan 2018 |
| 185.242.168.0/22 | 1k | RIPE NCC | BG | 19th Jan 2018 |
| 185.243.236.0/22 | 1k | RIPE NCC | BG | 30th Jan 2018 |
| 185.243.248.0/22 | 1k | RIPE NCC | BG | 30th Jan 2018 |
| 185.251.108.0/23 | 512 | RIPE NCC | BG | 23rd Mar 2018 |
| 185.251.110.0/23 | 512 | RIPE NCC | BG | 23rd Mar 2018 |
| 185.251.183.0/24 | 256 | RIPE NCC | BG | 11th Mar 2021 |
| 185.252.179.0/24 | 256 | RIPE NCC | BG | 28th Mar 2018 |
| 185.40.164.0/22 | 1k | RIPE NCC | BG | 15th Nov 2013 |
| 185.49.88.0/22 | 1k | RIPE NCC | BG | 28th Feb 2014 |
| 185.5.116.0/22 | 1k | RIPE NCC | BG | 2nd Oct 2012 |
| 185.64.20.0/22 | 1k | RIPE NCC | BG | 16th Jul 2014 |
| 185.65.117.0/24 | 256 | RIPE NCC | BG | 9th Mar 2026 |
| 185.73.236.0/22 | 1k | RIPE NCC | BG | 21st Oct 2014 |
| 188.92.2.0/24 | 256 | RIPE NCC | BG | 25th Jun 2024 |
| 193.169.198.0/23 | 512 | RIPE NCC | BG | 30th Jul 2009 |
| 193.169.31.0/24 | 256 | RIPE NCC | BG | 22nd May 2009 |
| 193.200.14.0/23 | 512 | RIPE NCC | BG | 7th Feb 1996 |
| 193.228.172.0/23 | 512 | RIPE NCC | BG | 16th Oct 2019 |
| 193.228.182.0/23 | 512 | RIPE NCC | BG | 16th Oct 2019 |
| 193.24.240.0/22 | 1k | RIPE NCC | BG | 20th Feb 2004 |
| 193.3.63.0/24 | 256 | RIPE NCC | BG | 2nd Sept 2020 |
| 193.41.182.0/23 | 512 | RIPE NCC | BG | 17th Jan 2001 |
| 194.104.132.0/24 | 256 | RIPE NCC | BG | 30th Sept 2021 |
| 194.145.160.0/22 | 1k | RIPE NCC | BG | 24th Aug 2004 |
| 194.147.223.0/24 | 256 | RIPE NCC | BG | 18th Nov 2022 |
| 194.32.210.0/24 | 256 | RIPE NCC | BG | 1st Oct 2024 |
| 194.41.10.0/23 | 512 | RIPE NCC | BG | 22nd Oct 2019 |
| 194.42.47.0/26 | 64 | RIPE NCC | BG | 28th Feb 2025 |
| 194.48.202.0/24 | 256 | RIPE NCC | BG | 3rd May 2023 |