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.246.154.0/23 | 512 | RIPE NCC |  ES | 17th Oct 2019 |
| 193.246.158.0/24 | 256 | RIPE NCC |  CH | 28th May 1997 |
| 193.246.163.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.166.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.168.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.172.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.202.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.204.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.206.0/24 | 256 | RIPE NCC |  RU | 19th Nov 2019 |
| 193.246.208.0/20 | 4.1k | RIPE NCC | CH | 28th May 1997 |
| 193.246.242.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.245.0/24 | 256 | RIPE NCC | RU | 19th Nov 2019 |
| 193.246.246.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.252.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.254.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.51.0/24 | 256 | RIPE NCC | RU | 19th Nov 2019 |
| 193.246.52.0/22 | 1k | RIPE NCC |  GB | 28th May 1997 |
| 193.246.6.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.60.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.62.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.104.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.106.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.145.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.152.0/21 | 2k | RIPE NCC | CH | 28th May 1997 |
| 193.247.160.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.163.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.164.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.166.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.186.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.187.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.188.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.201.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.204.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.206.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.214.0/23 | 512 | RIPE NCC | ES | 17th Oct 2019 |
| 193.247.218.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.220.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.247.232.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.247.254.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.255.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.64.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.68.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.247.78.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.80.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.89.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.247.90.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.247.92.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.25.124.0/23 | 512 | RIPE NCC |  TR | 2nd Apr 2004 |
| 193.25.128.0/19 | 8.2k | RIPE NCC |  DE | 11th Feb 1993 |
| 193.25.170.0/23 | 512 | RIPE NCC | DE | 28th Nov 2011 |