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,356 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 212.102.122.0/24 | 256 | RIPE NCC |  IT | 19th Dec 2019 |
| 212.102.127.0/24 | 256 | RIPE NCC |  DE | 19th Dec 2019 |
| 212.102.96.0/24 | 256 | RIPE NCC |  GR | 19th Dec 2019 |
| 212.103.63.0/24 | 256 | RIPE NCC | DE | 2nd Nov 2018 |
| 212.104.131.0/24 | 256 | RIPE NCC |  RU | 26th Jan 2026 |
| 212.104.133.0/24 | 256 | RIPE NCC |  AT | 26th Jan 2026 |
| 212.104.151.0/24 | 256 | RIPE NCC |  TR | 29th Dec 1998 |
| 212.104.157.0/24 | 256 | RIPE NCC |  GB | 29th Dec 1998 |
| 212.108.100.0/24 | 256 | RIPE NCC |  SA | 28th Jul 2025 |
| 212.108.102.0/24 | 256 | RIPE NCC |  IR | 28th Jul 2025 |
| 212.108.106.0/24 | 256 | RIPE NCC | GR | 16th Jun 2026 |
| 212.108.110.0/24 | 256 | RIPE NCC | DE | 28th Jul 2025 |
| 212.108.111.0/24 | 256 | RIPE NCC |  AE | 28th Jul 2025 |
| 212.108.119.0/24 | 256 | RIPE NCC |  CY | 29th Jul 2025 |
| 212.108.121.0/24 | 256 | RIPE NCC |  PL | 29th Jul 2025 |
| 212.108.127.0/24 | 256 | RIPE NCC | IR | 30th Jul 2025 |
| 212.108.80.0/23 | 512 | RIPE NCC | GB | 15th Jan 1999 |
| 212.108.84.0/24 | 256 | RIPE NCC | GB | 15th Jan 1999 |
| 212.108.96.0/24 | 256 | RIPE NCC | IT | 28th Jul 2025 |
| 212.109.168.0/21 | 2k | RIPE NCC | RU | 5th Mar 2012 |
| 212.110.66.0/23 | 512 | RIPE NCC |  MK | 21st Jan 1999 |
| 212.110.68.0/22 | 1k | RIPE NCC | MK | 21st Jan 1999 |
| 212.110.72.0/22 | 1k | RIPE NCC | MK | 21st Jan 1999 |
| 212.110.76.0/22 | 1k | RIPE NCC | MK | 21st Jan 1999 |
| 212.110.80.0/21 | 2k | RIPE NCC | MK | 21st Jan 1999 |
| 212.110.88.0/22 | 1k | RIPE NCC | MK | 21st Jan 1999 |
| 212.115.104.0/22 | 1k | RIPE NCC |  NL | 5th Nov 2018 |
| 212.115.32.0/22 | 1k | RIPE NCC | DE | 2nd Nov 2018 |
| 212.115.60.0/22 | 1k | RIPE NCC |  RO | 5th Nov 2018 |
| 212.117.224.0/19 | 8.2k | RIPE NCC | GB | 9th Jun 2000 |
| 212.117.32.0/20 | 4.1k | RIPE NCC |  US | 30th Jan 2008 |
| 212.119.128.0/19 | 8.2k | RIPE NCC |  SE | 8th Jan 1999 |
| 212.119.56.0/22 | 1k | RIPE NCC | GB | 6th Nov 2018 |
| 212.119.60.0/22 | 1k | RIPE NCC | SE | 6th Nov 2018 |
| 212.119.96.0/19 | 8.2k | RIPE NCC | RU | 2nd Dec 1999 |
| 212.129.96.0/19 | 8.2k | RIPE NCC | RU | 22nd Jan 2003 |
| 212.132.0.0/19 | 8.2k | RIPE NCC | GB | 19th Nov 1998 |
| 212.132.128.0/19 | 8.2k | RIPE NCC | SE | 19th Nov 1998 |
| 212.152.0.0/19 | 8.2k | RIPE NCC | SE | 9th Nov 1998 |
| 212.158.174.0/23 | 512 | RIPE NCC | RU | 14th Jul 1999 |
| 212.16.112.0/20 | 4.1k | RIPE NCC | NL | 13th Aug 1999 |
| 212.173.0.0/17 | 32.8k | RIPE NCC | GB | 12th May 1999 |
| 212.18.109.0/24 | 256 | RIPE NCC | PL | 11th Jan 2024 |
| 212.19.232.0/23 | 512 | RIPE NCC | NL | 18th Oct 1999 |
| 212.19.237.0/24 | 256 | RIPE NCC | NL | 18th Oct 1999 |
| 212.19.238.0/23 | 512 | RIPE NCC | NL | 18th Oct 1999 |
| 212.19.240.0/20 | 4.1k | RIPE NCC | NL | 18th Oct 1999 |
| 212.192.160.0/21 | 2k | RIPE NCC | RU | 15th Jan 1998 |
| 212.192.170.0/23 | 512 | RIPE NCC | RU | 15th Jan 1998 |
| 212.192.172.0/22 | 1k | RIPE NCC | RU | 15th Jan 1998 |