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,872 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 217.119.49.0/24 | 256 | RIPE NCC |  DE | 26th Feb 2004 |
| 217.119.50.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.51.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.54.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.56.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.57.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.60.0/22 | 1k | RIPE NCC | DE | 26th Feb 2004 |
| 217.12.160.0/20 | 4.1k | RIPE NCC |  IT | 24th Aug 2000 |
| 217.129.0.0/16 | 65.5k | RIPE NCC |  PT | 16th Jan 2001 |
| 217.138.0.0/21 | 2k | RIPE NCC |  GB | 31st Jan 2001 |
| 217.138.105.0/24 | 256 | RIPE NCC |  RO | 31st Jan 2001 |
| 217.138.111.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.133.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.134.0/23 | 512 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.14.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.144.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.155.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.53.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.71.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.80.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.84.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.138.94.0/24 | 256 | RIPE NCC | RO | 31st Jan 2001 |
| 217.14.24.0/24 | 256 | RIPE NCC |  RU | 9th Dec 2002 |
| 217.14.26.0/23 | 512 | RIPE NCC | RU | 9th Dec 2002 |
| 217.14.28.0/22 | 1k | RIPE NCC | RU | 9th Dec 2002 |
| 217.140.16.0/20 | 4.1k | RIPE NCC | GB | 5th Mar 2001 |
| 217.142.32.0/19 | 8.2k | RIPE NCC |  SE | 31st Jan 2001 |
| 217.147.4.0/22 | 1k | RIPE NCC | SE | 1st Oct 2018 |
| 217.150.86.0/23 | 512 | RIPE NCC |  LB | 18th May 2012 |
| 217.151.0.0/20 | 4.1k | RIPE NCC |  FR | 15th Mar 2001 |
| 217.151.48.0/20 | 4.1k | RIPE NCC | SE | 29th Jun 2004 |
| 217.154.104.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.12.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.128.0/23 | 512 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.136.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.139.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.151.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.158.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.209.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.219.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.221.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.236.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.25.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.154.29.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.46.0/24 | 256 | RIPE NCC | GB | 19th Feb 2001 |
| 217.16.32.0/20 | 4.1k | RIPE NCC |  NL | 11th Sept 2000 |
| 217.16.48.0/20 | 4.1k | RIPE NCC | GB | 22nd Nov 2002 |
| 217.170.160.0/20 | 4.1k | RIPE NCC |  PL | 14th May 2009 |
| 217.171.160.0/20 | 4.1k | RIPE NCC | IT | 2nd Apr 2001 |
| 217.172.160.0/23 | 512 | RIPE NCC | DE | 6th Apr 2001 |