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.133.176.0/22 | 1k | RIPE NCC |  GB | 6th Jan 2016 |
| 185.133.192.0/22 | 1k | RIPE NCC |  AT | 7th Jan 2016 |
| 185.133.252.0/22 | 1k | RIPE NCC |  US | 11th Jan 2016 |
| 185.133.34.0/24 | 256 | RIPE NCC |  TR | 27th Jan 2026 |
| 185.134.105.0/24 | 256 | RIPE NCC |  BE | 28th May 2025 |
| 185.134.188.0/24 | 256 | RIPE NCC |  HU | 11th Aug 2025 |
| 185.134.190.0/24 | 256 | RIPE NCC |  FR | 11th Aug 2025 |
| 185.134.200.0/22 | 1k | RIPE NCC |  RU | 18th Jan 2016 |
| 185.134.4.0/24 | 256 | RIPE NCC |  DE | 11th Jan 2016 |
| 185.134.5.0/24 | 256 | RIPE NCC | DE | 11th Jan 2016 |
| 185.134.92.0/22 | 1k | RIPE NCC |  SE | 14th Jan 2016 |
| 185.135.0.0/22 | 1k | RIPE NCC |  PL | 19th Jan 2016 |
| 185.135.108.0/22 | 1k | RIPE NCC | TR | 21st Jan 2016 |
| 185.135.152.0/22 | 1k | RIPE NCC | US | 22nd Jan 2016 |
| 185.135.196.0/24 | 256 | RIPE NCC | FR | 3rd Feb 2026 |
| 185.135.197.0/24 | 256 | RIPE NCC | PL | 3rd Feb 2026 |
| 185.135.199.0/24 | 256 | RIPE NCC |  SA | 5th Feb 2026 |
| 185.135.24.0/22 | 1k | RIPE NCC | DE | 20th Jan 2016 |
| 185.135.45.0/24 | 256 | RIPE NCC |  PA | 7th Mar 2023 |
| 185.135.46.0/24 | 256 | RIPE NCC |  IR | 7th Mar 2023 |
| 185.136.140.0/22 | 1k | RIPE NCC | DE | 1st Feb 2016 |
| 185.136.228.0/22 | 1k | RIPE NCC | AT | 2nd Feb 2016 |
| 185.136.232.0/22 | 1k | RIPE NCC | GB | 2nd Feb 2016 |
| 185.136.240.0/24 | 256 | RIPE NCC | GB | 21st Jan 2026 |
| 185.136.241.0/24 | 256 | RIPE NCC |  IT | 21st Jan 2026 |
| 185.136.32.0/22 | 1k | RIPE NCC |  AM | 27th Jan 2016 |
| 185.136.60.0/22 | 1k | RIPE NCC | GB | 27th Jan 2016 |
| 185.136.8.0/22 | 1k | RIPE NCC |  RO | 26th Jan 2016 |
| 185.137.157.0/24 | 256 | RIPE NCC | DE | 7th Jan 2025 |
| 185.137.192.0/22 | 1k | RIPE NCC | GB | 8th Feb 2016 |
| 185.137.243.0/24 | 256 | RIPE NCC | GB | 8th Feb 2016 |
| 185.137.44.0/22 | 1k | RIPE NCC |  ES | 3rd Feb 2016 |
| 185.137.96.0/24 | 256 | RIPE NCC | FR | 6th Feb 2023 |
| 185.137.99.0/24 | 256 | RIPE NCC |  EE | 7th Feb 2023 |
| 185.138.0.0/22 | 1k | RIPE NCC | GB | 9th Feb 2016 |
| 185.138.12.0/22 | 1k | RIPE NCC |  AZ | 9th Feb 2016 |
| 185.138.164.0/24 | 256 | RIPE NCC |  MD | 29th Jun 2021 |
| 185.138.192.0/22 | 1k | RIPE NCC | US | 15th Feb 2016 |
| 185.138.24.0/22 | 1k | RIPE NCC | DE | 9th Feb 2016 |
| 185.138.60.0/22 | 1k | RIPE NCC | IT | 10th Feb 2016 |
| 185.138.96.0/22 | 1k | RIPE NCC | BE | 11th Feb 2016 |
| 185.139.144.0/22 | 1k | RIPE NCC | GB | 18th Feb 2016 |
| 185.139.180.0/24 | 256 | RIPE NCC | IT | 19th Feb 2016 |
| 185.139.184.0/22 | 1k | RIPE NCC |  CH | 19th Feb 2016 |
| 185.139.218.0/23 | 512 | RIPE NCC |  CZ | 22nd Feb 2016 |
| 185.139.72.0/22 | 1k | RIPE NCC | DE | 18th Feb 2016 |
| 185.139.84.0/22 | 1k | RIPE NCC |  CA | 18th Feb 2016 |
| 185.139.96.0/22 | 1k | RIPE NCC | DE | 18th Feb 2016 |
| 185.14.152.0/22 | 1k | RIPE NCC | GB | 31st Dec 2012 |
| 185.14.192.0/22 | 1k | RIPE NCC |  UA | 4th Jan 2013 |