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.25.180.0/23 | 512 | RIPE NCC |  UA | 15th Mar 2004 |
| 193.25.201.0/24 | 256 | RIPE NCC |  DE | 10th Jan 2020 |
| 193.25.254.0/24 | 256 | RIPE NCC | DE | 11th Feb 1993 |
| 193.254.19.0/24 | 256 | RIPE NCC | DE | 23rd Dec 1998 |
| 193.254.194.0/23 | 512 | RIPE NCC |  GB | 16th Aug 2002 |
| 193.254.198.0/23 | 512 | RIPE NCC |  US | 22nd Aug 2002 |
| 193.254.2.0/24 | 256 | RIPE NCC |  AL | 28th Oct 1993 |
| 193.254.200.0/23 | 512 | RIPE NCC |  GR | 22nd Aug 2002 |
| 193.254.23.0/25 | 128 | RIPE NCC | DE | 23rd Dec 1998 |
| 193.254.23.128/25 | 128 | RIPE NCC |  FI | 3rd Aug 2000 |
| 193.254.232.0/23 | 512 | RIPE NCC | UA | 23rd Sept 2002 |
| 193.254.234.0/23 | 512 | RIPE NCC |  SC | 17th Oct 2019 |
| 193.254.24.0/23 | 512 | RIPE NCC |  IT | 11th Jun 1999 |
| 193.254.26.0/24 | 256 | RIPE NCC | IT | 11th Jun 1999 |
| 193.26.132.0/24 | 256 | RIPE NCC |  DK | 18th Mar 2004 |
| 193.26.134.0/24 | 256 | RIPE NCC |  SK | 18th Mar 2004 |
| 193.26.136.0/21 | 2k | RIPE NCC |  RO | 11th Mar 1993 |
| 193.26.144.0/23 | 512 | RIPE NCC | DE | 11th Mar 1993 |
| 193.26.160.0/19 | 8.2k | RIPE NCC | DE | 11th Mar 1993 |
| 193.26.215.0/24 | 256 | RIPE NCC | DE | 13th Nov 2019 |
| 193.26.219.0/24 | 256 | RIPE NCC | DE | 13th Nov 2019 |
| 193.26.240.0/23 | 512 | RIPE NCC | DE | 11th Mar 1993 |
| 193.26.244.0/23 | 512 | RIPE NCC | DE | 11th Mar 1993 |
| 193.26.29.0/24 | 256 | RIPE NCC |  NL | 29th Sept 2004 |
| 193.26.5.0/24 | 256 | RIPE NCC | DE | 13th Sept 2004 |
| 193.26.7.0/24 | 256 | RIPE NCC | RO | 14th Sept 2004 |
| 193.27.16.0/23 | 512 | RIPE NCC | NL | 7th Oct 2019 |
| 193.27.204.0/23 | 512 | RIPE NCC |  PL | 23rd Dec 2003 |
| 193.27.206.0/23 | 512 | RIPE NCC |  UZ | 23rd Dec 2003 |
| 193.27.216.0/23 | 512 | RIPE NCC | FI | 14th Jan 2004 |
| 193.27.226.0/23 | 512 | RIPE NCC | NL | 19th Jan 2004 |
| 193.27.230.0/23 | 512 | RIPE NCC |  RU | 20th Jan 2004 |
| 193.27.250.0/23 | 512 | RIPE NCC | DK | 30th Jan 2004 |
| 193.27.36.0/22 | 1k | RIPE NCC | RU | 10th Jul 2018 |
| 193.27.4.0/24 | 256 | RIPE NCC |  FR | 14th Apr 2004 |
| 193.27.42.0/24 | 256 | RIPE NCC | GB | 19th Mar 2004 |
| 193.27.47.0/24 | 256 | RIPE NCC |  ES | 11th Aug 2011 |
| 193.27.64.0/23 | 512 | RIPE NCC | RO | 6th Feb 2004 |
| 193.27.74.0/23 | 512 | RIPE NCC | NL | 12th Feb 2004 |
| 193.27.76.0/23 | 512 | RIPE NCC | NL | 7th Oct 2019 |
| 193.27.8.0/24 | 256 | RIPE NCC | DE | 13th Nov 2019 |
| 193.28.106.0/24 | 256 | RIPE NCC | US | 13th Nov 2019 |
| 193.28.107.0/24 | 256 | RIPE NCC | DE | 1st Jun 1993 |
| 193.28.108.0/22 | 1k | RIPE NCC | DE | 1st Jun 1993 |
| 193.28.112.0/20 | 4.1k | RIPE NCC | DE | 1st Jun 1993 |
| 193.28.13.0/24 | 256 | RIPE NCC | DE | 13th Sept 2005 |
| 193.28.151.0/24 | 256 | RIPE NCC |  CZ | 12th Nov 2024 |
| 193.28.154.0/24 | 256 | RIPE NCC | GB | 23rd Jul 2004 |
| 193.28.156.0/24 | 256 | RIPE NCC | GR | 26th May 2025 |
| 193.28.181.0/24 | 256 | RIPE NCC |  IR | 4th Oct 2011 |