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.201.149.0/26 | 64 | RIPE NCC |  DE | 3rd Jul 2023 |
| 193.201.149.128/26 | 64 | RIPE NCC |  GB | 25th Feb 2026 |
| 193.201.149.192/26 | 64 | RIPE NCC |  CY | 14th Sept 2012 |
| 193.201.149.64/26 | 64 | RIPE NCC |  PL | 12th May 2010 |
| 193.201.150.0/26 | 64 | RIPE NCC |  US | 29th Jun 2004 |
| 193.201.150.128/26 | 64 | RIPE NCC | CY | 14th Sept 2012 |
| 193.201.150.192/26 | 64 | RIPE NCC |  CH | 9th Nov 2023 |
| 193.201.150.64/26 | 64 | RIPE NCC | CY | 14th Sept 2012 |
| 193.201.151.0/26 | 64 | RIPE NCC | CY | 14th Sept 2012 |
| 193.201.151.128/26 | 64 | RIPE NCC | GB | 1st Feb 2024 |
| 193.201.151.192/26 | 64 | RIPE NCC | DE | 4th Jul 2005 |
| 193.201.151.64/26 | 64 | RIPE NCC | DE | 24th Jan 2024 |
| 193.201.152.0/25 | 128 | RIPE NCC |  RU | 28th Mar 2003 |
| 193.201.152.128/25 | 128 | RIPE NCC |  UA | 27th Nov 2003 |
| 193.201.154.0/25 | 128 | RIPE NCC | GB | 4th Dec 2003 |
| 193.201.154.128/25 | 128 | RIPE NCC |  RO | 11th Apr 2005 |
| 193.201.155.0/26 | 64 | RIPE NCC |  LB | 7th Nov 2025 |
| 193.201.155.128/25 | 128 | RIPE NCC |  IL | 15th Apr 2004 |
| 193.201.155.64/26 | 64 | RIPE NCC |  SA | 31st Dec 2024 |
| 193.201.156.0/25 | 128 | RIPE NCC | RU | 3rd Jun 2004 |
| 193.201.156.128/25 | 128 | RIPE NCC |  SE | 17th May 2004 |
| 193.201.157.0/25 | 128 | RIPE NCC | CY | 14th Sept 2012 |
| 193.201.157.128/26 | 64 | RIPE NCC |  NL | 29th Jan 2025 |
| 193.201.157.192/26 | 64 | RIPE NCC |  FR | 26th Feb 2025 |
| 193.201.160.0/24 | 256 | RIPE NCC | GB | 1st Jul 2002 |
| 193.201.161.0/24 | 256 | RIPE NCC | RO | 2nd Jul 2002 |
| 193.201.165.0/24 | 256 | RIPE NCC |  SI | 4th Jul 2002 |
| 193.201.174.0/24 | 256 | RIPE NCC | GB | 18th Jul 2002 |
| 193.201.196.0/24 | 256 | RIPE NCC | FR | 26th May 2026 |
| 193.201.197.0/24 | 256 | RIPE NCC | GB | 27th May 2026 |
| 193.201.22.0/24 | 256 | RIPE NCC | CH | 19th Jan 2026 |
| 193.201.224.0/22 | 1k | RIPE NCC | UA | 23rd Jul 2002 |
| 193.201.23.0/24 | 256 | RIPE NCC |  IR | 19th Jan 2026 |
| 193.201.28.0/23 | 512 | RIPE NCC |  IT | 4th Jun 2002 |
| 193.201.47.0/24 | 256 | RIPE NCC | NL | 18th Aug 2026 |
| 193.201.56.0/22 | 1k | RIPE NCC | US | 9th May 2018 |
| 193.201.8.0/24 | 256 | RIPE NCC | RU | 16th Sept 2021 |
| 193.201.92.0/22 | 1k | RIPE NCC | GB | 25th Jun 2002 |
| 193.202.1.0/24 | 256 | RIPE NCC | GB | 7th Apr 1993 |
| 193.202.104.0/24 | 256 | RIPE NCC | NL | 21st Jun 1993 |
| 193.202.105.0/24 | 256 | RIPE NCC | GB | 13th Jan 2009 |
| 193.202.114.0/24 | 256 | RIPE NCC |  IE | 18th Nov 2019 |
| 193.202.2.0/23 | 512 | RIPE NCC | GB | 7th Apr 1993 |
| 193.202.224.0/20 | 4.1k | RIPE NCC | GB | 13th Jul 1993 |
| 193.202.24.0/22 | 1k | RIPE NCC | DE | 2nd Aug 1993 |
| 193.202.28.0/23 | 512 | RIPE NCC | DE | 2nd Aug 1993 |
| 193.202.30.0/24 | 256 | RIPE NCC | DE | 2nd Aug 1993 |
| 193.202.4.0/22 | 1k | RIPE NCC | GB | 7th Apr 1993 |
| 193.202.46.0/23 | 512 | RIPE NCC | CH | 12th Oct 1993 |
| 193.202.48.0/21 | 2k | RIPE NCC | CH | 12th Oct 1993 |