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 unannounced space registered through RIPE NCC, largest first.
Unannounced blocks registered through RIPE NCC
25,283 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.19.32.0/19 | 8.2k | RIPE NCC |  FR | 31st May 1994 |
| 193.19.68.0/23 | 512 | RIPE NCC |  RU | 21st Nov 2003 |
| 193.19.72.0/23 | 512 | RIPE NCC |  PS | 4th Oct 2019 |
| 193.19.96.0/23 | 512 | RIPE NCC | PS | 4th Oct 2019 |
| 193.19.98.0/24 | 256 | RIPE NCC |  LU | 10th Jul 2023 |
| 193.19.99.0/24 | 256 | RIPE NCC |  LT | 10th Jul 2023 |
| 193.192.12.0/26 | 64 | RIPE NCC |  CZ | 11th Nov 2024 |
| 193.192.12.128/25 | 128 | RIPE NCC |  CY | 14th Sept 2012 |
| 193.192.12.64/26 | 64 | RIPE NCC |  GB | 18th Nov 2024 |
| 193.192.128.0/19 | 8.2k | RIPE NCC | RU | 14th May 1996 |
| 193.192.13.0/24 | 256 | RIPE NCC | GB | 15th Nov 1999 |
| 193.192.16.0/20 | 4.1k | RIPE NCC | GB | 6th Jun 1996 |
| 193.192.34.0/23 | 512 | RIPE NCC | GB | 4th Aug 2005 |
| 193.193.161.0/24 | 256 | RIPE NCC |  DK | 6th Jul 2026 |
| 193.193.164.0/24 | 256 | RIPE NCC |  SC | 18th Nov 2019 |
| 193.193.188.0/23 | 512 | RIPE NCC | GB | 27th Apr 2000 |
| 193.193.32.0/19 | 8.2k | RIPE NCC | GB | 22nd May 1996 |
| 193.194.105.0/24 | 256 | RIPE NCC | RU | 5th Sept 2011 |
| 193.194.146.0/24 | 256 | RIPE NCC |  AT | 5th Mar 1999 |
| 193.194.158.0/24 | 256 | RIPE NCC |  US | 29th Jul 1999 |
| 193.194.192.0/18 | 16.4k | RIPE NCC |  SE | 18th Mar 1996 |
| 193.194.22.0/23 | 512 | RIPE NCC | GB | 29th Apr 1997 |
| 193.194.24.0/21 | 2k | RIPE NCC | GB | 29th Apr 1997 |
| 193.194.6.0/23 | 512 | RIPE NCC |  DE | 1st Aug 1997 |
| 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 |