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 |
|---|---|---|---|---|
| 167.168.0.0/16 | 65.5k | RIPE NCC |  CH | 1st Sept 1993 |
| 169.36.0.0/15 | 131k | RIPE NCC | CH | 1st Sept 1993 |
| 169.39.0.0/16 | 65.5k | RIPE NCC | CH | 1st Sept 1993 |
| 169.41.0.0/16 | 65.5k | RIPE NCC | CH | 1st Sept 1993 |
| 169.42.0.0/15 | 131k | RIPE NCC | CH | 1st Sept 1993 |
| 169.49.0.0/16 | 65.5k | RIPE NCC | CH | 1st Sept 1993 |
| 169.52.0.0/16 | 65.5k | RIPE NCC | CH | 1st Sept 1993 |
| 170.236.0.0/16 | 65.5k | RIPE NCC | CH | 26th Mar 1997 |
| 170.237.128.0/17 | 32.8k | RIPE NCC | CH | 26th Mar 1997 |
| 170.237.16.0/20 | 4.1k | RIPE NCC | CH | 26th Mar 1997 |
| 170.237.32.0/19 | 8.2k | RIPE NCC | CH | 26th Mar 1997 |
| 170.237.64.0/18 | 16.4k | RIPE NCC | CH | 26th Mar 1997 |
| 170.60.0.0/16 | 65.5k | RIPE NCC | CH | 22nd Feb 1994 |
| 171.25.0.0/17 | 32.8k | RIPE NCC | CH | 9th Aug 1994 |
| 171.33.0.0/18 | 16.4k | RIPE NCC | CH | 10th Feb 1995 |
| 176.223.119.0/24 | 256 | RIPE NCC | CH | 29th Nov 2011 |
| 178.250.24.0/21 | 2k | RIPE NCC | CH | 31st May 2010 |
| 185.0.30.0/24 | 256 | RIPE NCC | CH | 5th Jun 2023 |
| 185.0.31.0/24 | 256 | RIPE NCC | CH | 9th Jun 2023 |
| 185.0.40.0/26 | 64 | RIPE NCC | CH | 17th Jul 2025 |
| 185.1.105.0/24 | 256 | RIPE NCC | CH | 22nd Nov 2017 |
| 185.1.135.0/24 | 256 | RIPE NCC | CH | 10th May 2019 |
| 185.1.147.0/24 | 256 | RIPE NCC | CH | 23rd Feb 2022 |
| 185.1.154.0/24 | 256 | RIPE NCC | CH | 3rd Dec 2019 |
| 185.1.205.0/24 | 256 | RIPE NCC | CH | 28th May 2021 |
| 185.1.216.0/24 | 256 | RIPE NCC | CH | 20th Sept 2021 |
| 185.1.59.0/24 | 256 | RIPE NCC | CH | 19th Sept 2018 |
| 185.1.93.0/24 | 256 | RIPE NCC | CH | 26th Jun 2017 |
| 185.104.60.0/23 | 512 | RIPE NCC | CH | 11th Jun 2015 |
| 185.106.64.0/22 | 1k | RIPE NCC | CH | 25th Jun 2015 |
| 185.109.36.0/22 | 1k | RIPE NCC | CH | 14th Jul 2015 |
| 185.110.220.0/22 | 1k | RIPE NCC | CH | 27th Jul 2015 |
| 185.112.8.0/22 | 1k | RIPE NCC | CH | 3rd Aug 2015 |
| 185.116.113.0/24 | 256 | RIPE NCC | CH | 10th Jan 2024 |
| 185.117.227.0/24 | 256 | RIPE NCC | CH | 13th Mar 2020 |
| 185.124.132.0/22 | 1k | RIPE NCC | CH | 3rd Nov 2015 |
| 185.125.196.0/22 | 1k | RIPE NCC | CH | 11th Nov 2015 |
| 185.131.4.0/22 | 1k | RIPE NCC | CH | 11th Dec 2015 |
| 185.139.184.0/22 | 1k | RIPE NCC | CH | 19th Feb 2016 |
| 185.140.88.0/22 | 1k | RIPE NCC | CH | 24th Feb 2016 |
| 185.147.188.0/22 | 1k | RIPE NCC | CH | 15th Apr 2016 |
| 185.148.136.0/22 | 1k | RIPE NCC | CH | 21st Apr 2016 |
| 185.157.122.0/24 | 256 | RIPE NCC | CH | 1st Apr 2020 |
| 185.166.93.0/24 | 256 | RIPE NCC | CH | 22nd Jan 2026 |
| 185.167.80.0/22 | 1k | RIPE NCC | CH | 9th Sept 2016 |
| 185.169.106.0/24 | 256 | RIPE NCC | CH | 12th Jan 2024 |
| 185.18.172.0/22 | 1k | RIPE NCC | CH | 13th Feb 2013 |
| 185.190.32.0/22 | 1k | RIPE NCC | CH | 15th Feb 2017 |
| 185.194.180.0/22 | 1k | RIPE NCC | CH | 15th Mar 2017 |
| 185.196.136.0/22 | 1k | RIPE NCC | CH | 27th Mar 2017 |