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.207.52.0/22 | 1k | RIPE NCC |  IR | 7th Jun 2017 |
| 185.208.108.0/22 | 1k | RIPE NCC |  TR | 14th Jun 2017 |
| 185.208.12.0/22 | 1k | RIPE NCC |  AT | 12th Jun 2017 |
| 185.208.124.0/22 | 1k | RIPE NCC |  NL | 15th Jun 2017 |
| 185.208.168.0/22 | 1k | RIPE NCC | AT | 15th Jun 2017 |
| 185.208.24.0/22 | 1k | RIPE NCC |  IT | 13th Jun 2017 |
| 185.208.48.0/22 | 1k | RIPE NCC |  BG | 13th Jun 2017 |
| 185.209.0.0/22 | 1k | RIPE NCC |  LV | 19th Jun 2017 |
| 185.209.14.0/24 | 256 | RIPE NCC |  DE | 4th Nov 2020 |
| 185.209.200.0/22 | 1k | RIPE NCC |  SY | 22nd Jun 2017 |
| 185.209.24.0/22 | 1k | RIPE NCC |  RU | 19th Jun 2017 |
| 185.209.252.0/22 | 1k | RIPE NCC | DE | 23rd Jun 2017 |
| 185.209.80.0/24 | 256 | RIPE NCC | BG | 5th Nov 2020 |
| 185.209.83.0/24 | 256 | RIPE NCC |  GB | 5th Nov 2020 |
| 185.21.100.0/22 | 1k | RIPE NCC | DE | 14th Mar 2013 |
| 185.21.133.0/24 | 256 | RIPE NCC | GB | 20th Jul 2020 |
| 185.21.200.0/22 | 1k | RIPE NCC | NL | 19th Mar 2013 |
| 185.21.44.0/22 | 1k | RIPE NCC |  ES | 12th Mar 2013 |
| 185.21.5.0/24 | 256 | RIPE NCC | TR | 11th Mar 2013 |
| 185.210.104.0/22 | 1k | RIPE NCC | GB | 27th Jun 2017 |
| 185.210.132.0/22 | 1k | RIPE NCC |  DK | 28th Jun 2017 |
| 185.210.161.0/24 | 256 | RIPE NCC | GB | 6th Nov 2020 |
| 185.210.162.0/24 | 256 | RIPE NCC | IT | 6th Nov 2020 |
| 185.210.164.0/22 | 1k | RIPE NCC |  IE | 28th Jun 2017 |
| 185.210.212.0/22 | 1k | RIPE NCC | IT | 29th Jun 2017 |
| 185.210.228.0/24 | 256 | RIPE NCC |  IQ | 12th Mar 2026 |
| 185.210.231.0/24 | 256 | RIPE NCC |  UZ | 16th Mar 2026 |
| 185.210.252.0/22 | 1k | RIPE NCC | TR | 30th Jun 2017 |
| 185.210.48.0/22 | 1k | RIPE NCC | IT | 26th Jun 2017 |
| 185.210.52.0/23 | 512 | RIPE NCC | DE | 27th Jun 2017 |
| 185.210.8.0/22 | 1k | RIPE NCC | DE | 23rd Jun 2017 |
| 185.211.104.0/22 | 1k | RIPE NCC |  KW | 4th Jul 2017 |
| 185.211.144.0/22 | 1k | RIPE NCC | DE | 4th Jul 2017 |
| 185.211.34.0/24 | 256 | RIPE NCC | DE | 30th Jun 2017 |
| 185.211.36.0/22 | 1k | RIPE NCC |  SK | 30th Jun 2017 |
| 185.211.84.0/22 | 1k | RIPE NCC | IR | 3rd Jul 2017 |
| 185.212.117.0/24 | 256 | RIPE NCC | RU | 7th Sept 2021 |
| 185.212.118.0/24 | 256 | RIPE NCC | DE | 7th Sept 2021 |
| 185.212.132.0/22 | 1k | RIPE NCC |  PL | 12th Jul 2017 |
| 185.212.144.0/22 | 1k | RIPE NCC |  US | 12th Jul 2017 |
| 185.212.176.0/22 | 1k | RIPE NCC | IT | 12th Jul 2017 |
| 185.212.228.0/22 | 1k | RIPE NCC | IE | 13th Jul 2017 |
| 185.212.68.0/24 | 256 | RIPE NCC | DE | 11th Jul 2017 |
| 185.213.12.0/22 | 1k | RIPE NCC | NL | 14th Jul 2017 |
| 185.213.123.0/24 | 256 | RIPE NCC |  AZ | 19th Jul 2017 |
| 185.213.180.0/22 | 1k | RIPE NCC |  VG | 19th Jul 2017 |
| 185.213.236.0/22 | 1k | RIPE NCC | DE | 20th Jul 2017 |
| 185.213.28.0/22 | 1k | RIPE NCC | RU | 14th Jul 2017 |
| 185.213.72.0/22 | 1k | RIPE NCC |  FR | 17th Jul 2017 |
| 185.213.96.0/22 | 1k | RIPE NCC | DE | 17th Jul 2017 |