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,239 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.223.104.0/22 | 1k | RIPE NCC |  TR | 9th May 2018 |
| 193.223.112.0/20 | 4.1k | RIPE NCC |  CH | 1st Sept 1993 |
| 193.223.128.0/19 | 8.2k | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.160.0/21 | 2k | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.168.0/23 | 512 | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.170.0/24 | 256 | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.171.0/24 | 256 | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.172.0/22 | 1k | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.176.0/20 | 4.1k | RIPE NCC |  FR | 1st Sept 1993 |
| 193.223.2.0/23 | 512 | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.4.0/22 | 1k | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.8.0/21 | 2k | RIPE NCC | CH | 1st Sept 1993 |
| 193.227.100.0/24 | 256 | RIPE NCC |  PL | 12th Jan 2007 |
| 193.227.101.0/24 | 256 | RIPE NCC | CH | 30th Aug 2006 |
| 193.227.102.0/24 | 256 | RIPE NCC |  LT | 30th Aug 2006 |
| 193.227.105.0/24 | 256 | RIPE NCC | PL | 30th Aug 2006 |
| 193.227.106.0/24 | 256 | RIPE NCC |  GB | 31st Aug 2006 |
| 193.227.118.0/24 | 256 | RIPE NCC | GB | 5th Sept 2006 |
| 193.227.126.0/24 | 256 | RIPE NCC |  SE | 7th Sept 2006 |
| 193.227.128.0/24 | 256 | AFRINIC |  EG | 19th Nov 1995 |
| 193.227.132.0/24 | 256 | RIPE NCC |  ES | 14th Jun 2005 |
| 193.227.136.0/21 | 2k | RIPE NCC | FR | 5th Aug 1996 |
| 193.227.200.0/23 | 512 | RIPE NCC | GB | 28th Jan 2000 |
| 193.227.224.0/23 | 512 | RIPE NCC | CH | 3rd Oct 2005 |
| 193.227.226.0/24 | 256 | RIPE NCC | CH | 13th Jul 2026 |
| 193.227.227.0/24 | 256 | RIPE NCC |  US | 17th Jul 2026 |
| 193.227.246.0/23 | 512 | RIPE NCC | GB | 12th Oct 2005 |
| 193.227.254.0/23 | 512 | RIPE NCC |  DE | 18th Oct 2005 |
| 193.228.12.0/22 | 1k | RIPE NCC |  RO | 9th May 2018 |
| 193.228.138.0/24 | 256 | RIPE NCC | FR | 12th May 2021 |
| 193.228.141.0/24 | 256 | RIPE NCC | GB | 10th Jul 2007 |
| 193.228.144.0/24 | 256 | RIPE NCC | FR | 16th Jun 2025 |
| 193.228.147.0/24 | 256 | RIPE NCC | FR | 17th Jul 2007 |
| 193.228.159.0/24 | 256 | RIPE NCC |  RU | 20th Jul 2007 |
| 193.228.170.0/23 | 512 | RIPE NCC |  AT | 27th Jun 1995 |
| 193.228.172.0/23 | 512 | RIPE NCC |  BG | 16th Oct 2019 |
| 193.228.182.0/23 | 512 | RIPE NCC | BG | 16th Oct 2019 |
| 193.228.187.0/24 | 256 | RIPE NCC | DE | 18th Sept 1995 |
| 193.228.192.0/24 | 256 | RIPE NCC | AT | 26th Sept 1995 |
| 193.228.203.0/24 | 256 | RIPE NCC | AT | 9th Nov 1995 |
| 193.228.207.0/24 | 256 | RIPE NCC | AT | 14th Nov 1995 |
| 193.228.240.0/20 | 4.1k | RIPE NCC | DE | 19th Dec 1995 |
| 193.228.63.0/24 | 256 | RIPE NCC | AT | 20th Apr 1995 |
| 193.228.64.0/21 | 2k | RIPE NCC | AT | 13th Apr 1995 |
| 193.228.88.0/23 | 512 | RIPE NCC | AT | 2nd May 1995 |
| 193.228.92.0/24 | 256 | RIPE NCC | AT | 8th May 1995 |
| 193.23.120.0/24 | 256 | RIPE NCC | US | 29th Jun 2004 |
| 193.23.136.0/24 | 256 | RIPE NCC | TR | 28th Apr 2026 |
| 193.23.140.0/24 | 256 | RIPE NCC |  UA | 19th Feb 2009 |
| 193.23.158.0/24 | 256 | RIPE NCC | PL | 11th Jul 2024 |