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
24,939 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 109.236.160.0/24 | 256 | RIPE NCC |  GB | 17th Dec 2009 |
| 109.237.48.0/21 | 2k | RIPE NCC |  CH | 13th Jan 2009 |
| 109.237.56.0/23 | 512 | RIPE NCC | CH | 13th Jan 2009 |
| 109.237.58.0/24 | 256 | RIPE NCC | CH | 13th Jan 2009 |
| 109.68.176.0/21 | 2k | RIPE NCC |  NO | 16th Sept 2009 |
| 109.68.196.0/22 | 1k | RIPE NCC | GB | 17th Sept 2009 |
| 109.68.216.0/24 | 256 | RIPE NCC |  TR | 9th Jul 2026 |
| 109.68.218.0/24 | 256 | RIPE NCC |  BY | 9th Jul 2026 |
| 109.68.220.0/24 | 256 | RIPE NCC |  SI | 9th Jul 2026 |
| 109.68.222.0/24 | 256 | RIPE NCC |  AZ | 13th Jul 2026 |
| 109.68.32.0/21 | 2k | RIPE NCC |  DE | 2nd Mar 2010 |
| 109.69.136.0/21 | 2k | RIPE NCC |  NL | 13th Oct 2009 |
| 109.69.16.0/21 | 2k | RIPE NCC |  RU | 25th Sept 2009 |
| 109.70.176.0/21 | 2k | RIPE NCC |  FI | 9th Nov 2009 |
| 109.70.200.0/21 | 2k | RIPE NCC |  IT | 10th Nov 2009 |
| 109.70.8.0/21 | 2k | RIPE NCC | NL | 23rd Oct 2009 |
| 109.71.0.0/21 | 2k | RIPE NCC | NL | 11th Nov 2009 |
| 109.71.157.0/24 | 256 | RIPE NCC |  FR | 18th Dec 2025 |
| 109.71.158.0/24 | 256 | RIPE NCC | RU | 18th Dec 2025 |
| 109.71.188.0/23 | 512 | RIPE NCC |  KW | 23rd Nov 2009 |
| 109.71.32.0/21 | 2k | RIPE NCC |  KZ | 12th Nov 2009 |
| 109.71.79.0/24 | 256 | RIPE NCC |  IE | 23rd Jun 2020 |
| 109.72.176.0/20 | 4.1k | RIPE NCC | NL | 23rd Sept 2009 |
| 109.73.140.0/22 | 1k | RIPE NCC | DE | 29th Aug 2018 |
| 109.74.18.0/24 | 256 | RIPE NCC | TR | 19th Jan 2026 |
| 109.75.224.0/21 | 2k | RIPE NCC | FI | 24th Nov 2009 |
| 109.94.124.0/23 | 512 | RIPE NCC |  RS | 6th Nov 2009 |
| 109.94.192.0/20 | 4.1k | RIPE NCC | RU | 27th Oct 2009 |
| 109.94.211.0/24 | 256 | RIPE NCC | RU | 29th Aug 2018 |
| 109.95.128.0/21 | 2k | RIPE NCC |  IL | 23rd Dec 2009 |
| 109.95.240.0/21 | 2k | RIPE NCC | GB | 27th Jan 2010 |
| 111.88.176.0/21 | 2k | RIPE NCC | RU | 12th Jun 2009 |
| 111.88.192.0/20 | 4.1k | RIPE NCC | RU | 12th Jun 2009 |
| 111.88.208.0/22 | 1k | RIPE NCC | RU | 12th Jun 2009 |
| 116.214.122.0/24 | 256 | RIPE NCC | GB | 1st May 2007 |
| 116.214.124.0/24 | 256 | RIPE NCC | GB | 1st May 2007 |
| 119.12.16.0/24 | 256 | RIPE NCC |  PL | 26th Nov 2007 |
| 123.100.234.0/24 | 256 | RIPE NCC | GB | 10th Nov 2006 |
| 124.198.192.0/19 | 8.2k | RIPE NCC | DE | 22nd Mar 2010 |
| 128.0.0.0/24 | 256 | RIPE NCC | NL | 14th Sept 2012 |
| 128.0.104.0/24 | 256 | RIPE NCC |  UA | 14th Sept 2012 |
| 128.0.107.0/24 | 256 | RIPE NCC |  CY | 14th Sept 2012 |
| 128.0.108.0/22 | 1k | RIPE NCC | CY | 14th Sept 2012 |
| 128.0.32.0/24 | 256 | RIPE NCC |  SC | 14th Sept 2012 |
| 128.0.33.0/24 | 256 | RIPE NCC | CH | 14th Sept 2012 |
| 128.0.38.0/23 | 512 | RIPE NCC | GB | 14th Sept 2012 |
| 128.0.41.0/24 | 256 | RIPE NCC |  AE | 14th Sept 2012 |
| 128.0.45.0/24 | 256 | RIPE NCC |  IQ | 14th Sept 2012 |
| 128.140.128.0/20 | 4.1k | RIPE NCC | FR | 11th Oct 2011 |
| 128.204.194.0/24 | 256 | RIPE NCC | NL | 13th Oct 2011 |