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
85,239 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.28.186.0/24 | 256 | RIPE NCC |  RU | 12th Jul 2023 |
| 193.28.188.0/24 | 256 | RIPE NCC |  CH | 9th Aug 2004 |
| 193.28.201.0/24 | 256 | RIPE NCC |  GB | 22nd Mar 2004 |
| 193.28.206.0/24 | 256 | RIPE NCC |  NL | 23rd Mar 2004 |
| 193.28.220.0/22 | 1k | RIPE NCC | NL | 25th Apr 2018 |
| 193.28.227.0/24 | 256 | RIPE NCC |  DK | 27th Apr 2004 |
| 193.28.228.0/24 | 256 | RIPE NCC |  DE | 31st Aug 2011 |
| 193.28.239.0/24 | 256 | RIPE NCC |  CA | 26th May 2020 |
| 193.28.252.0/23 | 512 | RIPE NCC | GB | 7th Oct 2019 |
| 193.28.42.0/24 | 256 | RIPE NCC | NL | 12th Feb 2004 |
| 193.28.45.0/24 | 256 | RIPE NCC | GB | 13th Feb 2004 |
| 193.28.47.0/24 | 256 | RIPE NCC |  BE | 16th Feb 2004 |
| 193.28.57.0/24 | 256 | RIPE NCC |  US | 13th Nov 2019 |
| 193.28.6.0/24 | 256 | RIPE NCC | RU | 8th Dec 2008 |
| 193.28.60.0/24 | 256 | RIPE NCC | US | 13th Nov 2019 |
| 193.28.93.0/24 | 256 | RIPE NCC | US | 13th Nov 2019 |
| 193.28.95.0/24 | 256 | RIPE NCC |  IT | 26th Apr 2004 |
| 193.29.0.0/24 | 256 | RIPE NCC | DE | 28th Jul 1993 |
| 193.29.100.0/22 | 1k | RIPE NCC | DE | 10th Sept 2018 |
| 193.29.108.0/22 | 1k | RIPE NCC | GB | 10th Sept 2018 |
| 193.29.128.0/23 | 512 | RIPE NCC | GB | 7th Oct 2019 |
| 193.29.130.0/23 | 512 | RIPE NCC | DE | 28th Jul 1993 |
| 193.29.136.0/23 | 512 | RIPE NCC |  FR | 28th Jul 1993 |
| 193.29.138.0/24 | 256 | RIPE NCC | FR | 28th Jul 1993 |
| 193.29.140.0/22 | 1k | RIPE NCC | FR | 28th Jul 1993 |
| 193.29.160.0/20 | 4.1k | RIPE NCC | GB | 28th Jul 1993 |
| 193.29.176.0/24 | 256 | RIPE NCC |  FI | 28th Jul 1993 |
| 193.29.178.0/23 | 512 | RIPE NCC | GB | 7th Oct 2019 |
| 193.29.192.0/21 | 2k | RIPE NCC | DE | 28th Jun 2010 |
| 193.29.20.0/23 | 512 | RIPE NCC | CH | 7th Oct 2019 |
| 193.29.208.0/21 | 2k | RIPE NCC | DE | 28th Jul 1993 |
| 193.29.216.0/22 | 1k | RIPE NCC | DE | 28th Jul 1993 |
| 193.29.229.0/24 | 256 | RIPE NCC | DE | 28th Jul 1993 |
| 193.29.248.0/23 | 512 | RIPE NCC | NL | 7th Oct 2019 |
| 193.29.26.0/24 | 256 | RIPE NCC | NL | 13th Nov 2019 |
| 193.29.27.0/24 | 256 | RIPE NCC | DE | 28th Jul 1993 |
| 193.29.36.0/23 | 512 | RIPE NCC |  MT | 7th Oct 2019 |
| 193.29.40.0/23 | 512 | RIPE NCC | MT | 7th Oct 2019 |
| 193.29.43.0/24 | 256 | RIPE NCC | DE | 28th Jul 1993 |
| 193.29.49.0/24 | 256 | RIPE NCC |  ES | 22nd Sept 2025 |
| 193.29.50.0/24 | 256 | RIPE NCC |  IR | 8th May 2025 |
| 193.29.6.0/23 | 512 | RIPE NCC | GB | 7th Oct 2019 |
| 193.3.12.0/22 | 1k | RIPE NCC | DK | 1st Sept 1993 |
| 193.3.133.0/24 | 256 | RIPE NCC | DK | 1st Sept 1993 |
| 193.3.134.0/23 | 512 | RIPE NCC | DK | 1st Sept 1993 |
| 193.3.138.0/23 | 512 | RIPE NCC | DK | 1st Sept 1993 |
| 193.3.144.0/21 | 2k | RIPE NCC | DK | 1st Sept 1993 |
| 193.3.152.0/22 | 1k | RIPE NCC | DK | 1st Sept 1993 |
| 193.3.156.0/24 | 256 | RIPE NCC | DK | 1st Sept 1993 |
| 193.3.158.0/24 | 256 | RIPE NCC |  HR | 15th Feb 2021 |