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
84,954 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 5.159.240.0/21 | 2k | RIPE NCC |  ES | 30th Jul 2012 |
| 5.159.80.0/20 | 4.1k | RIPE NCC |  DE | 27th Jul 2012 |
| 5.172.100.0/22 | 1k | RIPE NCC |  IT | 30th Jul 2012 |
| 5.172.104.0/21 | 2k | RIPE NCC | IT | 30th Jul 2012 |
| 5.172.112.0/20 | 4.1k | RIPE NCC | IT | 30th Jul 2012 |
| 5.178.126.0/23 | 512 | RIPE NCC | IT | 7th Aug 2012 |
| 5.179.96.0/20 | 4.1k | ARIN |  US | 4th Dec 2024 |
| 5.180.156.0/22 | 1k | RIPE NCC | DE | 29th Mar 2019 |
| 5.180.160.0/22 | 1k | RIPE NCC |  NL | 29th Mar 2019 |
| 5.180.176.0/24 | 256 | RIPE NCC |  UA | 19th May 2021 |
| 5.180.88.0/22 | 1k | RIPE NCC | DE | 29th Mar 2019 |
| 5.181.13.0/24 | 256 | RIPE NCC |  CH | 1st Apr 2019 |
| 5.181.148.0/22 | 1k | RIPE NCC |  AT | 2nd Apr 2019 |
| 5.181.17.0/24 | 256 | RIPE NCC |  TR | 1st Apr 2019 |
| 5.181.220.0/22 | 1k | RIPE NCC | ES | 3rd Apr 2019 |
| 5.182.104.0/23 | 512 | RIPE NCC |  DK | 5th Apr 2019 |
| 5.182.246.0/24 | 256 | RIPE NCC | TR | 9th Apr 2019 |
| 5.182.36.0/22 | 1k | RIPE NCC |  RU | 4th Apr 2019 |
| 5.182.61.0/24 | 256 | RIPE NCC | CH | 21st Jan 2026 |
| 5.182.63.0/24 | 256 | RIPE NCC | DE | 21st Jan 2026 |
| 5.182.76.0/22 | 1k | RIPE NCC |  GB | 5th Apr 2019 |
| 5.183.112.0/22 | 1k | RIPE NCC | GB | 10th Apr 2019 |
| 5.183.150.0/24 | 256 | RIPE NCC | ES | 11th Apr 2019 |
| 5.183.160.0/24 | 256 | RIPE NCC | TR | 14th Jan 2025 |
| 5.183.163.0/24 | 256 | RIPE NCC |  SM | 14th Jan 2025 |
| 5.183.236.0/22 | 1k | RIPE NCC |  BE | 11th Apr 2019 |
| 5.183.244.0/22 | 1k | RIPE NCC | AT | 11th Apr 2019 |
| 5.183.32.0/22 | 1k | RIPE NCC | DE | 10th Apr 2019 |
| 5.187.34.0/24 | 256 | RIPE NCC |  CZ | 9th Aug 2012 |
| 5.187.36.0/23 | 512 | RIPE NCC | CH | 9th Aug 2012 |
| 5.198.132.0/22 | 1k | RIPE NCC | CZ | 24th Aug 2012 |
| 5.207.0.0/16 | 65.5k | RIPE NCC | UA | 5th Sept 2012 |
| 5.220.0.0/15 | 131k | RIPE NCC |  IR | 4th Sept 2012 |
| 5.222.0.0/17 | 32.8k | RIPE NCC | DE | 4th Sept 2012 |
| 5.222.128.0/17 | 32.8k | RIPE NCC | DE | 4th Sept 2012 |
| 5.252.136.0/22 | 1k | RIPE NCC | CH | 5th Feb 2019 |
| 5.252.140.0/22 | 1k | RIPE NCC | DE | 5th Feb 2019 |
| 5.252.208.0/22 | 1k | RIPE NCC | GB | 6th Feb 2019 |
| 5.253.108.0/22 | 1k | RIPE NCC | GB | 8th Feb 2019 |
| 5.253.116.0/22 | 1k | RIPE NCC |  RO | 8th Feb 2019 |
| 5.253.160.0/22 | 1k | RIPE NCC |  BZ | 8th Feb 2019 |
| 5.253.225.0/24 | 256 | RIPE NCC | IR | 24th Jan 2022 |
| 5.253.226.0/24 | 256 | RIPE NCC | NL | 24th Jan 2022 |
| 5.253.231.0/24 | 256 | RIPE NCC | BE | 11th Feb 2019 |
| 5.253.232.0/22 | 1k | RIPE NCC | DE | 11th Feb 2019 |
| 5.253.236.0/22 | 1k | RIPE NCC | DE | 11th Feb 2019 |
| 5.253.68.0/22 | 1k | RIPE NCC |  PS | 7th Feb 2019 |
| 5.253.96.0/22 | 1k | RIPE NCC | IR | 8th Feb 2019 |
| 5.255.152.0/21 | 2k | RIPE NCC | NL | 14th Sept 2012 |
| 5.255.60.0/24 | 256 | RIPE NCC | GB | 14th Sept 2012 |