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.11.0.0/20 | 4.1k | RIPE NCC |  CH | 1st Sept 1993 |
| 194.11.112.0/20 | 4.1k | RIPE NCC | CH | 1st Sept 1993 |
| 194.11.18.0/24 | 256 | RIPE NCC |  GB | 2nd Jun 2008 |
| 194.11.204.0/23 | 512 | RIPE NCC | CH | 1st Sept 1993 |
| 194.11.22.0/24 | 256 | RIPE NCC |  PL | 3rd Jun 2008 |
| 194.11.227.0/24 | 256 | RIPE NCC | GB | 1st Sept 1993 |
| 194.11.230.0/23 | 512 | RIPE NCC |  NL | 18th Oct 2019 |
| 194.11.234.0/23 | 512 | RIPE NCC | NL | 18th Oct 2019 |
| 194.11.240.0/23 | 512 | RIPE NCC | CH | 1st Sept 1993 |
| 194.11.30.0/24 | 256 | RIPE NCC | CH | 1st Sept 1993 |
| 194.11.31.0/24 | 256 | RIPE NCC | CH | 1st Sept 1993 |
| 194.11.88.0/21 | 2k | RIPE NCC | CH | 1st Sept 1993 |
| 194.11.96.0/20 | 4.1k | RIPE NCC | CH | 1st Sept 1993 |
| 194.110.1.0/24 | 256 | RIPE NCC |  TR | 22nd Nov 2019 |
| 194.110.117.0/24 | 256 | RIPE NCC | GB | 22nd Nov 2019 |
| 194.110.128.0/24 | 256 | RIPE NCC | CH | 4th Apr 2007 |
| 194.110.132.0/24 | 256 | RIPE NCC | GB | 22nd Nov 2019 |
| 194.110.143.0/24 | 256 | RIPE NCC |  DE | 22nd Nov 2019 |
| 194.110.19.0/24 | 256 | RIPE NCC | TR | 22nd Nov 2019 |
| 194.110.194.0/24 | 256 | RIPE NCC |  IE | 29th Mar 2007 |
| 194.110.20.0/23 | 512 | RIPE NCC |  IT | 29th Oct 2019 |
| 194.110.200.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2019 |
| 194.110.210.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2019 |
| 194.110.211.0/24 | 256 | RIPE NCC | NL | 5th Apr 2007 |
| 194.110.214.0/24 | 256 | RIPE NCC | NL | 10th Apr 2007 |
| 194.110.215.0/24 | 256 | RIPE NCC | GB | 10th Apr 2007 |
| 194.110.216.0/24 | 256 | RIPE NCC |  RS | 11th Apr 2007 |
| 194.110.223.0/24 | 256 | RIPE NCC |  RU | 12th Apr 2007 |
| 194.110.236.0/24 | 256 | RIPE NCC |  JO | 12th Apr 2007 |
| 194.110.237.0/24 | 256 | RIPE NCC | GB | 12th Apr 2007 |
| 194.110.244.0/24 | 256 | RIPE NCC | GB | 16th Apr 2007 |
| 194.110.245.0/24 | 256 | RIPE NCC |  FR | 16th Apr 2007 |
| 194.110.252.0/24 | 256 | RIPE NCC |  UA | 13th Nov 2009 |
| 194.110.26.0/24 | 256 | RIPE NCC | PL | 18th Jul 2007 |
| 194.110.28.0/23 | 512 | RIPE NCC | IT | 29th Oct 2019 |
| 194.110.31.0/24 | 256 | RIPE NCC |  FI | 1st Feb 1995 |
| 194.110.32.0/22 | 1k | RIPE NCC | FI | 18th Sept 1995 |
| 194.110.36.0/23 | 512 | RIPE NCC | FI | 18th Sept 1995 |
| 194.110.39.0/24 | 256 | RIPE NCC | FI | 18th Sept 1995 |
| 194.110.40.0/22 | 1k | RIPE NCC | FI | 3rd Oct 1995 |
| 194.110.68.0/24 | 256 | RIPE NCC |  RO | 17th Apr 2007 |
| 194.110.7.0/24 | 256 | RIPE NCC | TR | 22nd Nov 2019 |
| 194.110.71.0/24 | 256 | RIPE NCC | RU | 3rd Feb 2026 |
| 194.110.74.0/24 | 256 | RIPE NCC | GB | 22nd Nov 2019 |
| 194.110.80.0/22 | 1k | RIPE NCC | RU | 25th Sept 2018 |
| 194.110.92.0/22 | 1k | RIPE NCC | DE | 26th Sept 2018 |
| 194.110.96.0/20 | 4.1k | RIPE NCC |  SE | 16th Feb 1995 |
| 194.112.20.0/22 | 1k | RIPE NCC | DE | 13th Jan 1995 |
| 194.113.100.0/22 | 1k | RIPE NCC | DE | 14th Dec 1994 |
| 194.113.116.0/24 | 256 | RIPE NCC |  IR | 9th Jul 2026 |