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
25,269 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.86.136.0/22 | 1k | RIPE NCC |  FR | 2nd Feb 2015 |
| 185.86.172.0/22 | 1k | RIPE NCC |  DE | 3rd Feb 2015 |
| 185.86.208.0/23 | 512 | RIPE NCC |  ES | 5th Feb 2015 |
| 185.86.240.0/22 | 1k | RIPE NCC |  RS | 5th Feb 2015 |
| 185.86.68.0/22 | 1k | RIPE NCC |  DK | 30th Jan 2015 |
| 185.87.112.0/22 | 1k | RIPE NCC |  CH | 10th Feb 2015 |
| 185.87.144.0/22 | 1k | RIPE NCC |  FK | 11th Feb 2015 |
| 185.87.200.0/22 | 1k | RIPE NCC |  NL | 12th Feb 2015 |
| 185.87.4.0/22 | 1k | RIPE NCC |  BE | 6th Feb 2015 |
| 185.87.62.0/24 | 256 | RIPE NCC |  KZ | 19th Dec 2019 |
| 185.87.63.0/24 | 256 | RIPE NCC | ES | 19th Dec 2019 |
| 185.87.84.0/22 | 1k | RIPE NCC | ES | 10th Feb 2015 |
| 185.88.11.0/24 | 256 | RIPE NCC |  AE | 6th Jan 2020 |
| 185.88.133.0/24 | 256 | RIPE NCC |  TR | 17th Feb 2015 |
| 185.88.134.0/23 | 512 | RIPE NCC | TR | 17th Feb 2015 |
| 185.88.148.0/22 | 1k | RIPE NCC | NL | 17th Feb 2015 |
| 185.88.172.0/22 | 1k | RIPE NCC | TR | 18th Feb 2015 |
| 185.88.192.0/22 | 1k | RIPE NCC |  GB | 18th Feb 2015 |
| 185.88.216.0/22 | 1k | RIPE NCC | GB | 19th Feb 2015 |
| 185.88.44.0/22 | 1k | RIPE NCC | GB | 16th Feb 2015 |
| 185.88.84.0/22 | 1k | RIPE NCC |  IT | 16th Feb 2015 |
| 185.89.0.0/22 | 1k | RIPE NCC |  NO | 19th Feb 2015 |
| 185.89.100.0/22 | 1k | RIPE NCC |  UA | 24th Feb 2015 |
| 185.89.188.0/22 | 1k | RIPE NCC | CH | 26th Feb 2015 |
| 185.89.204.0/22 | 1k | RIPE NCC |  SE | 27th Feb 2015 |
| 185.9.108.0/22 | 1k | RIPE NCC | DE | 8th Nov 2012 |
| 185.9.136.0/24 | 256 | RIPE NCC | GB | 8th Apr 2024 |
| 185.9.137.0/24 | 256 | RIPE NCC | IT | 8th Apr 2024 |
| 185.9.244.0/22 | 1k | RIPE NCC |  LU | 13th Nov 2012 |
| 185.9.48.0/22 | 1k | RIPE NCC | GB | 6th Nov 2012 |
| 185.9.68.0/22 | 1k | RIPE NCC |  IQ | 7th Nov 2012 |
| 185.9.92.0/22 | 1k | RIPE NCC | GB | 7th Nov 2012 |
| 185.9.96.0/22 | 1k | RIPE NCC | FR | 8th Nov 2012 |
| 185.90.120.0/22 | 1k | RIPE NCC | GB | 5th Mar 2015 |
| 185.90.16.0/22 | 1k | RIPE NCC |  SA | 2nd Mar 2015 |
| 185.90.188.0/22 | 1k | RIPE NCC | IT | 6th Mar 2015 |
| 185.90.24.0/22 | 1k | RIPE NCC | SE | 3rd Mar 2015 |
| 185.90.252.0/22 | 1k | RIPE NCC | ES | 10th Mar 2015 |
| 185.90.76.0/22 | 1k | RIPE NCC |  IE | 4th Mar 2015 |
| 185.91.112.0/22 | 1k | RIPE NCC | GB | 12th Mar 2015 |
| 185.91.124.0/24 | 256 | RIPE NCC | GB | 22nd May 2023 |
| 185.91.144.0/22 | 1k | RIPE NCC |  AT | 12th Mar 2015 |
| 185.91.60.0/22 | 1k | RIPE NCC | IT | 11th Mar 2015 |
| 185.92.112.0/22 | 1k | RIPE NCC |  FI | 18th Mar 2015 |
| 185.92.16.0/22 | 1k | RIPE NCC | NL | 16th Mar 2015 |
| 185.92.176.0/22 | 1k | RIPE NCC |  SI | 19th Mar 2015 |
| 185.92.20.0/22 | 1k | RIPE NCC | FR | 16th Mar 2015 |
| 185.92.80.0/22 | 1k | RIPE NCC | ES | 17th Mar 2015 |
| 185.92.92.0/22 | 1k | RIPE NCC | NL | 18th Mar 2015 |
| 185.93.112.0/22 | 1k | RIPE NCC | ES | 25th Mar 2015 |