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 the most unannounced blocks, largest first.
Unannounced blocks
85,075 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.18.156.0/22 | 1k | RIPE NCC |  IR | 12th Feb 2013 |
| 185.18.160.0/22 | 1k | RIPE NCC |  EE | 12th Feb 2013 |
| 185.18.172.0/22 | 1k | RIPE NCC |  CH | 13th Feb 2013 |
| 185.18.88.0/23 | 512 | RIPE NCC |  RU | 7th Mar 2016 |
| 185.180.136.0/22 | 1k | RIPE NCC |  SK | 5th Dec 2016 |
| 185.180.164.0/22 | 1k | RIPE NCC |  DE | 6th Dec 2016 |
| 185.180.176.0/22 | 1k | RIPE NCC | RU | 6th Dec 2016 |
| 185.180.208.0/22 | 1k | RIPE NCC |  PL | 7th Dec 2016 |
| 185.180.4.0/22 | 1k | RIPE NCC |  GB | 1st Dec 2016 |
| 185.180.84.0/22 | 1k | RIPE NCC |  AE | 5th Dec 2016 |
| 185.181.172.0/22 | 1k | RIPE NCC |  IE | 12th Dec 2016 |
| 185.181.184.0/22 | 1k | RIPE NCC |  CZ | 13th Dec 2016 |
| 185.181.200.0/22 | 1k | RIPE NCC | RU | 13th Dec 2016 |
| 185.181.56.0/22 | 1k | RIPE NCC | CZ | 8th Dec 2016 |
| 185.181.88.0/22 | 1k | RIPE NCC |  SE | 9th Dec 2016 |
| 185.182.16.0/22 | 1k | RIPE NCC | RU | 14th Dec 2016 |
| 185.182.60.0/22 | 1k | RIPE NCC |  AT | 14th Dec 2016 |
| 185.183.204.0/22 | 1k | RIPE NCC | DE | 29th Dec 2016 |
| 185.183.52.0/22 | 1k | RIPE NCC | DE | 20th Dec 2016 |
| 185.183.8.0/22 | 1k | RIPE NCC | CZ | 20th Dec 2016 |
| 185.183.85.0/24 | 256 | RIPE NCC | DE | 21st Dec 2016 |
| 185.183.86.0/23 | 512 | RIPE NCC | DE | 21st Dec 2016 |
| 185.183.96.0/24 | 256 | RIPE NCC |  NL | 22nd Dec 2016 |
| 185.184.112.0/22 | 1k | RIPE NCC | PL | 3rd Jan 2017 |
| 185.184.140.0/22 | 1k | RIPE NCC | AT | 4th Jan 2017 |
| 185.184.180.0/22 | 1k | RIPE NCC | NL | 5th Jan 2017 |
| 185.184.188.0/22 | 1k | RIPE NCC | DE | 5th Jan 2017 |
| 185.184.217.0/24 | 256 | RIPE NCC |  AL | 29th Jun 2021 |
| 185.184.218.0/24 | 256 | RIPE NCC | GB | 29th Jun 2021 |
| 185.184.229.0/24 | 256 | RIPE NCC |  IM | 16th Sept 2020 |
| 185.184.36.0/22 | 1k | RIPE NCC |  IT | 2nd Jan 2017 |
| 185.184.41.0/24 | 256 | RIPE NCC | AT | 16th Aug 2023 |
| 185.184.48.0/22 | 1k | RIPE NCC | IR | 2nd Jan 2017 |
| 185.184.53.0/24 | 256 | RIPE NCC |  UZ | 2nd Jan 2017 |
| 185.184.76.0/24 | 256 | RIPE NCC | RU | 3rd Jan 2017 |
| 185.184.80.0/22 | 1k | RIPE NCC | PL | 3rd Jan 2017 |
| 185.185.120.0/22 | 1k | RIPE NCC | RU | 12th Jan 2017 |
| 185.185.156.0/22 | 1k | RIPE NCC |  GR | 13th Jan 2017 |
| 185.185.248.0/22 | 1k | RIPE NCC | AT | 16th Jan 2017 |
| 185.185.42.0/24 | 256 | RIPE NCC | GB | 10th Jan 2017 |
| 185.185.84.0/22 | 1k | RIPE NCC | GB | 11th Jan 2017 |
| 185.186.100.0/22 | 1k | RIPE NCC | GB | 18th Jan 2017 |
| 185.186.112.0/22 | 1k | RIPE NCC |  BG | 18th Jan 2017 |
| 185.186.164.0/22 | 1k | RIPE NCC | GB | 19th Jan 2017 |
| 185.186.176.0/22 | 1k | RIPE NCC |  PS | 20th Jan 2017 |
| 185.186.200.0/22 | 1k | RIPE NCC |  ES | 20th Jan 2017 |
| 185.186.236.0/22 | 1k | RIPE NCC | DE | 23rd Jan 2017 |
| 185.186.24.0/22 | 1k | RIPE NCC | DE | 17th Jan 2017 |
| 185.186.52.0/24 | 256 | RIPE NCC | AE | 17th Jan 2017 |
| 185.186.96.0/22 | 1k | RIPE NCC | PL | 18th Jan 2017 |