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,896 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 45.80.184.0/22 | 1k | RIPE NCC |  DE | 15th May 2019 |
| 45.80.216.0/22 | 1k | RIPE NCC |  RU | 16th May 2019 |
| 45.80.56.0/22 | 1k | RIPE NCC |  SE | 14th May 2019 |
| 45.80.60.0/22 | 1k | RIPE NCC | DE | 14th May 2019 |
| 45.80.84.0/24 | 256 | RIPE NCC |  IR | 28th Jan 2026 |
| 45.81.100.0/22 | 1k | RIPE NCC |  TR | 17th May 2019 |
| 45.81.140.0/22 | 1k | RIPE NCC | TR | 20th May 2019 |
| 45.81.176.0/22 | 1k | RIPE NCC |  BG | 21st May 2019 |
| 45.81.184.0/22 | 1k | RIPE NCC |  NL | 21st May 2019 |
| 45.81.236.0/22 | 1k | RIPE NCC |  AT | 21st May 2019 |
| 45.81.244.0/22 | 1k | RIPE NCC | AT | 21st May 2019 |
| 45.81.41.0/24 | 256 | RIPE NCC |  SK | 17th May 2019 |
| 45.81.42.0/23 | 512 | RIPE NCC |  CZ | 17th May 2019 |
| 45.81.48.0/23 | 512 | RIPE NCC | NL | 17th May 2019 |
| 45.81.50.0/23 | 512 | RIPE NCC | NL | 17th May 2019 |
| 45.81.8.0/22 | 1k | RIPE NCC | AT | 16th May 2019 |
| 45.82.116.0/22 | 1k | RIPE NCC |  HK | 23rd May 2019 |
| 45.82.12.0/24 | 256 | RIPE NCC | RU | 21st May 2019 |
| 45.82.204.0/22 | 1k | RIPE NCC | AT | 24th May 2019 |
| 45.82.208.0/22 | 1k | RIPE NCC |  FR | 24th May 2019 |
| 45.82.24.0/22 | 1k | RIPE NCC | DE | 22nd May 2019 |
| 45.82.248.0/22 | 1k | RIPE NCC |  CY | 27th May 2019 |
| 45.82.252.0/22 | 1k | RIPE NCC | CY | 27th May 2019 |
| 45.82.36.0/22 | 1k | RIPE NCC |  CH | 22nd May 2019 |
| 45.82.57.0/24 | 256 | RIPE NCC | NL | 22nd May 2019 |
| 45.82.58.0/23 | 512 | RIPE NCC | NL | 22nd May 2019 |
| 45.83.112.0/22 | 1k | RIPE NCC | CZ | 27th May 2019 |
| 45.83.128.0/22 | 1k | RIPE NCC | CY | 27th May 2019 |
| 45.83.140.0/22 | 1k | RIPE NCC | CY | 27th May 2019 |
| 45.83.148.0/22 | 1k | RIPE NCC | CY | 27th May 2019 |
| 45.83.196.0/22 | 1k | RIPE NCC | DE | 28th May 2019 |
| 45.83.200.0/22 | 1k | RIPE NCC | NL | 28th May 2019 |
| 45.83.208.0/22 | 1k | RIPE NCC | NL | 28th May 2019 |
| 45.83.252.0/22 | 1k | RIPE NCC | AT | 28th May 2019 |
| 45.83.52.0/22 | 1k | RIPE NCC |  EE | 27th May 2019 |
| 45.83.80.0/22 | 1k | RIPE NCC |  ES | 27th May 2019 |
| 45.84.160.0/22 | 1k | RIPE NCC | DE | 31st May 2019 |
| 45.84.248.0/22 | 1k | RIPE NCC | IR | 3rd Jun 2019 |
| 45.84.37.0/24 | 256 | RIPE NCC |  LB | 31st May 2019 |
| 45.84.38.0/23 | 512 | RIPE NCC | DE | 31st May 2019 |
| 45.84.48.0/22 | 1k | RIPE NCC | ES | 31st May 2019 |
| 45.84.8.0/22 | 1k | RIPE NCC | NL | 28th May 2019 |
| 45.84.88.0/24 | 256 | RIPE NCC | BG | 31st May 2019 |
| 45.85.112.0/22 | 1k | RIPE NCC | DE | 5th Jun 2019 |
| 45.85.189.0/24 | 256 | RIPE NCC | NL | 6th Jun 2019 |
| 45.85.196.0/22 | 1k | RIPE NCC |  IM | 7th Jun 2019 |
| 45.85.32.0/22 | 1k | RIPE NCC | FR | 4th Jun 2019 |
| 45.85.68.0/22 | 1k | RIPE NCC | RU | 4th Jun 2019 |
| 45.85.84.0/22 | 1k | RIPE NCC | AT | 5th Jun 2019 |
| 45.86.120.0/22 | 1k | RIPE NCC |  GB | 12th Jun 2019 |