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,783 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 91.194.148.0/24 | 256 | RIPE NCC |  AT | 22nd Sept 2021 |
| 91.194.158.0/23 | 512 | RIPE NCC |  GB | 26th Jun 2007 |
| 91.194.164.0/23 | 512 | RIPE NCC |  RU | 27th Jun 2007 |
| 91.194.186.0/23 | 512 | RIPE NCC |  SE | 5th Jul 2007 |
| 91.194.206.0/23 | 512 | RIPE NCC | RU | 10th Jul 2007 |
| 91.194.218.0/23 | 512 | RIPE NCC |  NL | 16th Jul 2007 |
| 91.194.32.0/23 | 512 | RIPE NCC |  US | 24th May 2007 |
| 91.194.4.0/23 | 512 | RIPE NCC |  ES | 14th May 2007 |
| 91.194.40.0/23 | 512 | RIPE NCC |  UA | 14th Sept 2009 |
| 91.194.42.0/23 | 512 | RIPE NCC | GB | 25th May 2007 |
| 91.194.55.0/24 | 256 | RIPE NCC |  TR | 18th Apr 2018 |
| 91.194.6.0/24 | 256 | RIPE NCC |  IR | 28th Jan 2026 |
| 91.194.64.0/23 | 512 | RIPE NCC | RU | 5th Jun 2007 |
| 91.194.94.0/23 | 512 | RIPE NCC |  DK | 16th Apr 2008 |
| 91.195.104.0/23 | 512 | RIPE NCC |  DE | 7th Sept 2007 |
| 91.195.110.0/24 | 256 | RIPE NCC |  AM | 10th Sept 2007 |
| 91.195.111.0/24 | 256 | RIPE NCC | AM | 10th Sept 2007 |
| 91.195.148.0/23 | 512 | RIPE NCC | RU | 21st Sept 2007 |
| 91.195.160.0/23 | 512 | RIPE NCC | NL | 25th Sept 2007 |
| 91.195.166.0/23 | 512 | RIPE NCC | GB | 26th Sept 2007 |
| 91.195.174.0/23 | 512 | RIPE NCC |  IE | 3rd Oct 2019 |
| 91.195.182.0/23 | 512 | RIPE NCC | GB | 2nd Oct 2007 |
| 91.195.186.0/23 | 512 | RIPE NCC | GB | 3rd Oct 2007 |
| 91.195.192.0/23 | 512 | RIPE NCC | GB | 4th Oct 2007 |
| 91.195.194.0/24 | 256 | RIPE NCC |  RO | 8th Oct 2007 |
| 91.195.208.0/23 | 512 | RIPE NCC | IE | 3rd Oct 2019 |
| 91.195.236.0/23 | 512 | RIPE NCC | NL | 23rd Oct 2007 |
| 91.195.242.0/23 | 512 | RIPE NCC | DE | 25th Oct 2007 |
| 91.195.250.0/23 | 512 | RIPE NCC |  PL | 29th Oct 2007 |
| 91.195.32.0/23 | 512 | RIPE NCC | SE | 14th Aug 2007 |
| 91.195.37.0/24 | 256 | RIPE NCC | IR | 30th Jan 2024 |
| 91.195.42.0/23 | 512 | RIPE NCC | PL | 21st Aug 2007 |
| 91.195.48.0/23 | 512 | RIPE NCC | DE | 23rd Aug 2007 |
| 91.195.6.0/23 | 512 | RIPE NCC | RO | 6th Aug 2007 |
| 91.195.82.0/23 | 512 | RIPE NCC | GB | 3rd Sept 2007 |
| 91.196.116.0/22 | 1k | RIPE NCC | GB | 11th Jun 2007 |
| 91.196.128.0/22 | 1k | RIPE NCC | ES | 12th Jun 2007 |
| 91.196.16.0/22 | 1k | RIPE NCC |  IT | 18th Apr 2018 |
| 91.196.60.0/22 | 1k | RIPE NCC | RU | 14th Oct 2009 |
| 91.196.88.0/22 | 1k | RIPE NCC | UA | 1st Jun 2007 |
| 91.197.12.0/22 | 1k | RIPE NCC |  CY | 12th Jul 2007 |
| 91.197.183.0/24 | 256 | RIPE NCC | RU | 10th Sept 2007 |
| 91.197.236.0/22 | 1k | RIPE NCC | RU | 18th Sept 2007 |
| 91.197.244.0/23 | 512 | RIPE NCC | RO | 19th Sept 2007 |
| 91.197.246.0/24 | 256 | RIPE NCC | RO | 19th Sept 2007 |
| 91.197.36.0/22 | 1k | RIPE NCC | RO | 18th Apr 2018 |
| 91.197.44.0/23 | 512 | RIPE NCC |  CZ | 23rd May 2012 |
| 91.198.111.0/24 | 256 | RIPE NCC | PL | 13th Sept 2007 |
| 91.198.124.0/24 | 256 | RIPE NCC | TR | 18th Sept 2007 |
| 91.198.127.0/24 | 256 | RIPE NCC | RU | 31st Mar 2010 |