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.200.115.0/24 | 256 | RIPE NCC |  CH | 28th Jan 2026 |
| 193.200.12.0/23 | 512 | RIPE NCC |  RU | 15th Oct 2019 |
| 193.200.131.0/24 | 256 | RIPE NCC |  LV | 24th Apr 2007 |
| 193.200.135.0/24 | 256 | RIPE NCC |  BE | 26th Apr 2007 |
| 193.200.14.0/23 | 512 | RIPE NCC |  BG | 7th Feb 1996 |
| 193.200.142.0/24 | 256 | RIPE NCC |  AT | 27th Apr 2007 |
| 193.200.150.0/24 | 256 | RIPE NCC |  DE | 22nd Jun 2026 |
| 193.200.154.0/24 | 256 | RIPE NCC |  RS | 24th Apr 2023 |
| 193.200.166.0/24 | 256 | RIPE NCC |  GB | 10th May 2007 |
| 193.200.174.0/24 | 256 | RIPE NCC |  NL | 14th May 2007 |
| 193.200.177.0/24 | 256 | RIPE NCC |  US | 15th May 2007 |
| 193.200.184.0/24 | 256 | RIPE NCC | US | 18th May 2007 |
| 193.200.185.0/24 | 256 | RIPE NCC | BE | 18th May 2007 |
| 193.200.192.0/24 | 256 | RIPE NCC | GB | 25th Mar 2020 |
| 193.200.193.0/24 | 256 | RIPE NCC | DE | 21st May 2007 |
| 193.200.198.0/24 | 256 | RIPE NCC | NL | 23rd May 2007 |
| 193.200.208.0/24 | 256 | RIPE NCC |  SE | 24th May 2007 |
| 193.200.210.0/24 | 256 | RIPE NCC | DE | 25th May 2007 |
| 193.200.218.0/24 | 256 | RIPE NCC | DE | 8th Jan 2009 |
| 193.200.222.0/24 | 256 | RIPE NCC |  IE | 31st May 2007 |
| 193.200.226.0/24 | 256 | RIPE NCC |  PL | 31st Mar 2010 |
| 193.200.230.0/24 | 256 | RIPE NCC | DE | 5th Jun 2007 |
| 193.200.245.0/24 | 256 | RIPE NCC | GB | 12th Jun 2007 |
| 193.200.249.0/24 | 256 | RIPE NCC | DE | 13th Jun 2007 |
| 193.200.25.0/24 | 256 | RIPE NCC | GB | 22nd Jan 2007 |
| 193.200.56.0/23 | 512 | RIPE NCC |  FI | 15th Oct 2019 |
| 193.200.58.0/23 | 512 | RIPE NCC |  FR | 23rd Mar 2007 |
| 193.200.70.0/23 | 512 | RIPE NCC | NL | 1st Mar 2007 |
| 193.200.79.0/24 | 256 | RIPE NCC | CH | 6th Mar 2024 |
| 193.201.100.0/24 | 256 | RIPE NCC |  UA | 18th Jun 2002 |
| 193.201.101.0/24 | 256 | RIPE NCC |  SI | 19th Jun 2002 |
| 193.201.103.0/24 | 256 | RIPE NCC | FR | 19th Jun 2002 |
| 193.201.104.0/24 | 256 | RIPE NCC | NL | 20th Jun 2002 |
| 193.201.108.0/24 | 256 | RIPE NCC |  ES | 27th Jun 2002 |
| 193.201.140.0/22 | 1k | RIPE NCC | GB | 11th Jul 2002 |
| 193.201.144.0/25 | 128 | RIPE NCC | PL | 21st Mar 2011 |
| 193.201.144.128/25 | 128 | RIPE NCC | FI | 4th Sept 2002 |
| 193.201.145.0/25 | 128 | RIPE NCC | FI | 3rd Sept 2009 |
| 193.201.145.128/26 | 64 | RIPE NCC | DE | 11th Dec 2024 |
| 193.201.145.192/26 | 64 | RIPE NCC | DE | 12th Dec 2024 |
| 193.201.146.0/25 | 128 | RIPE NCC | FR | 23rd Dec 2003 |
| 193.201.146.128/25 | 128 | RIPE NCC |  RO | 14th Jul 2010 |
| 193.201.147.0/26 | 64 | RIPE NCC |  IL | 16th May 2025 |
| 193.201.147.160/27 | 32 | RIPE NCC |  CY | 14th Sept 2012 |
| 193.201.147.224/27 | 32 | RIPE NCC | US | 29th Jun 2004 |
| 193.201.147.64/27 | 32 | RIPE NCC | NL | 4th Jul 2003 |
| 193.201.148.0/26 | 64 | RIPE NCC | CY | 14th Sept 2012 |
| 193.201.148.128/26 | 64 | RIPE NCC | SE | 29th Sept 2023 |
| 193.201.148.192/26 | 64 | RIPE NCC | NL | 27th Aug 2010 |
| 193.201.148.64/26 | 64 | RIPE NCC | DE | 9th May 2003 |