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 |
|---|---|---|---|---|
| 57.60.0.0/16 | 65.5k | RIPE NCC |  CH | 21st Jun 1993 |
| 57.8.0.0/14 | 262k | RIPE NCC | CH | 21st Jun 1993 |
| 77.81.50.0/23 | 512 | RIPE NCC | CH | 15th Feb 2007 |
| 80.173.148.0/22 | 1k | RIPE NCC | CH | 11th Jun 2003 |
| 80.73.252.0/24 | 256 | RIPE NCC | CH | 7th Feb 2005 |
| 82.202.184.0/23 | 512 | RIPE NCC | CH | 6th Oct 2003 |
| 85.217.208.0/21 | 2k | RIPE NCC | CH | 18th Jan 2005 |
| 87.236.178.0/23 | 512 | RIPE NCC | CH | 31st Aug 2005 |
| 87.239.224.0/21 | 2k | RIPE NCC | CH | 30th Mar 2006 |
| 89.106.201.0/24 | 256 | RIPE NCC | CH | 25th Jan 2022 |
| 89.145.176.0/21 | 2k | RIPE NCC | CH | 13th Sept 2011 |
| 89.249.32.0/21 | 2k | RIPE NCC | CH | 18th Jul 2006 |
| 89.46.116.0/22 | 1k | RIPE NCC | CH | 29th Nov 2005 |
| 91.193.20.0/22 | 1k | RIPE NCC | CH | 23rd Mar 2007 |
| 91.193.90.0/24 | 256 | RIPE NCC | CH | 7th Aug 2023 |
| 91.198.6.0/24 | 256 | RIPE NCC | CH | 20th Jun 2007 |
| 91.199.186.0/24 | 256 | RIPE NCC | CH | 11th Feb 2008 |
| 91.201.212.0/23 | 512 | RIPE NCC | CH | 13th Aug 2012 |
| 91.206.52.0/23 | 512 | RIPE NCC | CH | 17th Jun 2008 |
| 91.207.12.0/24 | 256 | RIPE NCC | CH | 14th Jan 2025 |
| 91.208.180.0/24 | 256 | RIPE NCC | CH | 1st Sept 2008 |
| 91.208.30.0/24 | 256 | RIPE NCC | CH | 7th Jul 2008 |
| 91.209.134.0/24 | 256 | RIPE NCC | CH | 19th Nov 2008 |
| 91.209.170.0/24 | 256 | RIPE NCC | CH | 2nd Dec 2008 |
| 91.209.204.0/24 | 256 | RIPE NCC | CH | 16th Dec 2008 |
| 91.209.41.0/24 | 256 | RIPE NCC | CH | 20th Oct 2008 |
| 91.212.200.0/24 | 256 | RIPE NCC | CH | 12th May 2009 |
| 91.213.128.0/24 | 256 | RIPE NCC | CH | 6th Aug 2009 |
| 91.213.159.0/24 | 256 | RIPE NCC | CH | 17th Aug 2009 |
| 91.213.171.0/24 | 256 | RIPE NCC | CH | 19th Aug 2009 |
| 91.216.40.0/24 | 256 | RIPE NCC | CH | 6th Sept 2021 |
| 91.216.83.0/24 | 256 | RIPE NCC | CH | 12th May 2010 |
| 91.216.84.0/23 | 512 | RIPE NCC | CH | 12th May 2010 |
| 91.220.64.0/24 | 256 | RIPE NCC | CH | 22nd Oct 2010 |
| 91.229.140.0/24 | 256 | RIPE NCC | CH | 20th Jun 2011 |
| 91.230.216.0/24 | 256 | RIPE NCC | CH | 27th Jan 2026 |
| 91.233.126.0/24 | 256 | RIPE NCC | CH | 9th Dec 2011 |
| 91.236.45.0/24 | 256 | RIPE NCC | CH | 28th Feb 2012 |
| 91.236.78.0/24 | 256 | RIPE NCC | CH | 29th Feb 2012 |
| 92.119.204.0/22 | 1k | RIPE NCC | CH | 12th Mar 2019 |
| 92.119.37.0/24 | 256 | RIPE NCC | CH | 7th Jun 2021 |
| 92.42.3.0/24 | 256 | RIPE NCC | CH | 3rd May 2023 |
| 93.123.14.0/23 | 512 | RIPE NCC | CH | 5th Mar 2008 |
| 93.123.82.0/23 | 512 | RIPE NCC | CH | 5th Mar 2008 |
| 94.177.100.0/22 | 1k | RIPE NCC | CH | 14th Aug 2008 |
| 94.177.140.0/22 | 1k | RIPE NCC | CH | 14th Aug 2008 |
| 94.244.192.0/18 | 16.4k | RIPE NCC | CH | 5th Jun 2009 |
| 95.130.200.0/21 | 2k | RIPE NCC | CH | 16th Mar 2009 |
| 95.183.48.0/20 | 4.1k | RIPE NCC | CH | 10th Feb 2009 |
| 95.36.100.0/22 | 1k | RIPE NCC | CH | 18th Nov 2008 |