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,755 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 91.220.9.0/24 | 256 | RIPE NCC |  ES | 7th Oct 2010 |
| 91.220.91.0/24 | 256 | RIPE NCC |  UA | 29th Oct 2010 |
| 91.220.92.0/24 | 256 | RIPE NCC |  RU | 1st Nov 2010 |
| 91.220.94.0/24 | 256 | RIPE NCC |  SA | 16th Jun 2026 |
| 91.220.95.0/24 | 256 | RIPE NCC |  MK | 1st Nov 2010 |
| 91.220.96.0/24 | 256 | RIPE NCC |  RO | 1st Nov 2010 |
| 91.221.10.0/23 | 512 | RIPE NCC |  DE | 14th Oct 2010 |
| 91.221.14.0/23 | 512 | RIPE NCC | UA | 14th Oct 2010 |
| 91.221.154.0/23 | 512 | RIPE NCC | UA | 3rd Dec 2010 |
| 91.221.158.0/23 | 512 | RIPE NCC |  PL | 6th Dec 2010 |
| 91.221.166.0/23 | 512 | RIPE NCC | UA | 9th Dec 2010 |
| 91.221.168.0/23 | 512 | RIPE NCC |  GB | 9th Dec 2010 |
| 91.221.186.0/23 | 512 | RIPE NCC |  DK | 15th Dec 2010 |
| 91.221.224.0/23 | 512 | RIPE NCC |  FR | 27th Dec 2010 |
| 91.221.226.0/23 | 512 | RIPE NCC | DE | 28th Dec 2010 |
| 91.221.32.0/23 | 512 | RIPE NCC |  IT | 20th Oct 2010 |
| 91.221.60.0/23 | 512 | RIPE NCC |  AM | 27th Oct 2010 |
| 91.221.72.0/23 | 512 | RIPE NCC |  NL | 4th Nov 2010 |
| 91.221.8.0/23 | 512 | RIPE NCC | DE | 14th Oct 2010 |
| 91.221.80.0/24 | 256 | RIPE NCC | NL | 12th Jan 2022 |
| 91.221.81.0/24 | 256 | RIPE NCC | NL | 12th Jan 2022 |
| 91.222.100.0/22 | 1k | RIPE NCC | PL | 9th Dec 2010 |
| 91.222.104.0/22 | 1k | RIPE NCC |  SK | 9th Dec 2010 |
| 91.222.156.0/22 | 1k | RIPE NCC | RU | 22nd Dec 2010 |
| 91.222.200.0/22 | 1k | RIPE NCC | SA | 10th Jan 2011 |
| 91.222.224.0/22 | 1k | RIPE NCC | PL | 13th Jan 2011 |
| 91.222.43.0/24 | 256 | RIPE NCC | FR | 25th Nov 2010 |
| 91.222.8.0/22 | 1k | RIPE NCC | DE | 22nd Aug 2011 |
| 91.223.114.0/24 | 256 | RIPE NCC | DE | 11th Feb 2011 |
| 91.223.129.0/24 | 256 | RIPE NCC | DE | 15th Feb 2011 |
| 91.223.138.0/24 | 256 | RIPE NCC | RU | 17th Feb 2011 |
| 91.223.139.0/24 | 256 | RIPE NCC | FR | 18th Feb 2011 |
| 91.223.15.0/24 | 256 | RIPE NCC | RU | 18th Jan 2011 |
| 91.223.16.0/24 | 256 | RIPE NCC | DE | 18th Jan 2011 |
| 91.223.171.0/24 | 256 | RIPE NCC | PL | 25th Feb 2011 |
| 91.223.172.0/24 | 256 | RIPE NCC | NL | 28th Feb 2011 |
| 91.223.181.0/24 | 256 | RIPE NCC | RU | 2nd Mar 2011 |
| 91.223.191.0/24 | 256 | RIPE NCC |  US | 4th Mar 2011 |
| 91.223.192.0/24 | 256 | RIPE NCC | FR | 3rd Mar 2025 |
| 91.223.196.0/24 | 256 | RIPE NCC | PL | 4th Mar 2011 |
| 91.223.200.0/24 | 256 | RIPE NCC | RO | 8th Mar 2011 |
| 91.223.206.0/24 | 256 | RIPE NCC | ES | 8th Mar 2011 |
| 91.223.210.0/24 | 256 | RIPE NCC | SA | 9th Mar 2011 |
| 91.223.213.0/24 | 256 | RIPE NCC |  NO | 10th Mar 2011 |
| 91.223.234.0/24 | 256 | RIPE NCC | UA | 16th Mar 2011 |
| 91.223.237.0/24 | 256 | RIPE NCC |  HR | 16th Mar 2011 |
| 91.223.239.0/24 | 256 | RIPE NCC | RU | 17th Mar 2011 |
| 91.223.251.0/24 | 256 | RIPE NCC | RU | 21st Mar 2011 |
| 91.223.252.0/24 | 256 | RIPE NCC | RU | 21st Mar 2011 |
| 91.223.255.0/24 | 256 | RIPE NCC | UA | 27th Jan 2026 |