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 the most unannounced blocks, largest first.
Unannounced blocks
84,619 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 79.143.48.0/20 | 4.1k | RIPE NCC |  AT | 20th Nov 2007 |
| 79.170.104.0/21 | 2k | RIPE NCC |  BY | 26th Sept 2007 |
| 79.170.168.0/21 | 2k | RIPE NCC |  TR | 1st Oct 2007 |
| 79.170.192.0/24 | 256 | RIPE NCC |  GB | 2nd Oct 2007 |
| 79.170.195.0/24 | 256 | RIPE NCC |  IL | 2nd Oct 2007 |
| 79.170.200.0/21 | 2k | RIPE NCC |  US | 3rd Oct 2007 |
| 79.170.232.0/21 | 2k | RIPE NCC |  FR | 5th Oct 2007 |
| 79.170.56.0/21 | 2k | RIPE NCC | FR | 25th Sept 2007 |
| 79.171.114.0/24 | 256 | RIPE NCC |  RU | 12th Oct 2007 |
| 79.171.168.0/23 | 512 | RIPE NCC | RU | 7th Oct 2008 |
| 79.171.170.0/23 | 512 | RIPE NCC | RU | 7th Oct 2008 |
| 79.171.184.0/21 | 2k | RIPE NCC |  CZ | 17th Oct 2007 |
| 79.171.192.0/21 | 2k | RIPE NCC |  NL | 17th Oct 2007 |
| 79.171.200.0/21 | 2k | RIPE NCC |  DE | 17th Oct 2007 |
| 79.171.24.0/21 | 2k | RIPE NCC |  ES | 30th Jan 2008 |
| 79.174.0.0/23 | 512 | RIPE NCC | DE | 4th Oct 2018 |
| 79.174.176.0/21 | 2k | RIPE NCC |  NO | 9th Aug 2012 |
| 79.174.96.0/19 | 8.2k | RIPE NCC | AT | 16th Jun 2008 |
| 79.64.0.0/15 | 131k | RIPE NCC |  SE | 19th Jun 2007 |
| 79.98.248.0/21 | 2k | RIPE NCC | RU | 17th Jan 2011 |
| 79.98.80.0/21 | 2k | RIPE NCC | GB | 29th Oct 2007 |
| 79.99.140.0/22 | 1k | RIPE NCC | AT | 22nd Nov 2007 |
| 79.99.152.0/21 | 2k | RIPE NCC |  FI | 27th Nov 2007 |
| 80.104.0.0/15 | 131k | RIPE NCC |  IT | 17th Jul 2001 |
| 80.117.0.0/16 | 65.5k | RIPE NCC | IT | 6th Aug 2001 |
| 80.173.112.0/22 | 1k | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.116.0/23 | 512 | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.118.0/23 | 512 | RIPE NCC |  AM | 11th Jun 2003 |
| 80.173.120.0/21 | 2k | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.128.0/22 | 1k | RIPE NCC |  HR | 11th Jun 2003 |
| 80.173.132.0/22 | 1k | RIPE NCC | HR | 11th Jun 2003 |
| 80.173.174.0/24 | 256 | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.175.0/24 | 256 | RIPE NCC | AM | 11th Jun 2003 |
| 80.173.224.0/22 | 1k | RIPE NCC | IT | 11th Jun 2003 |
| 80.173.64.0/19 | 8.2k | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.96.0/20 | 4.1k | RIPE NCC | ES | 11th Jun 2003 |
| 80.210.80.0/20 | 4.1k | RIPE NCC | NO | 12th Dec 2001 |
| 80.224.0.0/17 | 32.8k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.128.0/19 | 8.2k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.160.0/20 | 4.1k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.176.0/22 | 1k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.180.0/23 | 512 | RIPE NCC |  AE | 28th Sept 2001 |
| 80.224.182.0/23 | 512 | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.184.0/22 | 1k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.188.0/24 | 256 | RIPE NCC |  EE | 28th Sept 2001 |
| 80.224.190.0/24 | 256 | RIPE NCC | IT | 28th Sept 2001 |
| 80.224.191.0/24 | 256 | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.208.0/21 | 2k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.216.0/23 | 512 | RIPE NCC |  CH | 28th Sept 2001 |
| 80.224.248.0/22 | 1k | RIPE NCC | IT | 28th Sept 2001 |