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.147.4.0/22 | 1k | RIPE NCC |  DE | 12th Apr 2016 |
| 185.147.54.0/24 | 256 | RIPE NCC | DE | 18th Aug 2021 |
| 185.148.136.0/22 | 1k | RIPE NCC |  CH | 21st Apr 2016 |
| 185.148.16.0/22 | 1k | RIPE NCC |  NO | 18th Apr 2016 |
| 185.148.48.0/22 | 1k | RIPE NCC |  US | 19th Apr 2016 |
| 185.148.60.0/22 | 1k | RIPE NCC |  BG | 19th Apr 2016 |
| 185.148.88.0/22 | 1k | RIPE NCC | DE | 20th Apr 2016 |
| 185.149.116.0/22 | 1k | RIPE NCC |  AE | 26th Apr 2016 |
| 185.149.168.0/22 | 1k | RIPE NCC |  GE | 28th Apr 2016 |
| 185.149.224.0/22 | 1k | RIPE NCC | DE | 28th Apr 2016 |
| 185.149.236.0/22 | 1k | RIPE NCC |  GB | 29th Apr 2016 |
| 185.149.72.0/22 | 1k | RIPE NCC |  ES | 26th Apr 2016 |
| 185.149.84.0/22 | 1k | RIPE NCC |  CW | 26th Apr 2016 |
| 185.15.48.0/22 | 1k | RIPE NCC |  FR | 10th Jan 2013 |
| 185.15.88.0/22 | 1k | RIPE NCC |  RU | 10th Jan 2013 |
| 185.150.108.0/22 | 1k | RIPE NCC |  IR | 2nd May 2016 |
| 185.150.148.0/22 | 1k | RIPE NCC | GB | 3rd May 2016 |
| 185.150.3.0/24 | 256 | RIPE NCC | GB | 29th Apr 2016 |
| 185.151.132.0/22 | 1k | RIPE NCC |  HR | 10th May 2016 |
| 185.151.136.0/22 | 1k | RIPE NCC | GE | 10th May 2016 |
| 185.151.236.0/22 | 1k | RIPE NCC | IR | 13th May 2016 |
| 185.151.76.0/22 | 1k | RIPE NCC |  FI | 9th May 2016 |
| 185.151.88.0/22 | 1k | RIPE NCC |  DK | 9th May 2016 |
| 185.152.152.0/22 | 1k | RIPE NCC |  CZ | 19th May 2016 |
| 185.152.156.0/22 | 1k | RIPE NCC |  IT | 19th May 2016 |
| 185.152.192.0/22 | 1k | RIPE NCC |  CA | 19th May 2016 |
| 185.153.233.0/24 | 256 | RIPE NCC | DE | 30th Sept 2020 |
| 185.153.235.0/24 | 256 | RIPE NCC |  IE | 30th Sept 2020 |
| 185.153.72.0/22 | 1k | RIPE NCC | CZ | 23rd May 2016 |
| 185.153.80.0/22 | 1k | RIPE NCC | CZ | 23rd May 2016 |
| 185.153.88.0/22 | 1k | RIPE NCC | DE | 23rd May 2016 |
| 185.154.104.0/22 | 1k | RIPE NCC | DE | 31st May 2016 |
| 185.154.120.0/22 | 1k | RIPE NCC | RU | 31st May 2016 |
| 185.154.140.0/22 | 1k | RIPE NCC |  BE | 31st May 2016 |
| 185.154.172.0/22 | 1k | RIPE NCC | FR | 2nd Jun 2016 |
| 185.154.176.0/22 | 1k | RIPE NCC | DK | 2nd Jun 2016 |
| 185.154.190.0/24 | 256 | RIPE NCC | IR | 12th Jan 2024 |
| 185.154.191.0/24 | 256 | RIPE NCC | HR | 12th Jan 2024 |
| 185.154.244.0/22 | 1k | RIPE NCC | US | 6th Jun 2016 |
| 185.154.28.0/22 | 1k | RIPE NCC | DE | 27th May 2016 |
| 185.155.117.0/24 | 256 | RIPE NCC |  AT | 27th Jan 2026 |
| 185.155.229.0/24 | 256 | RIPE NCC | IR | 11th Aug 2025 |
| 185.155.230.0/24 | 256 | RIPE NCC | ES | 11th Aug 2025 |
| 185.155.244.0/22 | 1k | RIPE NCC | GB | 14th Jun 2016 |
| 185.155.44.0/22 | 1k | RIPE NCC |  NL | 7th Jun 2016 |
| 185.156.144.0/22 | 1k | RIPE NCC | AT | 17th Jun 2016 |
| 185.156.164.0/22 | 1k | RIPE NCC | GB | 17th Jun 2016 |
| 185.156.168.0/22 | 1k | RIPE NCC | BE | 17th Jun 2016 |
| 185.156.180.0/22 | 1k | RIPE NCC | RU | 20th Jun 2016 |
| 185.156.48.0/24 | 256 | RIPE NCC |  CY | 1st Jun 2026 |