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.32.252.0/23 | 512 | RIPE NCC |  GB | 27th Nov 1992 |
| 193.32.254.0/24 | 256 | RIPE NCC | GB | 28th Nov 1992 |
| 193.32.255.0/24 | 256 | RIPE NCC | GB | 20th Apr 1995 |
| 193.32.3.0/24 | 256 | RIPE NCC |  SE | 17th Aug 1992 |
| 193.32.31.0/24 | 256 | RIPE NCC |  US | 27th Aug 1992 |
| 193.32.32.0/24 | 256 | RIPE NCC | US | 27th Aug 1992 |
| 193.32.33.0/24 | 256 | RIPE NCC | US | 27th Aug 1992 |
| 193.32.35.0/24 | 256 | RIPE NCC | US | 27th Aug 1992 |
| 193.32.39.0/24 | 256 | RIPE NCC | GB | 8th Jun 2007 |
| 193.32.41.0/24 | 256 | RIPE NCC |  CH | 9th Sept 1992 |
| 193.32.42.0/23 | 512 | RIPE NCC | CH | 9th Sept 1992 |
| 193.32.44.0/24 | 256 | RIPE NCC | CH | 9th Sept 1992 |
| 193.32.45.0/24 | 256 | RIPE NCC | GB | 11th Sept 1992 |
| 193.32.52.0/24 | 256 | RIPE NCC |  LV | 20th Jul 2012 |
| 193.32.6.0/23 | 512 | RIPE NCC | GB | 21st Dec 1994 |
| 193.32.82.0/24 | 256 | RIPE NCC | GB | 4th May 1994 |
| 193.32.83.0/24 | 256 | RIPE NCC | GB | 4th May 1994 |
| 193.32.84.0/24 | 256 | RIPE NCC |  LI | 12th Apr 2021 |
| 193.32.88.0/22 | 1k | RIPE NCC | GB | 29th Sept 1992 |
| 193.33.12.0/23 | 512 | RIPE NCC |  FR | 19th Jan 2007 |
| 193.33.138.0/23 | 512 | RIPE NCC | SE | 2nd Apr 2007 |
| 193.33.14.0/23 | 512 | RIPE NCC |  CZ | 19th Jan 2007 |
| 193.33.152.0/24 | 256 | RIPE NCC |  UA | 15th May 2024 |
| 193.33.157.0/24 | 256 | RIPE NCC |  NL | 3rd May 2023 |
| 193.33.162.0/23 | 512 | RIPE NCC | CZ | 8th Oct 2019 |
| 193.33.20.0/23 | 512 | RIPE NCC |  DE | 25th Jan 2007 |
| 193.33.209.0/24 | 256 | RIPE NCC | DE | 20th Dec 2019 |
| 193.33.242.0/23 | 512 | RIPE NCC |  IT | 8th Oct 2019 |
| 193.33.245.0/24 | 256 | RIPE NCC | SE | 8th Sept 2025 |
| 193.33.252.0/23 | 512 | RIPE NCC | IT | 8th Oct 2019 |
| 193.33.35.0/24 | 256 | RIPE NCC | NL | 20th Feb 2023 |
| 193.33.4.0/23 | 512 | RIPE NCC |  PL | 16th Jan 2007 |
| 193.33.49.0/24 | 256 | RIPE NCC | GB | 5th Feb 2007 |
| 193.33.54.0/23 | 512 | RIPE NCC | UA | 7th Feb 2007 |
| 193.33.87.0/24 | 256 | RIPE NCC |  CY | 8th Oct 2019 |
| 193.33.97.0/24 | 256 | RIPE NCC | NL | 31st May 2021 |
| 193.34.130.0/23 | 512 | RIPE NCC | FR | 12th Oct 2006 |
| 193.34.134.0/23 | 512 | RIPE NCC | GB | 29th Jun 2010 |
| 193.34.146.0/23 | 512 | RIPE NCC | GB | 20th Oct 2006 |
| 193.34.156.0/23 | 512 | RIPE NCC |  RO | 23rd Oct 2006 |
| 193.34.192.0/25 | 128 | RIPE NCC | DE | 30th Oct 2006 |
| 193.34.192.128/25 | 128 | RIPE NCC |  MT | 16th Jan 2012 |
| 193.34.193.0/25 | 128 | RIPE NCC | PL | 5th Dec 2006 |
| 193.34.195.0/25 | 128 | RIPE NCC | GB | 3rd Mar 2008 |
| 193.34.195.128/25 | 128 | RIPE NCC | PL | 9th Jan 2009 |
| 193.34.196.0/25 | 128 | RIPE NCC | PL | 5th Mar 2007 |
| 193.34.196.128/25 | 128 | RIPE NCC | UA | 30th Nov 2023 |
| 193.34.197.0/25 | 128 | RIPE NCC | PL | 11th Apr 2007 |
| 193.34.197.128/25 | 128 | RIPE NCC | FR | 28th Aug 2012 |
| 193.34.198.0/26 | 64 | RIPE NCC | CH | 12th Sept 2024 |