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,269 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 62.75.208.0/22 | 1k | RIPE NCC |  DE | 27th Jul 2001 |
| 62.75.225.0/24 | 256 | RIPE NCC | DE | 27th Jul 2001 |
| 62.75.226.0/23 | 512 | RIPE NCC | DE | 27th Jul 2001 |
| 62.75.240.0/21 | 2k | RIPE NCC | DE | 27th Jul 2001 |
| 62.75.248.0/22 | 1k | RIPE NCC | DE | 27th Jul 2001 |
| 62.76.151.0/24 | 256 | RIPE NCC |  RU | 16th Jun 1997 |
| 62.76.240.0/22 | 1k | RIPE NCC | RU | 16th Jun 1997 |
| 62.76.244.0/23 | 512 | RIPE NCC | RU | 16th Jun 1997 |
| 62.76.48.0/21 | 2k | RIPE NCC | RU | 16th Jun 1997 |
| 62.76.56.0/22 | 1k | RIPE NCC | RU | 16th Jun 1997 |
| 62.76.60.0/23 | 512 | RIPE NCC | RU | 16th Jun 1997 |
| 62.78.0.0/19 | 8.2k | RIPE NCC |  US | 24th Jul 2000 |
| 62.80.64.0/19 | 8.2k | RIPE NCC |  GB | 22nd Jun 2000 |
| 62.83.0.0/16 | 65.5k | RIPE NCC |  ES | 11th Feb 2000 |
| 63.141.34.0/23 | 512 | RIPE NCC |  IN | 18th Jan 2011 |
| 63.246.160.0/19 | 8.2k | RIPE NCC | DE | 25th Oct 2002 |
| 64.111.88.0/22 | 1k | RIPE NCC |  FR | 19th Nov 2007 |
| 64.17.244.0/22 | 1k | RIPE NCC |  RS | 11th Jul 2001 |
| 64.190.118.0/23 | 512 | RIPE NCC | FR | 31st May 2002 |
| 64.190.141.0/24 | 256 | RIPE NCC |  PL | 31st May 2002 |
| 64.190.167.0/24 | 256 | RIPE NCC | FR | 31st May 2002 |
| 64.190.219.0/24 | 256 | RIPE NCC | FR | 31st May 2002 |
| 64.190.81.0/24 | 256 | RIPE NCC |  NL | 31st May 2002 |
| 64.226.196.0/22 | 1k | RIPE NCC |  IL | 23rd Feb 2000 |
| 64.239.120.0/23 | 512 | RIPE NCC | GB | 25th Sept 2001 |
| 64.239.56.0/23 | 512 | RIPE NCC |  NO | 25th Sept 2001 |
| 64.254.160.0/20 | 4.1k | RIPE NCC |  IT | 17th Oct 2007 |
| 64.255.44.0/23 | 512 | RIPE NCC | IL | 16th Jan 2001 |
| 64.28.40.0/23 | 512 | RIPE NCC |  EE | 3rd Jan 2000 |
| 64.30.158.0/24 | 256 | RIPE NCC |  BG | 20th Apr 2017 |
| 64.39.233.0/24 | 256 | RIPE NCC | DE | 21st Jul 2000 |
| 64.39.236.0/24 | 256 | RIPE NCC | DE | 21st Jul 2000 |
| 64.39.80.0/20 | 4.1k | RIPE NCC | NO | 7th Mar 2008 |
| 65.181.117.0/24 | 256 | RIPE NCC | GB | 9th Mar 2011 |
| 66.186.194.0/23 | 512 | RIPE NCC |  AL | 9th Nov 2001 |
| 66.234.128.0/20 | 4.1k | RIPE NCC |  IE | 26th Feb 2002 |
| 66.242.48.0/23 | 512 | RIPE NCC | GB | 4th Mar 2002 |
| 66.255.200.0/22 | 1k | RIPE NCC | IE | 9th Feb 2004 |
| 66.45.120.0/21 | 2k | RIPE NCC | ES | 15th Nov 2000 |
| 66.9.112.0/20 | 4.1k | RIPE NCC |  SA | 12th Sept 2000 |
| 67.158.62.0/24 | 256 | RIPE NCC | IE | 1st Apr 2010 |
| 67.231.176.0/20 | 4.1k | RIPE NCC | IT | 26th May 2009 |
| 68.67.120.0/24 | 256 | RIPE NCC | NL | 22nd Jun 2009 |
| 70.40.128.0/21 | 2k | RIPE NCC | US | 1st Oct 2008 |
| 72.251.252.0/22 | 1k | RIPE NCC | DE | 29th Mar 2009 |
| 72.4.64.0/21 | 2k | RIPE NCC | IL | 1st Nov 2004 |
| 72.4.80.0/21 | 2k | RIPE NCC |  HK | 1st Nov 2004 |
| 74.122.24.0/24 | 256 | RIPE NCC | DE | 12th Jul 2019 |
| 74.122.26.0/23 | 512 | RIPE NCC |  CN | 12th Jul 2019 |
| 74.209.175.0/24 | 256 | RIPE NCC | GB | 19th May 2009 |