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,778 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 91.200.149.0/24 | 256 | RIPE NCC |  RU | 19th Apr 2018 |
| 91.200.152.0/22 | 1k | RIPE NCC |  SE | 16th Oct 2007 |
| 91.200.164.0/22 | 1k | RIPE NCC | RU | 17th Oct 2007 |
| 91.200.179.0/24 | 256 | RIPE NCC |  IT | 22nd May 2020 |
| 91.200.196.0/22 | 1k | RIPE NCC |  MT | 26th Oct 2007 |
| 91.200.228.0/22 | 1k | RIPE NCC | RU | 7th Nov 2007 |
| 91.200.63.0/24 | 256 | RIPE NCC |  CY | 25th Jul 2012 |
| 91.201.128.0/22 | 1k | RIPE NCC |  DE | 12th Dec 2007 |
| 91.201.170.0/24 | 256 | RIPE NCC |  US | 14th Aug 2020 |
| 91.201.192.0/22 | 1k | RIPE NCC |  RO | 7th Jan 2008 |
| 91.201.212.0/23 | 512 | RIPE NCC |  CH | 13th Aug 2012 |
| 91.201.238.0/24 | 256 | RIPE NCC | RU | 22nd Jan 2008 |
| 91.201.24.0/24 | 256 | RIPE NCC | RU | 16th Nov 2007 |
| 91.201.8.0/23 | 512 | RIPE NCC | RU | 13th Nov 2007 |
| 91.202.172.0/22 | 1k | RIPE NCC |  PL | 25th Feb 2008 |
| 91.202.28.0/22 | 1k | RIPE NCC |  GB | 19th Apr 2018 |
| 91.202.32.0/22 | 1k | RIPE NCC |  BE | 19th Apr 2018 |
| 91.202.88.0/22 | 1k | RIPE NCC | RO | 12th Feb 2008 |
| 91.202.96.0/22 | 1k | RIPE NCC |  GE | 12th Feb 2008 |
| 91.203.104.0/24 | 256 | RIPE NCC | PL | 8th Jul 2010 |
| 91.203.105.0/24 | 256 | RIPE NCC | RU | 5th Aug 2010 |
| 91.203.120.0/23 | 512 | RIPE NCC |  IL | 17th Apr 2008 |
| 91.203.122.0/23 | 512 | RIPE NCC | IL | 17th Apr 2008 |
| 91.203.148.0/22 | 1k | RIPE NCC |  NL | 22nd Apr 2008 |
| 91.203.224.0/24 | 256 | RIPE NCC | RU | 14th May 2008 |
| 91.203.23.0/24 | 256 | RIPE NCC |  KZ | 14th Mar 2008 |
| 91.203.235.0/24 | 256 | RIPE NCC | RU | 15th May 2008 |
| 91.203.248.0/22 | 1k | RIPE NCC | PL | 20th May 2008 |
| 91.203.252.0/22 | 1k | RIPE NCC | RU | 28th Dec 2011 |
| 91.203.40.0/22 | 1k | RIPE NCC | SE | 19th Mar 2008 |
| 91.203.76.0/22 | 1k | RIPE NCC | NL | 19th Apr 2018 |
| 91.204.100.0/22 | 1k | RIPE NCC | RU | 9th Jun 2008 |
| 91.204.112.0/22 | 1k | RIPE NCC |  UA | 12th Aug 2011 |
| 91.204.12.0/22 | 1k | RIPE NCC | UA | 26th May 2008 |
| 91.204.236.0/22 | 1k | RIPE NCC |  UZ | 17th Jul 2008 |
| 91.204.40.0/22 | 1k | RIPE NCC | GB | 26th Jun 2018 |
| 91.204.80.0/24 | 256 | APNIC |  AU | 4th Jun 2008 |
| 91.204.83.0/24 | 256 | RIPE NCC | NL | 4th Jun 2008 |
| 91.205.100.0/22 | 1k | RIPE NCC | US | 29th Aug 2008 |
| 91.205.159.0/24 | 256 | RIPE NCC |  NO | 2nd Mar 2020 |
| 91.205.228.0/24 | 256 | RIPE NCC | GB | 27th May 2020 |
| 91.205.252.0/22 | 1k | RIPE NCC | RU | 3rd Oct 2008 |
| 91.206.122.0/24 | 256 | RIPE NCC | DE | 25th Jan 2022 |
| 91.206.130.0/23 | 512 | RIPE NCC | GE | 21st Jul 2008 |
| 91.206.144.0/23 | 512 | RIPE NCC |  IM | 25th Jul 2008 |
| 91.206.170.0/24 | 256 | RIPE NCC |  DK | 2nd Sept 2024 |
| 91.206.172.0/23 | 512 | RIPE NCC | PL | 4th Aug 2008 |
| 91.206.186.0/23 | 512 | RIPE NCC | UA | 7th Aug 2008 |
| 91.206.202.0/23 | 512 | RIPE NCC |  AT | 3rd Oct 2019 |
| 91.206.204.0/23 | 512 | RIPE NCC | AT | 3rd Oct 2019 |