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,273 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.104.127.0/24 | 256 | RIPE NCC |  RU | 11th Nov 2009 |
| 193.104.137.0/24 | 256 | RIPE NCC |  IT | 12th Nov 2009 |
| 193.104.140.0/24 | 256 | RIPE NCC |  GG | 18th Nov 2009 |
| 193.104.141.0/24 | 256 | RIPE NCC |  SE | 15th Nov 2019 |
| 193.104.142.0/24 | 256 | RIPE NCC |  NL | 15th Nov 2019 |
| 193.104.144.0/24 | 256 | RIPE NCC |  GB | 19th Nov 2009 |
| 193.104.147.0/24 | 256 | RIPE NCC |  IL | 19th Nov 2009 |
| 193.104.153.0/24 | 256 | RIPE NCC | NL | 15th Nov 2019 |
| 193.104.176.0/24 | 256 | RIPE NCC | NL | 15th Nov 2019 |
| 193.104.181.0/24 | 256 | RIPE NCC | GB | 30th Dec 2024 |
| 193.104.185.0/24 | 256 | RIPE NCC |  CH | 7th Dec 2009 |
| 193.104.186.0/24 | 256 | RIPE NCC | NL | 7th Dec 2009 |
| 193.104.19.0/24 | 256 | RIPE NCC |  FR | 2nd Oct 2009 |
| 193.104.190.0/24 | 256 | RIPE NCC | NL | 15th Nov 2019 |
| 193.104.204.0/24 | 256 | RIPE NCC |  SA | 14th Dec 2009 |
| 193.104.21.0/24 | 256 | RIPE NCC |  RO | 5th Oct 2009 |
| 193.104.215.0/24 | 256 | RIPE NCC |  IE | 16th Dec 2009 |
| 193.104.221.0/24 | 256 | RIPE NCC |  PL | 18th Dec 2009 |
| 193.104.228.0/24 | 256 | RIPE NCC |  DK | 17th Nov 2009 |
| 193.104.23.0/24 | 256 | RIPE NCC |  SI | 5th Oct 2009 |
| 193.104.255.0/24 | 256 | RIPE NCC | NL | 4th Jan 2010 |
| 193.104.44.0/24 | 256 | RIPE NCC |  ES | 13th Oct 2009 |
| 193.104.6.0/24 | 256 | RIPE NCC | NL | 30th Sept 2009 |
| 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 |