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 unannounced space registered through RIPE NCC, largest first.
Unannounced blocks registered through RIPE NCC
25,269 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.4.192.0/22 | 1k | RIPE NCC |  IE | 27th Sept 2012 |
| 185.4.224.0/23 | 512 | RIPE NCC |  GE | 27th Sept 2012 |
| 185.4.24.0/22 | 1k | RIPE NCC |  GB | 25th Sept 2012 |
| 185.4.56.0/22 | 1k | RIPE NCC |  RU | 25th Sept 2012 |
| 185.40.164.0/22 | 1k | RIPE NCC |  BG | 15th Nov 2013 |
| 185.40.220.0/22 | 1k | RIPE NCC |  IT | 19th Nov 2013 |
| 185.40.24.0/22 | 1k | RIPE NCC |  US | 11th Nov 2013 |
| 185.41.164.0/22 | 1k | RIPE NCC | IT | 27th Nov 2013 |
| 185.41.172.0/22 | 1k | RIPE NCC |  SE | 27th Nov 2013 |
| 185.41.220.0/22 | 1k | RIPE NCC |  IR | 4th Feb 2019 |
| 185.41.44.0/22 | 1k | RIPE NCC | GB | 29th Nov 2013 |
| 185.41.52.0/22 | 1k | RIPE NCC |  CA | 22nd Nov 2013 |
| 185.41.84.0/22 | 1k | RIPE NCC |  SY | 25th Nov 2013 |
| 185.42.0.0/22 | 1k | RIPE NCC | GB | 2nd Dec 2013 |
| 185.42.148.0/22 | 1k | RIPE NCC | US | 27th May 2019 |
| 185.42.200.0/22 | 1k | RIPE NCC |  NL | 11th Dec 2013 |
| 185.42.204.0/22 | 1k | RIPE NCC | US | 11th Dec 2013 |
| 185.43.100.0/22 | 1k | RIPE NCC | RU | 19th Dec 2013 |
| 185.43.216.0/22 | 1k | RIPE NCC | GB | 23rd Dec 2013 |
| 185.43.34.0/24 | 256 | RIPE NCC | NL | 4th May 2026 |
| 185.44.0.0/22 | 1k | RIPE NCC | RU | 27th Dec 2013 |
| 185.44.178.0/23 | 512 | RIPE NCC |  DE | 9th Jan 2014 |
| 185.44.180.0/22 | 1k | RIPE NCC | IT | 9th Jan 2014 |
| 185.44.188.0/22 | 1k | RIPE NCC |  CZ | 9th Jan 2014 |
| 185.44.224.0/22 | 1k | RIPE NCC | NL | 10th Jan 2014 |
| 185.44.32.0/22 | 1k | RIPE NCC | DE | 27th Dec 2013 |
| 185.46.0.0/22 | 1k | RIPE NCC | IR | 27th Jan 2014 |
| 185.46.108.0/22 | 1k | RIPE NCC | IR | 30th Jan 2014 |
| 185.46.140.0/24 | 256 | RIPE NCC |  SI | 10th Jan 2024 |
| 185.46.152.0/24 | 256 | RIPE NCC | RU | 31st Jan 2014 |
| 185.46.153.0/24 | 256 | RIPE NCC | RU | 31st Jan 2014 |
| 185.46.154.0/24 | 256 | RIPE NCC | RU | 31st Jan 2014 |
| 185.46.156.0/22 | 1k | RIPE NCC | NL | 31st Jan 2014 |
| 185.46.165.0/24 | 256 | RIPE NCC |  FR | 3rd Feb 2014 |
| 185.46.166.0/23 | 512 | RIPE NCC |  BE | 3rd Feb 2014 |
| 185.46.237.0/24 | 256 | RIPE NCC |  ZA | 30th Jun 2025 |
| 185.46.4.0/22 | 1k | RIPE NCC |  CH | 20th Feb 2018 |
| 185.47.100.0/22 | 1k | RIPE NCC | US | 11th Feb 2014 |
| 185.47.166.0/24 | 256 | RIPE NCC |  AE | 11th Jan 2024 |
| 185.47.196.0/22 | 1k | RIPE NCC | NL | 14th Feb 2014 |
| 185.47.20.0/22 | 1k | RIPE NCC | NL | 6th Feb 2014 |
| 185.47.24.0/22 | 1k | RIPE NCC | CH | 6th Feb 2014 |
| 185.47.7.0/24 | 256 | RIPE NCC |  AZ | 6th Feb 2014 |
| 185.47.72.0/22 | 1k | RIPE NCC | IE | 10th Feb 2014 |
| 185.48.184.0/22 | 1k | RIPE NCC |  MT | 24th Feb 2014 |
| 185.48.6.0/24 | 256 | RIPE NCC | FR | 11th Aug 2025 |
| 185.48.7.0/24 | 256 | RIPE NCC | CZ | 11th Aug 2025 |
| 185.49.104.0/23 | 512 | RIPE NCC | IR | 4th Mar 2014 |
| 185.49.88.0/22 | 1k | RIPE NCC | BG | 28th Feb 2014 |
| 185.49.92.0/22 | 1k | RIPE NCC | GB | 3rd Mar 2014 |