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
84,960 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 109.123.224.0/23 | 512 | RIPE NCC |  DE | 20th Oct 2009 |
| 109.160.104.0/21 | 2k | RIPE NCC |  BG | 27th Aug 2009 |
| 109.172.16.0/21 | 2k | RIPE NCC |  RU | 18th Nov 2009 |
| 109.172.44.0/23 | 512 | RIPE NCC | RU | 18th Nov 2009 |
| 109.175.207.0/24 | 256 | RIPE NCC |  GB | 17th May 2010 |
| 109.175.210.0/24 | 256 | RIPE NCC |  AD | 17th May 2010 |
| 109.175.212.0/24 | 256 | RIPE NCC | GB | 17th May 2010 |
| 109.175.218.0/24 | 256 | RIPE NCC |  TR | 17th May 2010 |
| 109.175.222.0/24 | 256 | RIPE NCC | TR | 17th May 2010 |
| 109.175.223.0/24 | 256 | RIPE NCC | GB | 17th May 2010 |
| 109.175.225.0/24 | 256 | RIPE NCC |  KZ | 17th May 2010 |
| 109.175.241.0/24 | 256 | RIPE NCC | TR | 17th May 2010 |
| 109.175.249.0/24 | 256 | RIPE NCC |  AE | 17th May 2010 |
| 109.175.250.0/23 | 512 | RIPE NCC | GB | 17th May 2010 |
| 109.175.254.0/24 | 256 | RIPE NCC | AE | 17th May 2010 |
| 109.196.168.0/22 | 1k | RIPE NCC |  RO | 29th Aug 2018 |
| 109.197.0.0/21 | 2k | RIPE NCC |  SE | 1st Feb 2010 |
| 109.197.32.0/24 | 256 | RIPE NCC |  PL | 8th Feb 2010 |
| 109.205.144.0/21 | 2k | RIPE NCC | RU | 12th Feb 2010 |
| 109.205.246.0/24 | 256 | RIPE NCC | SE | 18th Feb 2010 |
| 109.206.236.0/24 | 256 | RIPE NCC | BG | 12th Oct 2018 |
| 109.207.105.0/24 | 256 | RIPE NCC | PL | 4th Feb 2010 |
| 109.207.106.0/24 | 256 | RIPE NCC | PL | 4th Feb 2010 |
| 109.207.107.0/24 | 256 | RIPE NCC | PL | 4th Feb 2010 |
| 109.207.108.0/24 | 256 | RIPE NCC | PL | 4th Feb 2010 |
| 109.207.110.0/24 | 256 | RIPE NCC | PL | 4th Feb 2010 |
| 109.207.111.0/24 | 256 | RIPE NCC | PL | 4th Feb 2010 |
| 109.207.167.0/24 | 256 | RIPE NCC | RU | 22nd Feb 2010 |
| 109.207.248.0/22 | 1k | RIPE NCC |  UZ | 15th Mar 2010 |
| 109.230.192.0/23 | 512 | RIPE NCC |  IR | 24th Feb 2010 |
| 109.230.210.0/24 | 256 | RIPE NCC |  AT | 24th Feb 2010 |
| 109.230.222.0/24 | 256 | RIPE NCC |  ES | 24th Feb 2010 |
| 109.230.246.0/24 | 256 | RIPE NCC | IR | 24th Feb 2010 |
| 109.230.247.0/24 | 256 | RIPE NCC | IR | 24th Feb 2010 |
| 109.230.251.0/24 | 256 | RIPE NCC | IR | 24th Feb 2010 |
| 109.232.111.0/24 | 256 | RIPE NCC | RU | 2nd Dec 2009 |
| 109.232.164.0/22 | 1k | RIPE NCC |  NL | 29th Jun 2018 |
| 109.232.241.0/24 | 256 | RIPE NCC | PL | 9th Dec 2009 |
| 109.232.244.0/23 | 512 | RIPE NCC | PL | 9th Dec 2009 |
| 109.232.246.0/24 | 256 | RIPE NCC | PL | 9th Dec 2009 |
| 109.232.247.0/24 | 256 | RIPE NCC | PL | 9th Dec 2009 |
| 109.233.32.0/21 | 2k | ARIN |  US | 13th Dec 2022 |
| 109.234.74.0/24 | 256 | RIPE NCC |  LT | 26th Aug 2021 |
| 109.234.77.0/24 | 256 | RIPE NCC |  CH | 26th Aug 2021 |
| 109.236.160.0/24 | 256 | RIPE NCC | GB | 17th Dec 2009 |
| 109.237.48.0/21 | 2k | RIPE NCC | CH | 13th Jan 2009 |
| 109.68.176.0/21 | 2k | RIPE NCC |  NO | 16th Sept 2009 |
| 109.68.196.0/22 | 1k | RIPE NCC | GB | 17th Sept 2009 |
| 109.68.216.0/24 | 256 | RIPE NCC | TR | 9th Jul 2026 |
| 109.68.217.0/24 | 256 | RIPE NCC | IR | 9th Jul 2026 |