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
24,896 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.98.162.0/24 | 256 | RIPE NCC |  GB | 17th Jan 2025 |
| 185.98.172.0/22 | 1k | RIPE NCC |  IE | 30th Apr 2015 |
| 185.98.228.0/22 | 1k | RIPE NCC |  FI | 4th May 2015 |
| 185.98.24.0/24 | 256 | RIPE NCC |  CH | 23rd Jan 2026 |
| 185.98.27.0/24 | 256 | RIPE NCC | GB | 23rd Jan 2026 |
| 185.98.36.0/22 | 1k | RIPE NCC |  DK | 28th Apr 2015 |
| 185.98.44.0/22 | 1k | RIPE NCC | GB | 28th Apr 2015 |
| 185.98.86.0/24 | 256 | RIPE NCC |  RU | 29th Apr 2015 |
| 185.98.87.0/24 | 256 | RIPE NCC | RU | 29th Apr 2015 |
| 185.99.244.0/24 | 256 | RIPE NCC |  GR | 15th Sept 2026 |
| 185.99.245.0/24 | 256 | RIPE NCC |  UZ | 22nd Sept 2026 |
| 185.99.246.0/24 | 256 | RIPE NCC |  IR | 24th Sept 2026 |
| 185.99.247.0/24 | 256 | RIPE NCC | IR | 24th Sept 2026 |
| 185.99.60.0/22 | 1k | RIPE NCC |  ES | 6th May 2015 |
| 185.99.72.0/22 | 1k | RIPE NCC |  AT | 7th May 2015 |
| 185.99.84.0/22 | 1k | RIPE NCC | GB | 7th May 2015 |
| 186.242.208.0/20 | 4.1k | RIPE NCC |  LT | 13th Mar 2025 |
| 186.247.0.0/20 | 4.1k | RIPE NCC |  PA | 13th Mar 2025 |
| 186.247.208.0/20 | 4.1k | RIPE NCC | PA | 13th Mar 2025 |
| 187.4.208.0/20 | 4.1k | RIPE NCC | LT | 13th Mar 2025 |
| 187.41.0.0/18 | 16.4k | RIPE NCC | GB | 20th Feb 2025 |
| 187.41.80.0/20 | 4.1k | RIPE NCC | LT | 13th Mar 2025 |
| 187.79.160.0/19 | 8.2k | RIPE NCC | GB | 13th Mar 2025 |
| 188.116.12.0/22 | 1k | RIPE NCC |  DE | 29th May 2009 |
| 188.116.18.0/23 | 512 | RIPE NCC | AT | 29th May 2009 |
| 188.116.48.0/23 | 512 | RIPE NCC | AT | 29th May 2009 |
| 188.116.56.0/23 | 512 | RIPE NCC |  IT | 29th May 2009 |
| 188.119.153.0/24 | 256 | RIPE NCC |  MC | 6th Jul 2009 |
| 188.119.88.0/22 | 1k | RIPE NCC |  RO | 23rd Nov 2018 |
| 188.120.124.0/24 | 256 | RIPE NCC |  RS | 27th Apr 2009 |
| 188.122.160.0/19 | 8.2k | RIPE NCC | RU | 4th Jun 2009 |
| 188.123.120.0/21 | 2k | RIPE NCC |  SK | 11th Jun 2009 |
| 188.125.165.0/24 | 256 | RIPE NCC |  TR | 14th Jul 2009 |
| 188.125.166.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.125.167.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.125.174.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.125.175.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.126.224.0/19 | 8.2k | RIPE NCC |  SE | 24th Jul 2009 |
| 188.132.146.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.132.147.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.132.156.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.132.168.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.132.186.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.132.200.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.138.12.0/22 | 1k | RIPE NCC | DE | 8th May 2009 |
| 188.138.20.0/22 | 1k | RIPE NCC | DE | 8th May 2009 |
| 188.138.48.0/21 | 2k | RIPE NCC | DE | 8th May 2009 |
| 188.139.0.0/17 | 32.8k | RIPE NCC |  SA | 20th May 2009 |
| 188.144.0.0/15 | 131k | RIPE NCC | DE | 13th Mar 2009 |
| 188.190.112.0/24 | 256 | RIPE NCC |  NL | 17th Oct 2018 |