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.214.248.0/22 | 1k | RIPE NCC |  BG | 26th Jul 2017 |
| 185.214.32.0/22 | 1k | RIPE NCC |  PT | 21st Jul 2017 |
| 185.214.40.0/23 | 512 | RIPE NCC |  RS | 24th Jul 2017 |
| 185.214.42.0/24 | 256 | RIPE NCC | RS | 24th Jul 2017 |
| 185.214.68.0/22 | 1k | RIPE NCC |  AT | 25th Jul 2017 |
| 185.214.80.0/23 | 512 | RIPE NCC |  ES | 25th Jul 2017 |
| 185.215.112.0/24 | 256 | RIPE NCC |  CH | 13th Nov 2020 |
| 185.215.113.0/24 | 256 | RIPE NCC |  SC | 13th Nov 2020 |
| 185.215.188.0/22 | 1k | RIPE NCC |  DE | 2nd Aug 2017 |
| 185.215.208.0/22 | 1k | RIPE NCC | DE | 2nd Aug 2017 |
| 185.215.212.0/22 | 1k | RIPE NCC | AT | 2nd Aug 2017 |
| 185.215.48.0/22 | 1k | RIPE NCC |  US | 27th Jul 2017 |
| 185.215.7.0/24 | 256 | RIPE NCC | CH | 12th Apr 2021 |
| 185.216.108.0/22 | 1k | RIPE NCC |  GB | 4th Aug 2017 |
| 185.216.13.0/24 | 256 | RIPE NCC |  MD | 13th Mar 2023 |
| 185.216.136.0/24 | 256 | RIPE NCC | CH | 7th Aug 2017 |
| 185.216.137.0/24 | 256 | RIPE NCC | GB | 7th Aug 2017 |
| 185.216.224.0/22 | 1k | RIPE NCC | DE | 9th Aug 2017 |
| 185.216.228.0/23 | 512 | RIPE NCC | DE | 9th Aug 2017 |
| 185.216.48.0/24 | 256 | RIPE NCC | GB | 16th Nov 2020 |
| 185.216.56.0/23 | 512 | RIPE NCC | ES | 4th Aug 2017 |
| 185.216.88.0/22 | 1k | RIPE NCC |  IT | 4th Aug 2017 |
| 185.217.100.0/22 | 1k | RIPE NCC |  SA | 14th Aug 2017 |
| 185.217.104.0/22 | 1k | RIPE NCC | GB | 14th Aug 2017 |
| 185.217.112.0/22 | 1k | RIPE NCC | ES | 14th Aug 2017 |
| 185.217.120.0/22 | 1k | RIPE NCC |  FR | 14th Aug 2017 |
| 185.217.129.0/24 | 256 | RIPE NCC |  KZ | 6th Dec 2021 |
| 185.217.132.0/22 | 1k | RIPE NCC | GB | 14th Aug 2017 |
| 185.217.148.0/22 | 1k | RIPE NCC | DE | 15th Aug 2017 |
| 185.217.160.0/22 | 1k | RIPE NCC |  NL | 16th Aug 2017 |
| 185.217.167.0/24 | 256 | RIPE NCC |  RU | 20th Nov 2020 |
| 185.217.36.0/24 | 256 | RIPE NCC | FR | 17th Nov 2020 |
| 185.217.4.0/24 | 256 | RIPE NCC | SA | 26th Jun 2023 |
| 185.217.7.0/24 | 256 | RIPE NCC | RU | 28th Jun 2023 |
| 185.217.88.0/22 | 1k | RIPE NCC |  IQ | 14th Aug 2017 |
| 185.218.107.0/24 | 256 | RIPE NCC | DE | 12th Apr 2021 |
| 185.218.112.0/22 | 1k | RIPE NCC |  IE | 22nd Aug 2017 |
| 185.218.116.0/22 | 1k | RIPE NCC | CH | 22nd Aug 2017 |
| 185.218.128.0/22 | 1k | RIPE NCC | DE | 22nd Aug 2017 |
| 185.218.172.0/22 | 1k | RIPE NCC | FR | 23rd Aug 2017 |
| 185.218.176.0/22 | 1k | RIPE NCC |  SG | 24th Aug 2017 |
| 185.218.3.0/24 | 256 | RIPE NCC | MD | 6th Jul 2021 |
| 185.218.52.0/22 | 1k | RIPE NCC | DE | 21st Aug 2017 |
| 185.219.128.0/24 | 256 | RIPE NCC |  IS | 4th Sept 2017 |
| 185.219.129.0/24 | 256 | RIPE NCC | PT | 4th Sept 2017 |
| 185.219.131.0/24 | 256 | RIPE NCC | PT | 4th Sept 2017 |
| 185.219.200.0/22 | 1k | RIPE NCC |  PL | 6th Sept 2017 |
| 185.219.88.0/24 | 256 | RIPE NCC |  EE | 30th Aug 2017 |
| 185.22.164.0/22 | 1k | RIPE NCC | GB | 2nd Apr 2013 |
| 185.220.104.0/22 | 1k | RIPE NCC | NL | 12th Sept 2017 |