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,318 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 212.40.161.0/24 | 256 | RIPE NCC |  DE | 19th Mar 1999 |
| 212.40.162.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.164.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.166.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.167.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.169.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.170.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.172.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.174.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.177.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.178.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.180.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.184.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.187.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.188.0/22 | 1k | RIPE NCC | DE | 19th Mar 1999 |
| 212.43.160.0/19 | 8.2k | RIPE NCC |  GB | 15th Apr 1999 |
| 212.46.134.0/23 | 512 | RIPE NCC | GB | 12th May 1998 |
| 212.46.136.0/23 | 512 | RIPE NCC | GB | 12th May 1998 |
| 212.46.146.0/23 | 512 | RIPE NCC | GB | 12th May 1998 |
| 212.46.150.0/23 | 512 | RIPE NCC | GB | 12th May 1998 |
| 212.46.152.0/22 | 1k | RIPE NCC | GB | 12th May 1998 |
| 212.46.156.0/23 | 512 | RIPE NCC | GB | 12th May 1998 |
| 212.46.160.0/21 | 2k | RIPE NCC |  IT | 21st Dec 2007 |
| 212.46.48.0/24 | 256 | RIPE NCC |  UA | 28th Feb 2022 |
| 212.47.32.0/24 | 256 | RIPE NCC |  RU | 20th Jan 2026 |
| 212.47.34.0/24 | 256 | RIPE NCC | GB | 20th Jan 2026 |
| 212.47.37.0/24 | 256 | RIPE NCC |  TR | 20th Jan 2026 |
| 212.47.38.0/24 | 256 | RIPE NCC | DE | 20th Jan 2026 |
| 212.47.41.0/24 | 256 | RIPE NCC | TR | 20th Jan 2026 |
| 212.47.45.0/24 | 256 | RIPE NCC |  BA | 20th Jan 2026 |
| 212.47.46.0/24 | 256 | RIPE NCC | TR | 20th Jan 2026 |
| 212.47.48.0/24 | 256 | RIPE NCC |  NL | 16th Feb 2026 |
| 212.47.49.0/24 | 256 | RIPE NCC |  SE | 17th Feb 2026 |
| 212.47.51.0/24 | 256 | RIPE NCC | TR | 18th Feb 2026 |
| 212.47.52.0/24 | 256 | RIPE NCC | GB | 16th Mar 2026 |
| 212.47.53.0/24 | 256 | RIPE NCC |  CH | 16th Mar 2026 |
| 212.47.57.0/24 | 256 | RIPE NCC |  IM | 22nd Jun 2026 |
| 212.47.60.0/24 | 256 | RIPE NCC |  RO | 22nd Jun 2026 |
| 212.47.61.0/24 | 256 | RIPE NCC |  IQ | 22nd Jun 2026 |
| 212.47.62.0/24 | 256 | RIPE NCC |  US | 23rd Jun 2026 |
| 212.47.63.0/24 | 256 | RIPE NCC | DE | 23rd Jun 2026 |
| 212.47.88.0/21 | 2k | RIPE NCC |  BG | 29th Jul 1998 |
| 212.48.160.0/22 | 1k | RIPE NCC | IT | 18th Mar 1999 |
| 212.49.32.0/19 | 8.2k | RIPE NCC |  PL | 14th Jan 2009 |
| 212.5.40.0/21 | 2k | RIPE NCC | BG | 2nd Sept 2008 |
| 212.5.52.0/23 | 512 | RIPE NCC | BG | 2nd Sept 2008 |
| 212.5.54.0/24 | 256 | RIPE NCC | BG | 2nd Sept 2008 |
| 212.52.1.0/24 | 256 | RIPE NCC |  LV | 5th Nov 2021 |
| 212.52.14.0/24 | 256 | RIPE NCC |  GE | 5th Nov 2021 |
| 212.52.19.0/24 | 256 | RIPE NCC | PL | 5th Nov 2021 |