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 in Switzerland
950 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.135.154.0/23 | 512 | RIPE NCC |  CH | 28th May 1997 |
| 193.135.158.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.135.16.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.135.160.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.135.175.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.135.176.0/20 | 4.1k | RIPE NCC | CH | 28th May 1997 |
| 193.135.192.0/20 | 4.1k | RIPE NCC | CH | 28th May 1997 |
| 193.135.208.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.135.212.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.135.22.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.135.224.0/20 | 4.1k | RIPE NCC | CH | 28th May 1997 |
| 193.135.248.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.135.25.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.135.31.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.135.32.0/21 | 2k | RIPE NCC | CH | 28th May 1997 |
| 193.135.4.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.135.60.0/22 | 1k | RIPE NCC | CH | 28th May 1997 |
| 193.138.69.0/24 | 256 | RIPE NCC | CH | 7th Feb 2003 |
| 193.142.62.0/24 | 256 | RIPE NCC | CH | 14th Mar 2007 |
| 193.148.192.0/19 | 8.2k | RIPE NCC | CH | 1st Sept 1993 |
| 193.16.44.0/24 | 256 | RIPE NCC | CH | 5th Nov 2003 |
| 193.160.124.0/23 | 512 | RIPE NCC | CH | 15th May 1995 |
| 193.161.240.0/22 | 1k | RIPE NCC | CH | 2nd Mar 1995 |
| 193.161.244.0/24 | 256 | RIPE NCC | CH | 2nd Mar 1995 |
| 193.164.244.0/23 | 512 | RIPE NCC | CH | 14th Jul 2000 |
| 193.168.165.0/24 | 256 | RIPE NCC | CH | 5th May 2026 |
| 193.169.152.0/23 | 512 | RIPE NCC | CH | 20th Jul 2009 |
| 193.17.201.0/24 | 256 | RIPE NCC | CH | 8th Oct 2004 |
| 193.17.64.0/24 | 256 | RIPE NCC | CH | 13th Nov 2019 |
| 193.188.224.0/20 | 4.1k | RIPE NCC | CH | 12th Jan 1996 |
| 193.200.115.0/24 | 256 | RIPE NCC | CH | 28th Jan 2026 |
| 193.200.79.0/24 | 256 | RIPE NCC | CH | 6th Mar 2024 |
| 193.201.150.192/26 | 64 | RIPE NCC | CH | 9th Nov 2023 |
| 193.201.22.0/24 | 256 | RIPE NCC | CH | 19th Jan 2026 |
| 193.202.46.0/23 | 512 | RIPE NCC | CH | 12th Oct 1993 |
| 193.202.48.0/21 | 2k | RIPE NCC | CH | 12th Oct 1993 |
| 193.202.56.0/22 | 1k | RIPE NCC | CH | 12th Oct 1993 |
| 193.202.60.0/23 | 512 | RIPE NCC | CH | 12th Oct 1993 |
| 193.218.205.0/26 | 64 | RIPE NCC | CH | 19th Nov 2007 |
| 193.218.207.16/28 | 16 | RIPE NCC | CH | 26th Jan 2011 |
| 193.218.207.32/27 | 32 | RIPE NCC | CH | 26th Jan 2011 |
| 193.222.0.0/19 | 8.2k | RIPE NCC | CH | 1st Sept 1993 |
| 193.222.176.0/21 | 2k | RIPE NCC | CH | 1st Sept 1993 |
| 193.222.184.0/22 | 1k | RIPE NCC | CH | 1st Sept 1993 |
| 193.222.32.0/20 | 4.1k | RIPE NCC | CH | 1st Sept 1993 |
| 193.223.1.0/24 | 256 | RIPE NCC | CH | 1st Sept 1993 |
| 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 |