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 |
|---|---|---|---|---|
| 164.37.52.0/22 | 1k | RIPE NCC |  DE | 31st Jan 1993 |
| 164.37.56.0/22 | 1k | RIPE NCC |  DK | 31st Jan 1993 |
| 164.37.60.0/22 | 1k | RIPE NCC |  SE | 31st Jan 1993 |
| 164.37.64.0/21 | 2k | RIPE NCC | SE | 31st Jan 1993 |
| 164.37.80.0/20 | 4.1k | RIPE NCC | SE | 31st Jan 1993 |
| 164.40.224.0/21 | 2k | RIPE NCC |  BA | 18th Nov 2011 |
| 164.40.232.0/24 | 256 | RIPE NCC |  RU | 6th May 2026 |
| 164.40.233.0/24 | 256 | RIPE NCC |  IR | 7th May 2026 |
| 164.40.234.0/24 | 256 | RIPE NCC |  KZ | 11th May 2026 |
| 164.40.236.0/24 | 256 | RIPE NCC |  TR | 12th May 2026 |
| 164.40.238.0/24 | 256 | RIPE NCC |  AZ | 15th May 2026 |
| 164.40.239.0/24 | 256 | RIPE NCC |  FR | 15th May 2026 |
| 164.5.232.0/23 | 512 | RIPE NCC |  FI | 25th Sept 1992 |
| 164.5.234.0/23 | 512 | RIPE NCC | FI | 25th Sept 1992 |
| 164.5.236.0/22 | 1k | RIPE NCC | FI | 25th Sept 1992 |
| 164.6.0.0/16 | 65.5k | RIPE NCC |  GB | 25th Sept 1992 |
| 164.7.0.0/16 | 65.5k | RIPE NCC | FR | 7th Oct 1993 |
| 164.93.128.0/17 | 32.8k | RIPE NCC | GB | 12th Nov 2013 |
| 165.114.0.0/16 | 65.5k | RIPE NCC |  NL | 22nd Aug 2007 |
| 165.217.64.0/22 | 1k | RIPE NCC |  US | 7th Sept 1993 |
| 165.217.68.0/22 | 1k | RIPE NCC | US | 7th Sept 1993 |
| 165.217.72.0/22 | 1k | RIPE NCC | US | 7th Sept 1993 |
| 165.217.76.0/22 | 1k | RIPE NCC | US | 7th Sept 1993 |
| 165.217.80.0/22 | 1k | RIPE NCC | US | 7th Sept 1993 |
| 165.217.84.0/22 | 1k | RIPE NCC | US | 7th Sept 1993 |
| 165.217.88.0/22 | 1k | RIPE NCC | US | 7th Sept 1993 |
| 165.217.92.0/22 | 1k | RIPE NCC | US | 7th Sept 1993 |
| 165.218.0.0/16 | 65.5k | RIPE NCC | DE | 1st Sept 1993 |
| 165.65.196.0/22 | 1k | RIPE NCC | GB | 12th Apr 1993 |
| 165.65.200.0/22 | 1k | RIPE NCC | GB | 12th Apr 1993 |
| 165.84.224.0/21 | 2k | RIPE NCC | GB | 16th Feb 2016 |
| 166.10.0.0/16 | 65.5k | RIPE NCC | US | 1st Sept 1993 |
| 166.11.0.0/16 | 65.5k | RIPE NCC | US | 1st Sept 1993 |
| 166.12.0.0/14 | 262k | RIPE NCC |  CH | 1st Sept 1993 |
| 166.8.0.0/16 | 65.5k | RIPE NCC | US | 1st Sept 1993 |
| 166.9.0.0/16 | 65.5k | RIPE NCC | US | 1st Sept 1993 |
| 167.104.0.0/19 | 8.2k | RIPE NCC | DE | 28th Mar 1993 |
| 167.104.128.0/19 | 8.2k | RIPE NCC | DE | 28th Mar 1993 |
| 167.104.160.0/20 | 4.1k | RIPE NCC | SE | 28th May 1993 |
| 167.104.224.0/19 | 8.2k | RIPE NCC | DE | 28th Mar 1993 |
| 167.111.0.0/16 | 65.5k | RIPE NCC |  SA | 1st Sept 1993 |
| 167.150.120.0/24 | 256 | RIPE NCC |  NO | 2nd Aug 1993 |
| 167.160.21.0/24 | 256 | RIPE NCC |  GE | 3rd Mar 2014 |
| 167.160.24.0/23 | 512 | RIPE NCC |  ES | 3rd Mar 2014 |
| 167.160.30.0/24 | 256 | RIPE NCC | GE | 3rd Mar 2014 |
| 167.168.0.0/16 | 65.5k | RIPE NCC | CH | 1st Sept 1993 |
| 167.81.0.0/16 | 65.5k | RIPE NCC | NL | 12th May 1993 |
| 167.87.0.0/16 | 65.5k | RIPE NCC | DE | 17th May 1993 |
| 167.94.170.0/23 | 512 | RIPE NCC |  CA | 21st May 1993 |
| 167.94.172.0/23 | 512 | RIPE NCC | CA | 21st May 1993 |