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.234.18.0/24 | 256 | RIPE NCC |  GB | 21st Dec 2011 |
| 91.234.201.0/24 | 256 | RIPE NCC | GB | 27th Jan 2012 |
| 91.234.210.0/23 | 512 | RIPE NCC |  UA | 30th Jan 2012 |
| 91.234.212.0/24 | 256 | RIPE NCC |  RO | 30th Jan 2012 |
| 91.234.224.0/23 | 512 | RIPE NCC |  RU | 30th Jan 2012 |
| 91.234.230.0/23 | 512 | RIPE NCC |  BE | 30th Jan 2012 |
| 91.234.248.0/22 | 1k | RIPE NCC |  CZ | 31st Jan 2012 |
| 91.234.55.0/24 | 256 | RIPE NCC |  DE | 27th Dec 2011 |
| 91.234.99.0/24 | 256 | RIPE NCC | RU | 30th Dec 2011 |
| 91.235.0.0/23 | 512 | RIPE NCC |  PL | 1st Feb 2012 |
| 91.235.107.0/24 | 256 | RIPE NCC |  IL | 9th Feb 2012 |
| 91.235.117.0/24 | 256 | RIPE NCC |  IE | 9th Feb 2012 |
| 91.235.118.0/24 | 256 | RIPE NCC | GB | 9th Feb 2012 |
| 91.235.119.0/24 | 256 | RIPE NCC |  GI | 9th Feb 2012 |
| 91.235.150.0/23 | 512 | RIPE NCC | IL | 14th Feb 2012 |
| 91.235.156.0/23 | 512 | RIPE NCC | RU | 14th Feb 2012 |
| 91.235.168.0/24 | 256 | RIPE NCC |  NL | 15th Feb 2012 |
| 91.235.171.0/24 | 256 | RIPE NCC | DE | 15th May 2023 |
| 91.235.2.0/24 | 256 | RIPE NCC | GB | 6th Dec 2019 |
| 91.235.205.0/24 | 256 | RIPE NCC | GB | 24th May 2023 |
| 91.235.228.0/23 | 512 | RIPE NCC | PL | 17th Feb 2012 |
| 91.235.43.0/24 | 256 | RIPE NCC | RO | 3rd Feb 2012 |
| 91.235.6.0/24 | 256 | RIPE NCC |  IS | 2nd Feb 2012 |
| 91.235.76.0/23 | 512 | RIPE NCC | IE | 5th Nov 2019 |
| 91.236.104.0/24 | 256 | RIPE NCC | RU | 11th Nov 2019 |
| 91.236.105.0/24 | 256 | RIPE NCC | PL | 1st Mar 2012 |
| 91.236.115.0/24 | 256 | RIPE NCC | RU | 11th Nov 2019 |
| 91.236.152.0/24 | 256 | RIPE NCC | GB | 9th Mar 2012 |
| 91.236.162.0/24 | 256 | RIPE NCC |  AE | 12th Mar 2012 |
| 91.236.17.0/24 | 256 | RIPE NCC | GB | 24th Feb 2012 |
| 91.236.187.0/24 | 256 | RIPE NCC | PL | 13th Mar 2012 |
| 91.236.189.0/24 | 256 | RIPE NCC | NL | 13th Mar 2012 |
| 91.236.194.0/24 | 256 | RIPE NCC | NL | 14th Mar 2012 |
| 91.236.201.0/24 | 256 | RIPE NCC |  EE | 14th Mar 2012 |
| 91.236.206.0/24 | 256 | RIPE NCC | GB | 14th Mar 2012 |
| 91.236.207.0/24 | 256 | RIPE NCC |  SE | 14th Mar 2012 |
| 91.236.213.0/24 | 256 | RIPE NCC | RU | 11th Nov 2019 |
| 91.236.229.0/24 | 256 | RIPE NCC | PL | 15th Mar 2012 |
| 91.236.45.0/24 | 256 | RIPE NCC |  CH | 28th Feb 2012 |
| 91.236.59.0/24 | 256 | RIPE NCC |  ES | 29th Feb 2012 |
| 91.236.78.0/24 | 256 | RIPE NCC | CH | 29th Feb 2012 |
| 91.236.83.0/24 | 256 | RIPE NCC | NL | 1st Mar 2012 |
| 91.237.12.0/22 | 1k | RIPE NCC | UA | 16th Mar 2012 |
| 91.237.129.0/24 | 256 | RIPE NCC | NL | 11th Nov 2019 |
| 91.237.152.0/24 | 256 | RIPE NCC | UA | 27th Mar 2012 |
| 91.237.153.0/24 | 256 | RIPE NCC | NL | 11th Nov 2019 |
| 91.237.163.0/24 | 256 | RIPE NCC | RU | 27th Mar 2012 |
| 91.237.164.0/22 | 1k | RIPE NCC |  SC | 28th Mar 2012 |
| 91.237.174.0/23 | 512 | RIPE NCC |  US | 28th Mar 2012 |
| 91.237.177.0/24 | 256 | RIPE NCC | NL | 11th Nov 2019 |