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 in Belgium
303 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2a12:d140::/29 | 34.4B × /64 | RIPE NCC | 22nd Apr 2022 | |
| 2a13:5f00::/29 | 34.4B × /64 | RIPE NCC | 18th Jul 2022 | |
| 2a13:6100::/29 | 34.4B × /64 | RIPE NCC | 18th Jul 2022 | |
| 2a13:8300::/29 | 34.4B × /64 | RIPE NCC | 6th Feb 2023 | |
| 2a14:1380::/32 | 4.3B × /64 | RIPE NCC | 4th Dec 2023 | |
| 2a14:2900::/32 | 4.3B × /64 | RIPE NCC | 7th Nov 2023 | |
| 2a14:480::/29 | 34.4B × /64 | RIPE NCC | 27th Nov 2023 | |
| 2a14:6180::/29 | 34.4B × /64 | RIPE NCC | 4th Jan 2024 | |
| 31.14.50.0/23 | 512 | RIPE NCC | 18th Apr 2011 | |
| 37.123.232.0/21 | 2k | RIPE NCC | 16th Feb 2012 | |
| 37.228.72.0/21 | 2k | RIPE NCC | 10th Apr 2012 | |
| 46.19.7.0/24 | 256 | RIPE NCC | 4th Nov 2010 | |
| 5.183.236.0/22 | 1k | RIPE NCC | 11th Apr 2019 | |
| 5.253.231.0/24 | 256 | RIPE NCC | 11th Feb 2019 | |
| 57.1.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.230.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.233.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.234.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.236.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.238.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.241.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.242.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.254.0.0/15 | 131k | RIPE NCC | 21st Jun 1993 | |
| 57.30.0.0/15 | 131k | RIPE NCC | 21st Jun 1993 | |
| 57.38.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.4.0.0/15 | 131k | RIPE NCC | 21st Jun 1993 | |
| 57.47.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 57.6.0.0/16 | 65.5k | RIPE NCC | 21st Jun 1993 | |
| 78.40.96.0/21 | 2k | RIPE NCC | 13th Jul 2007 | |
| 79.142.176.0/22 | 1k | RIPE NCC | 13th Aug 2018 | |
| 80.91.144.0/20 | 4.1k | RIPE NCC | 14th Jun 2005 | |
| 83.138.63.0/24 | 256 | RIPE NCC | 6th Jan 2020 | |
| 85.8.228.0/24 | 256 | RIPE NCC | 29th Jun 2026 | |
| 85.88.32.0/19 | 8.2k | RIPE NCC | 22nd Oct 2004 | |
| 86.107.127.0/24 | 256 | RIPE NCC | 18th Apr 2005 | |
| 87.238.227.0/24 | 256 | RIPE NCC | 24th Jan 2006 | |
| 88.218.124.0/22 | 1k | RIPE NCC | 17th Dec 2018 | |
| 89.107.144.0/21 | 2k | RIPE NCC | 3rd May 2006 | |
| 89.207.154.0/24 | 256 | RIPE NCC | 18th Sept 2023 | |
| 91.199.15.0/24 | 256 | RIPE NCC | 9th Nov 2007 | |
| 91.202.32.0/22 | 1k | RIPE NCC | 19th Apr 2018 | |
| 91.206.75.0/24 | 256 | RIPE NCC | 28th Apr 2026 | |
| 91.208.12.0/24 | 256 | RIPE NCC | 1st Jul 2008 | |
| 91.208.220.0/24 | 256 | RIPE NCC | 29th Sept 2008 | |
| 91.220.136.0/24 | 256 | RIPE NCC | 11th Nov 2010 | |
| 91.220.154.0/24 | 256 | RIPE NCC | 17th Nov 2010 | |
| 91.220.191.0/24 | 256 | RIPE NCC | 30th Nov 2010 | |
| 91.227.209.0/24 | 256 | RIPE NCC | 18th May 2011 | |
| 91.230.64.0/24 | 256 | RIPE NCC | 6th Jul 2011 | |
| 91.234.230.0/23 | 512 | RIPE NCC | 30th Jan 2012 |