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.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.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 | RU | 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 |
| 185.36.12.0/22 | 1k | RIPE NCC |  FR | 24th Sept 2013 |
| 185.36.152.0/22 | 1k | RIPE NCC | PL | 1st Oct 2013 |
| 185.36.196.0/22 | 1k | RIPE NCC |  UA | 2nd Oct 2013 |
| 185.36.20.0/24 | 256 | RIPE NCC |  AT | 16th Jun 2026 |
| 185.36.21.0/24 | 256 | RIPE NCC |  IT | 16th Jun 2026 |
| 185.36.23.0/24 | 256 | RIPE NCC | RU | 16th Jun 2026 |
| 185.36.64.0/22 | 1k | RIPE NCC | FR | 26th Sept 2013 |
| 185.36.8.0/22 | 1k | RIPE NCC | GB | 24th Sept 2013 |
| 185.37.10.0/24 | 256 | RIPE NCC | UA | 7th Mar 2023 |
| 185.37.140.0/22 | 1k | RIPE NCC | SE | 14th Oct 2013 |
| 185.37.172.0/22 | 1k | RIPE NCC | GB | 14th Oct 2013 |
| 185.37.236.0/24 | 256 | RIPE NCC |  KZ | 16th Jan 2025 |
| 185.37.237.0/24 | 256 | RIPE NCC |  DK | 16th Jan 2025 |
| 185.37.244.0/22 | 1k | RIPE NCC |  NL | 16th Oct 2013 |
| 185.38.136.0/22 | 1k | RIPE NCC | IT | 23rd Oct 2013 |
| 185.38.172.0/24 | 256 | RIPE NCC | DE | 23rd Jan 2026 |
| 185.38.180.0/22 | 1k | RIPE NCC | DK | 24th Oct 2013 |
| 185.38.188.0/22 | 1k | RIPE NCC |  CZ | 24th Oct 2013 |
| 185.38.196.0/22 | 1k | RIPE NCC | FR | 24th Oct 2013 |
| 185.38.220.0/24 | 256 | RIPE NCC | PL | 25th Oct 2013 |
| 185.38.222.0/23 | 512 | RIPE NCC | PL | 25th Oct 2013 |
| 185.38.96.0/22 | 1k | RIPE NCC | SE | 22nd Oct 2013 |
| 185.39.11.0/24 | 256 | RIPE NCC | AT | 8th Dec 2021 |
| 185.39.128.0/22 | 1k | RIPE NCC |  FI | 31st Oct 2013 |
| 185.39.132.0/22 | 1k | RIPE NCC | RU | 31st Oct 2013 |
| 185.39.156.0/22 | 1k | RIPE NCC | FR | 4th Nov 2013 |
| 185.39.236.0/22 | 1k | RIPE NCC |  ZA | 7th Nov 2013 |
| 185.39.96.0/22 | 1k | RIPE NCC |  ES | 31st Oct 2013 |
| 185.4.136.0/22 | 1k | RIPE NCC | DK | 26th Sept 2012 |