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 registered through RIPE NCC
25,296 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 194.213.128.0/19 | 8.2k | RIPE NCC |  NO | 8th Jan 1996 |
| 194.213.160.0/19 | 8.2k | RIPE NCC | NO | 22nd Apr 1999 |
| 194.213.26.0/24 | 256 | RIPE NCC |  PL | 2nd Aug 2010 |
| 194.213.27.0/24 | 256 | RIPE NCC |  DE | 12th Sept 2005 |
| 194.213.28.0/24 | 256 | RIPE NCC |  GB | 12th Sept 2005 |
| 194.213.29.0/24 | 256 | RIPE NCC |  IE | 12th Sept 2005 |
| 194.213.7.0/24 | 256 | RIPE NCC |  CH | 6th Sept 2005 |
| 194.222.0.0/19 | 8.2k | RIPE NCC | GB | 21st Dec 1995 |
| 194.222.128.0/17 | 32.8k | RIPE NCC | GB | 26th Jun 1996 |
| 194.222.32.0/19 | 8.2k | RIPE NCC | GB | 27th Mar 1996 |
| 194.222.64.0/18 | 16.4k | RIPE NCC | GB | 26th Jun 1996 |
| 194.226.100.0/22 | 1k | RIPE NCC |  RU | 3rd Jan 1996 |
| 194.226.124.0/23 | 512 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.226.134.0/23 | 512 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.226.140.0/23 | 512 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.226.18.0/24 | 256 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.226.24.0/23 | 512 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.226.36.0/24 | 256 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.226.40.0/24 | 256 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.226.48.0/24 | 256 | RIPE NCC | RU | 3rd Jan 1996 |
| 194.233.112.0/20 | 4.1k | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.144.0/21 | 2k | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.20.0/22 | 1k | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.240.0/20 | 4.1k | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.28.0/22 | 1k | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.32.0/20 | 4.1k | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.48.0/23 | 512 | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.52.0/22 | 1k | RIPE NCC | DE | 26th Jan 1996 |
| 194.233.56.0/22 | 1k | RIPE NCC | DE | 26th Jan 1996 |
| 194.238.128.0/17 | 32.8k | RIPE NCC | GB | 2nd Feb 1996 |
| 194.238.45.0/24 | 256 | RIPE NCC | GB | 2nd Feb 1996 |
| 194.238.46.0/24 | 256 | RIPE NCC | GB | 2nd Feb 1996 |
| 194.238.47.0/24 | 256 | RIPE NCC |  TJ | 2nd Feb 1996 |
| 194.238.78.0/24 | 256 | RIPE NCC | GB | 2nd Feb 1996 |
| 194.24.232.0/23 | 512 | RIPE NCC |  IN | 21st Oct 2019 |
| 194.242.0.0/23 | 512 | RIPE NCC | PL | 27th Aug 2009 |
| 194.242.18.0/23 | 512 | RIPE NCC |  NL | 3rd Sept 2009 |
| 194.242.38.0/24 | 256 | RIPE NCC | NL | 22nd Nov 2019 |
| 194.242.50.0/24 | 256 | RIPE NCC |  LU | 3rd May 2001 |
| 194.242.51.0/24 | 256 | RIPE NCC | CH | 3rd May 2001 |
| 194.242.55.0/24 | 256 | RIPE NCC | GB | 4th Feb 2004 |
| 194.246.34.0/24 | 256 | RIPE NCC |  IR | 8th May 2024 |
| 194.246.39.0/26 | 64 | RIPE NCC | PL | 19th Dec 2025 |
| 194.246.39.128/27 | 32 | RIPE NCC | DE | 17th Sept 1996 |
| 194.246.39.160/27 | 32 | RIPE NCC | DE | 17th Sept 1996 |
| 194.246.39.224/27 | 32 | RIPE NCC | NL | 31st Aug 2004 |
| 194.246.39.64/26 | 64 | RIPE NCC | NL | 13th Jan 2026 |
| 194.246.64.0/21 | 2k | RIPE NCC | DE | 21st Jun 1996 |
| 194.246.98.0/24 | 256 | RIPE NCC | GB | 11th Feb 2004 |
| 194.247.168.0/23 | 512 | RIPE NCC | RU | 12th Nov 2009 |