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,221 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.104.61.0/24 | 256 | RIPE NCC |  CH | 19th Oct 2009 |
| 193.104.65.0/24 | 256 | RIPE NCC |  AT | 20th Oct 2009 |
| 193.104.9.0/24 | 256 | RIPE NCC |  DE | 30th Sept 2009 |
| 193.104.91.0/24 | 256 | RIPE NCC |  GB | 28th Oct 2009 |
| 193.105.10.0/24 | 256 | RIPE NCC |  DK | 7th Jan 2010 |
| 193.105.101.0/24 | 256 | RIPE NCC |  NL | 5th Feb 2010 |
| 193.105.102.0/24 | 256 | RIPE NCC |  FI | 15th Nov 2019 |
| 193.105.117.0/24 | 256 | RIPE NCC | FI | 15th Nov 2019 |
| 193.105.118.0/24 | 256 | RIPE NCC |  RU | 12th Feb 2010 |
| 193.105.120.0/24 | 256 | RIPE NCC | GB | 15th Feb 2010 |
| 193.105.121.0/24 | 256 | RIPE NCC | FI | 15th Nov 2019 |
| 193.105.140.0/24 | 256 | RIPE NCC |  RO | 18th Feb 2010 |
| 193.105.145.0/24 | 256 | RIPE NCC |  IE | 19th Feb 2010 |
| 193.105.15.0/24 | 256 | RIPE NCC |  MC | 19th Nov 2019 |
| 193.105.170.0/24 | 256 | RIPE NCC | GB | 3rd Mar 2010 |
| 193.105.171.0/24 | 256 | RIPE NCC |  UA | 4th Mar 2010 |
| 193.105.173.0/24 | 256 | RIPE NCC |  US | 6th Aug 2010 |
| 193.105.177.0/24 | 256 | RIPE NCC | US | 15th Nov 2019 |
| 193.105.180.0/24 | 256 | RIPE NCC |  PL | 5th Mar 2010 |
| 193.105.183.0/24 | 256 | RIPE NCC | NL | 8th Mar 2010 |
| 193.105.186.0/24 | 256 | RIPE NCC |  FR | 9th Mar 2010 |
| 193.105.187.0/24 | 256 | RIPE NCC | DE | 8th Jun 2020 |
| 193.105.194.0/24 | 256 | RIPE NCC | RU | 9th Jun 2026 |
| 193.105.202.0/24 | 256 | RIPE NCC | PL | 15th Mar 2010 |
| 193.105.203.0/24 | 256 | RIPE NCC |  IL | 17th Aug 2011 |
| 193.105.213.0/24 | 256 | RIPE NCC | RU | 17th Mar 2010 |
| 193.105.214.0/24 | 256 | RIPE NCC | AT | 17th Mar 2010 |
| 193.105.221.0/24 | 256 | RIPE NCC | PL | 18th Mar 2010 |
| 193.105.232.0/24 | 256 | RIPE NCC | FR | 22nd Mar 2010 |
| 193.105.24.0/24 | 256 | RIPE NCC | PL | 12th Jan 2010 |
| 193.105.244.0/23 | 512 | RIPE NCC |  HK | 10th Oct 2019 |
| 193.105.34.0/24 | 256 | RIPE NCC |  ES | 14th Jan 2010 |
| 193.105.42.0/24 | 256 | RIPE NCC |  GR | 19th Jan 2010 |
| 193.105.44.0/24 | 256 | RIPE NCC | DK | 19th Jan 2010 |
| 193.105.57.0/24 | 256 | RIPE NCC |  GI | 21st Jan 2010 |
| 193.105.78.0/24 | 256 | RIPE NCC | RO | 15th Aug 2011 |
| 193.105.8.0/24 | 256 | RIPE NCC |  SA | 6th Jan 2010 |
| 193.105.80.0/24 | 256 | RIPE NCC | GR | 29th Jan 2010 |
| 193.105.81.0/24 | 256 | RIPE NCC |  CZ | 15th Nov 2019 |
| 193.105.86.0/24 | 256 | RIPE NCC | AT | 29th Jan 2010 |
| 193.105.89.0/24 | 256 | RIPE NCC | SA | 1st Feb 2010 |
| 193.105.90.0/24 | 256 | RIPE NCC | FR | 17th Jun 2009 |
| 193.106.112.0/22 | 1k | RIPE NCC | RU | 24th Dec 2009 |
| 193.106.148.0/24 | 256 | RIPE NCC |  SE | 19th Oct 2022 |
| 193.106.149.0/24 | 256 | RIPE NCC | RO | 19th Oct 2022 |
| 193.106.191.0/24 | 256 | RIPE NCC | RU | 4th Dec 2023 |
| 193.106.220.0/22 | 1k | RIPE NCC | UA | 20th Jan 2010 |
| 193.106.32.0/22 | 1k | RIPE NCC | DE | 4th May 2018 |
| 193.106.44.0/22 | 1k | RIPE NCC | RO | 3rd Dec 2009 |
| 193.107.188.0/22 | 1k | RIPE NCC | RU | 5th Mar 2010 |