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 Saudi Arabia
161 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2a0a:18c0::/29 | 34.4B × /64 | RIPE NCC | 22nd Feb 2017 | |
| 2a0a:8c00::/29 | 34.4B × /64 | RIPE NCC | 18th Aug 2016 | |
| 2a0a:9400::/29 | 34.4B × /64 | RIPE NCC | 18th Aug 2016 | |
| 2a0a:9c00::/29 | 34.4B × /64 | RIPE NCC | 18th Aug 2016 | |
| 2a0a:c480::/29 | 34.4B × /64 | RIPE NCC | 8th Dec 2016 | |
| 2a0b:1f40::/29 | 34.4B × /64 | RIPE NCC | 8th Jun 2017 | |
| 2a0b:c0::/29 | 34.4B × /64 | RIPE NCC | 23rd May 2017 | |
| 2a0c:8740::/29 | 34.4B × /64 | RIPE NCC | 10th Aug 2026 | |
| 2a0c:9100::/29 | 34.4B × /64 | RIPE NCC | 14th Nov 2017 | |
| 2a0d:e880::/29 | 34.4B × /64 | RIPE NCC | 8th Mar 2018 | |
| 2a0e:3100::/32 | 4.3B × /64 | RIPE NCC | 19th Sept 2025 | |
| 2a0e:a5c0::/29 | 34.4B × /64 | RIPE NCC | 31st Jan 2024 | |
| 2a0f:6ec0::/29 | 34.4B × /64 | RIPE NCC | 10th Oct 2022 | |
| 2a10:1600::/29 | 34.4B × /64 | RIPE NCC | 31st Jan 2020 | |
| 2a10:1700::/29 | 34.4B × /64 | RIPE NCC | 6th Feb 2020 | |
| 2a10:800::/29 | 34.4B × /64 | RIPE NCC | 28th Jan 2020 | |
| 2a12:f940::/29 | 34.4B × /64 | RIPE NCC | 19th May 2022 | |
| 2a13:a7c0::/29 | 34.4B × /64 | RIPE NCC | 10th Aug 2023 | |
| 2a13:cbc0::/29 | 34.4B × /64 | RIPE NCC | 1st Sept 2023 | |
| 2a13:f880::/29 | 34.4B × /64 | RIPE NCC | 11th Apr 2023 | |
| 2a14:3640::/29 | 34.4B × /64 | RIPE NCC | 9th Apr 2024 | |
| 2a14:65c0::/29 | 34.4B × /64 | RIPE NCC | 12th Jun 2024 | |
| 2a14:940::/29 | 34.4B × /64 | RIPE NCC | 20th Feb 2024 | |
| 2a14:de80::/29 | 34.4B × /64 | RIPE NCC | 1st Apr 2025 | |
| 2a14:f800::/29 | 34.4B × /64 | RIPE NCC | 2nd Dec 2024 | |
| 37.186.28.0/23 | 512 | RIPE NCC | 20th Mar 2012 | |
| 37.186.30.0/24 | 256 | RIPE NCC | 20th Mar 2012 | |
| 37.186.31.0/24 | 256 | RIPE NCC | 20th Mar 2012 | |
| 45.135.112.0/22 | 1k | RIPE NCC | 30th Jul 2019 | |
| 45.65.72.0/22 | 1k | RIPE NCC | 12th Nov 2018 | |
| 66.9.112.0/20 | 4.1k | RIPE NCC | 12th Sept 2000 | |
| 77.236.120.0/21 | 2k | RIPE NCC | 29th Jan 2007 | |
| 78.40.16.0/21 | 2k | RIPE NCC | 9th Jul 2007 | |
| 80.74.80.0/20 | 4.1k | RIPE NCC | 11th Feb 2005 | |
| 80.79.14.0/24 | 256 | RIPE NCC | 11th Jan 2024 | |
| 81.22.112.0/20 | 4.1k | RIPE NCC | 23rd Jan 2006 | |
| 83.101.160.0/22 | 1k | RIPE NCC | 24th Feb 2004 | |
| 83.101.168.0/21 | 2k | RIPE NCC | 24th Feb 2004 | |
| 83.101.176.0/20 | 4.1k | RIPE NCC | 24th Feb 2004 | |
| 83.101.192.0/18 | 16.4k | RIPE NCC | 24th Feb 2004 | |
| 85.237.128.0/19 | 8.2k | RIPE NCC | 25th May 2005 | |
| 85.8.235.0/24 | 256 | RIPE NCC | 30th Jun 2026 | |
| 85.8.240.0/24 | 256 | RIPE NCC | 17th Jul 2026 | |
| 87.120.168.0/21 | 2k | RIPE NCC | 12th Jul 2005 | |
| 87.121.176.0/20 | 4.1k | RIPE NCC | 12th Jul 2005 | |
| 87.121.240.0/21 | 2k | RIPE NCC | 12th Jul 2005 | |
| 9.162.0.0/16 | 65.5k | RIPE NCC | 16th Dec 1988 | |
| 9.212.0.0/16 | 65.5k | RIPE NCC | 16th Dec 1988 | |
| 9.250.0.0/15 | 131k | RIPE NCC | 16th Dec 1988 | |
| 91.102.16.0/21 | 2k | RIPE NCC | 10th Oct 2006 |