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,709 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 95.129.80.0/21 | 2k | RIPE NCC |  NL | 13th Feb 2009 |
| 95.130.132.0/22 | 1k | RIPE NCC |  RU | 6th Mar 2009 |
| 95.130.175.0/24 | 256 | RIPE NCC |  TR | 12th Mar 2009 |
| 95.130.200.0/21 | 2k | RIPE NCC |  CH | 16th Mar 2009 |
| 95.131.0.0/21 | 2k | RIPE NCC | RU | 18th Mar 2009 |
| 95.131.104.0/21 | 2k | RIPE NCC |  GB | 26th Mar 2009 |
| 95.131.120.0/23 | 512 | RIPE NCC |  DE | 27th Mar 2009 |
| 95.131.122.0/23 | 512 | RIPE NCC | DE | 27th Mar 2009 |
| 95.131.124.0/22 | 1k | RIPE NCC | DE | 27th Mar 2009 |
| 95.131.168.0/21 | 2k | RIPE NCC |  ES | 1st Apr 2009 |
| 95.131.201.0/24 | 256 | RIPE NCC |  AU | 27th May 2024 |
| 95.131.204.0/24 | 256 | RIPE NCC | RU | 18th Jun 2024 |
| 95.131.207.0/24 | 256 | RIPE NCC |  IT | 18th Jun 2024 |
| 95.131.64.0/21 | 2k | RIPE NCC | DE | 24th Mar 2009 |
| 95.132.0.0/16 | 65.5k | RIPE NCC |  UA | 23rd Jan 2009 |
| 95.133.0.0/17 | 32.8k | RIPE NCC | UA | 23rd Jan 2009 |
| 95.133.132.0/22 | 1k | RIPE NCC | UA | 23rd Jan 2009 |
| 95.133.144.0/20 | 4.1k | RIPE NCC | UA | 23rd Jan 2009 |
| 95.133.160.0/23 | 512 | RIPE NCC |  IS | 23rd Jan 2009 |
| 95.133.162.0/23 | 512 | RIPE NCC | DE | 23rd Jan 2009 |
| 95.133.168.0/23 | 512 | RIPE NCC | DE | 23rd Jan 2009 |
| 95.133.170.0/23 | 512 | RIPE NCC | UA | 23rd Jan 2009 |
| 95.133.172.0/22 | 1k | RIPE NCC | UA | 23rd Jan 2009 |
| 95.133.176.0/20 | 4.1k | RIPE NCC | UA | 23rd Jan 2009 |
| 95.133.208.0/20 | 4.1k | RIPE NCC | UA | 23rd Jan 2009 |
| 95.133.224.0/22 | 1k | RIPE NCC |  QA | 23rd Jan 2009 |
| 95.140.224.0/20 | 4.1k | RIPE NCC |  US | 2nd Apr 2009 |
| 95.141.244.0/24 | 256 | RIPE NCC | GB | 9th Jan 2024 |
| 95.141.249.0/24 | 256 | RIPE NCC | GB | 9th Jan 2024 |
| 95.141.250.0/24 | 256 | RIPE NCC | DE | 9th Jan 2024 |
| 95.141.255.0/24 | 256 | RIPE NCC |  HU | 9th Jan 2024 |
| 95.142.144.0/22 | 1k | RIPE NCC |  IQ | 21st May 2012 |
| 95.142.150.0/24 | 256 | RIPE NCC |  AZ | 21st May 2012 |
| 95.142.152.0/21 | 2k | RIPE NCC | DE | 21st May 2012 |
| 95.143.100.0/24 | 256 | RIPE NCC | NL | 19th Jan 2026 |
| 95.143.101.0/24 | 256 | RIPE NCC |  PL | 19th Jan 2026 |
| 95.143.102.0/24 | 256 | RIPE NCC |  FR | 20th Jan 2026 |
| 95.143.104.0/24 | 256 | RIPE NCC | IT | 20th Jan 2026 |
| 95.143.105.0/24 | 256 | RIPE NCC | RU | 20th Jan 2026 |
| 95.143.107.0/24 | 256 | RIPE NCC | DE | 20th Jan 2026 |
| 95.143.108.0/24 | 256 | RIPE NCC | RU | 20th Jan 2026 |
| 95.143.109.0/24 | 256 | RIPE NCC |  CZ | 20th Jan 2026 |
| 95.143.110.0/24 | 256 | RIPE NCC | RU | 20th Jan 2026 |
| 95.143.98.0/24 | 256 | RIPE NCC | GB | 19th Jan 2026 |
| 95.143.99.0/24 | 256 | RIPE NCC | GB | 19th Jan 2026 |
| 95.152.128.0/18 | 16.4k | RIPE NCC | NL | 13th Feb 2009 |
| 95.155.64.0/18 | 16.4k | RIPE NCC | PL | 3rd Mar 2009 |
| 95.156.222.0/23 | 512 | RIPE NCC |  IR | 27th Mar 2009 |
| 95.156.233.0/24 | 256 | RIPE NCC | IR | 27th Mar 2009 |
| 95.156.234.0/23 | 512 | RIPE NCC | IR | 27th Mar 2009 |