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,818 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 83.143.88.0/21 | 2k | RIPE NCC |  FI | 24th May 2005 |
| 83.143.96.0/21 | 2k | RIPE NCC |  PL | 30th May 2005 |
| 83.150.128.0/18 | 16.4k | RIPE NCC |  SE | 22nd Mar 2004 |
| 83.151.208.0/20 | 4.1k | ARIN |  US | 18th Jun 2024 |
| 83.151.48.0/20 | 4.1k | RIPE NCC |  DE | 28th May 2004 |
| 83.151.64.0/18 | 16.4k | RIPE NCC |  GB | 24th Mar 2004 |
| 83.171.192.0/22 | 1k | RIPE NCC |  LB | 15th Nov 2018 |
| 83.172.162.0/23 | 512 | RIPE NCC | DE | 3rd May 2004 |
| 83.172.164.0/23 | 512 | RIPE NCC | DE | 3rd May 2004 |
| 83.175.0.0/18 | 16.4k | RIPE NCC |  IT | 27th May 2004 |
| 83.175.136.0/23 | 512 | RIPE NCC | PL | 16th Feb 2006 |
| 83.175.161.0/24 | 256 | RIPE NCC | PL | 10th Jun 2004 |
| 83.175.163.0/24 | 256 | RIPE NCC | PL | 10th Jun 2004 |
| 83.175.164.0/24 | 256 | RIPE NCC | PL | 10th Jun 2004 |
| 83.216.64.0/19 | 8.2k | RIPE NCC | GB | 25th Feb 2004 |
| 83.217.32.0/19 | 8.2k | RIPE NCC |  RU | 4th Mar 2004 |
| 83.219.100.0/22 | 1k | RIPE NCC | DE | 20th Jun 2018 |
| 83.220.16.0/21 | 2k | RIPE NCC | IT | 29th Mar 2004 |
| 83.220.192.0/19 | 8.2k | RIPE NCC |  IE | 7th Apr 2004 |
| 83.220.24.0/23 | 512 | RIPE NCC | IT | 29th Mar 2004 |
| 83.220.26.0/24 | 256 | RIPE NCC | IT | 29th Mar 2004 |
| 83.220.27.0/24 | 256 | RIPE NCC | IT | 29th Mar 2004 |
| 83.220.30.0/23 | 512 | RIPE NCC | IT | 29th Mar 2004 |
| 83.221.162.0/24 | 256 | RIPE NCC |  UZ | 15th Apr 2004 |
| 83.221.165.0/24 | 256 | RIPE NCC | UZ | 15th Apr 2004 |
| 83.221.166.0/23 | 512 | RIPE NCC | UZ | 15th Apr 2004 |
| 83.221.182.0/24 | 256 | RIPE NCC | UZ | 15th Apr 2004 |
| 83.221.183.0/24 | 256 | RIPE NCC | UZ | 15th Apr 2004 |
| 83.229.16.0/24 | 256 | RIPE NCC |  RS | 13th May 2004 |
| 83.229.31.0/24 | 256 | RIPE NCC |  IL | 13th May 2004 |
| 83.241.0.0/17 | 32.8k | RIPE NCC |  LV | 19th Mar 2004 |
| 83.242.101.0/24 | 256 | RIPE NCC |  DK | 6th Jan 2025 |
| 83.242.103.0/24 | 256 | RIPE NCC | RU | 12th Mar 2012 |
| 83.242.106.0/24 | 256 | RIPE NCC | RU | 12th Mar 2012 |
| 83.68.0.0/19 | 8.2k | RIPE NCC |  NL | 29th Apr 2004 |
| 83.94.64.0/19 | 8.2k | RIPE NCC | GB | 1st Dec 2003 |
| 83.97.40.0/21 | 2k | RIPE NCC | DE | 9th Feb 2004 |
| 83.97.48.0/21 | 2k | RIPE NCC | DE | 11th Feb 2004 |
| 83.98.160.0/22 | 1k | RIPE NCC | NL | 14th Jan 2004 |
| 83.98.165.0/24 | 256 | RIPE NCC | NL | 14th Jan 2004 |
| 84.18.160.0/19 | 8.2k | RIPE NCC | GB | 12th Aug 2004 |
| 84.19.104.0/21 | 2k | RIPE NCC | GB | 25th Aug 2004 |
| 84.201.208.0/20 | 4.1k | RIPE NCC | US | 5th Jan 2005 |
| 84.201.224.0/20 | 4.1k | RIPE NCC |  BG | 14th Jan 2005 |
| 84.205.161.0/24 | 256 | RIPE NCC | GB | 3rd Feb 2005 |
| 84.205.167.0/24 | 256 | RIPE NCC | PL | 3rd Feb 2005 |
| 84.205.180.0/23 | 512 | RIPE NCC | PL | 3rd Feb 2005 |
| 84.234.0.0/20 | 4.1k | RIPE NCC | PL | 6th Jul 2004 |
| 84.234.117.0/24 | 256 | RIPE NCC | PL | 24th Nov 2004 |
| 84.234.32.0/20 | 4.1k | RIPE NCC | PL | 16th Aug 2004 |