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
24,902 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.28.45.0/24 | 256 | RIPE NCC |  NL | 17th Feb 2025 |
| 185.28.56.0/22 | 1k | RIPE NCC | NL | 11th Jun 2013 |
| 185.28.64.0/22 | 1k | RIPE NCC |  IT | 11th Jun 2013 |
| 185.29.172.0/22 | 1k | RIPE NCC |  GB | 28th Jun 2013 |
| 185.29.208.0/24 | 256 | RIPE NCC | GB | 1st Oct 2024 |
| 185.29.209.0/24 | 256 | RIPE NCC | IT | 1st Oct 2024 |
| 185.29.228.0/23 | 512 | RIPE NCC |  AU | 3rd Jul 2013 |
| 185.29.96.0/22 | 1k | RIPE NCC | IT | 2nd Jul 2013 |
| 185.3.16.0/22 | 1k | RIPE NCC |  RU | 19th Sept 2012 |
| 185.3.164.0/22 | 1k | RIPE NCC | GB | 21st Sept 2012 |
| 185.3.244.0/22 | 1k | RIPE NCC |  HU | 24th Sept 2012 |
| 185.3.85.0/24 | 256 | RIPE NCC |  DE | 20th Sept 2012 |
| 185.30.148.0/22 | 1k | RIPE NCC |  SA | 11th Jul 2013 |
| 185.30.216.0/22 | 1k | RIPE NCC |  FR | 17th Jul 2013 |
| 185.30.240.0/22 | 1k | RIPE NCC |  ES | 18th Jul 2013 |
| 185.30.36.0/22 | 1k | RIPE NCC |  LB | 4th Jul 2013 |
| 185.30.8.0/22 | 1k | RIPE NCC | GB | 3rd Jul 2013 |
| 185.30.88.0/22 | 1k | RIPE NCC |  AZ | 9th Jul 2013 |
| 185.31.10.0/24 | 256 | RIPE NCC | NL | 2nd Jul 2024 |
| 185.31.152.0/22 | 1k | RIPE NCC | GB | 24th Jul 2013 |
| 185.31.202.0/24 | 256 | RIPE NCC |  LT | 5th Dec 2023 |
| 185.31.203.0/24 | 256 | RIPE NCC |  CZ | 5th Dec 2023 |
| 185.31.232.0/22 | 1k | RIPE NCC | GB | 29th Jul 2013 |
| 185.31.252.0/22 | 1k | RIPE NCC | GB | 30th Jul 2013 |
| 185.31.9.0/24 | 256 | RIPE NCC |  EE | 2nd Jul 2024 |
| 185.32.140.0/22 | 1k | RIPE NCC | NL | 6th Aug 2013 |
| 185.32.192.0/22 | 1k | RIPE NCC |  US | 8th Aug 2013 |
| 185.32.236.0/22 | 1k | RIPE NCC |  LU | 14th Aug 2013 |
| 185.32.24.0/22 | 1k | RIPE NCC |  RO | 31st Jul 2013 |
| 185.32.40.0/22 | 1k | RIPE NCC | GB | 31st Jul 2013 |
| 185.32.71.0/24 | 256 | RIPE NCC |  PL | 4th Apr 2023 |
| 185.33.124.0/23 | 512 | RIPE NCC |  KW | 20th Aug 2013 |
| 185.33.126.0/24 | 256 | RIPE NCC | KW | 20th Aug 2013 |
| 185.33.16.0/22 | 1k | RIPE NCC | LU | 15th Aug 2013 |
| 185.33.168.0/22 | 1k | RIPE NCC |  PS | 22nd Aug 2013 |
| 185.33.20.0/22 | 1k | RIPE NCC |  CH | 15th Aug 2013 |
| 185.33.220.0/22 | 1k | RIPE NCC | US | 23rd Aug 2013 |
| 185.33.240.0/22 | 1k | RIPE NCC |  SE | 26th Aug 2013 |
| 185.33.82.0/23 | 512 | RIPE NCC | HU | 16th Aug 2013 |
| 185.34.100.0/24 | 256 | RIPE NCC | DE | 10th Jun 2021 |
| 185.34.112.0/22 | 1k | RIPE NCC | DE | 2nd Sept 2013 |
| 185.34.116.0/22 | 1k | RIPE NCC | GB | 2nd Sept 2013 |
| 185.34.64.0/23 | 512 | RIPE NCC | RO | 29th Aug 2013 |
| 185.35.0.0/22 | 1k | RIPE NCC | RU | 11th Sept 2013 |
| 185.35.104.0/22 | 1k | RIPE NCC |  AE | 16th Sept 2013 |
| 185.35.24.0/22 | 1k | RIPE NCC | GB | 12th Sept 2013 |
| 185.35.44.0/22 | 1k | RIPE NCC | RU | 13th Sept 2013 |
| 185.36.100.0/24 | 256 | RIPE NCC |  TR | 10th Jan 2024 |
| 185.36.101.0/24 | 256 | RIPE NCC |  PT | 10th Jan 2024 |
| 185.36.108.0/22 | 1k | RIPE NCC | GB | 30th Sept 2013 |