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
85,108 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.8.100.0/22 | 1k | APNIC |  BN | 30th Oct 2012 |
| 185.8.118.0/23 | 512 | RIPE NCC |  DE | 30th Oct 2012 |
| 185.8.120.0/22 | 1k | RIPE NCC |  IT | 30th Oct 2012 |
| 185.80.104.0/22 | 1k | RIPE NCC |  JO | 8th Dec 2014 |
| 185.80.136.0/22 | 1k | RIPE NCC |  TR | 9th Dec 2014 |
| 185.80.244.0/24 | 256 | RIPE NCC |  NL | 11th Dec 2014 |
| 185.80.89.0/24 | 256 | RIPE NCC |  AT | 7th Mar 2023 |
| 185.81.136.0/22 | 1k | ARIN |  US | 22nd Jun 2020 |
| 185.81.156.0/22 | 1k | RIPE NCC |  FR | 17th Dec 2014 |
| 185.81.204.0/24 | 256 | RIPE NCC | AT | 18th Dec 2014 |
| 185.81.44.0/22 | 1k | RIPE NCC | FR | 12th Dec 2014 |
| 185.81.68.0/24 | 256 | RIPE NCC |  HK | 25th Jan 2022 |
| 185.81.69.0/24 | 256 | RIPE NCC |  BE | 25th Jan 2022 |
| 185.82.155.0/24 | 256 | RIPE NCC | NL | 30th Dec 2014 |
| 185.82.180.0/22 | 1k | RIPE NCC |  IR | 30th Dec 2014 |
| 185.82.186.0/23 | 512 | RIPE NCC | NL | 30th Dec 2014 |
| 185.82.188.0/22 | 1k | RIPE NCC | NL | 30th Dec 2014 |
| 185.82.201.0/24 | 256 | RIPE NCC | NL | 31st Dec 2014 |
| 185.82.203.0/24 | 256 | RIPE NCC | NL | 31st Dec 2014 |
| 185.82.232.0/22 | 1k | RIPE NCC |  HU | 2nd Jan 2015 |
| 185.82.4.0/22 | 1k | RIPE NCC | DE | 19th Dec 2014 |
| 185.83.100.0/22 | 1k | RIPE NCC |  GB | 8th Jan 2015 |
| 185.83.128.0/22 | 1k | RIPE NCC | GB | 8th Jan 2015 |
| 185.83.156.0/23 | 512 | RIPE NCC | US | 9th Jan 2015 |
| 185.83.158.0/24 | 256 | RIPE NCC | US | 9th Jan 2015 |
| 185.83.184.0/22 | 1k | RIPE NCC | IR | 12th Jan 2015 |
| 185.83.244.0/22 | 1k | RIPE NCC | TR | 13th Jan 2015 |
| 185.83.76.0/22 | 1k | RIPE NCC | IR | 7th Jan 2015 |
| 185.84.157.0/24 | 256 | RIPE NCC | IR | 17th Jan 2025 |
| 185.84.168.0/22 | 1k | RIPE NCC | IT | 19th Jan 2015 |
| 185.84.176.0/22 | 1k | RIPE NCC | IT | 19th Jan 2015 |
| 185.84.225.0/24 | 256 | RIPE NCC |  RO | 7th Mar 2023 |
| 185.84.67.0/24 | 256 | RIPE NCC |  IM | 15th Jan 2015 |
| 185.84.76.0/22 | 1k | RIPE NCC |  CH | 15th Jan 2015 |
| 185.85.100.0/22 | 1k | RIPE NCC |  SE | 23rd Jan 2015 |
| 185.85.116.0/22 | 1k | RIPE NCC | GB | 26th Jan 2015 |
| 185.85.140.0/22 | 1k | RIPE NCC | NL | 26th Jan 2015 |
| 185.85.172.0/22 | 1k | RIPE NCC | FR | 27th Jan 2015 |
| 185.85.40.0/22 | 1k | RIPE NCC | DE | 21st Jan 2015 |
| 185.85.48.0/22 | 1k | RIPE NCC | DE | 22nd Jan 2015 |
| 185.85.8.0/22 | 1k | RIPE NCC | CH | 21st Jan 2015 |
| 185.85.80.0/22 | 1k | RIPE NCC | NL | 23rd Jan 2015 |
| 185.85.92.0/22 | 1k | RIPE NCC |  CZ | 23rd Jan 2015 |
| 185.86.136.0/22 | 1k | RIPE NCC | FR | 2nd Feb 2015 |
| 185.86.172.0/22 | 1k | RIPE NCC | DE | 3rd Feb 2015 |
| 185.86.208.0/23 | 512 | RIPE NCC |  ES | 5th Feb 2015 |
| 185.86.240.0/22 | 1k | RIPE NCC |  RS | 5th Feb 2015 |
| 185.86.68.0/22 | 1k | RIPE NCC |  DK | 30th Jan 2015 |
| 185.87.112.0/22 | 1k | RIPE NCC | CH | 10th Feb 2015 |
| 185.87.144.0/22 | 1k | RIPE NCC |  FK | 11th Feb 2015 |