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 Lithuania
309 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2a13:b640::/29 | 34.4B × /64 | RIPE NCC | 23rd Aug 2023 | |
| 2a13:b740::/29 | 34.4B × /64 | RIPE NCC | 24th Aug 2023 | |
| 2a13:b7c0::/29 | 34.4B × /64 | RIPE NCC | 24th Aug 2023 | |
| 2a13:bb40::/29 | 34.4B × /64 | RIPE NCC | 25th Aug 2023 | |
| 2a13:bd40::/29 | 34.4B × /64 | RIPE NCC | 25th Aug 2023 | |
| 2a13:be40::/29 | 34.4B × /64 | RIPE NCC | 25th Aug 2023 | |
| 2a13:bec0::/29 | 34.4B × /64 | RIPE NCC | 25th Aug 2023 | |
| 2a13:bfc0::/29 | 34.4B × /64 | RIPE NCC | 28th Aug 2023 | |
| 2a13:c340::/29 | 34.4B × /64 | RIPE NCC | 28th Aug 2023 | |
| 2a13:c440::/29 | 34.4B × /64 | RIPE NCC | 28th Aug 2023 | |
| 2a13:c540::/29 | 34.4B × /64 | RIPE NCC | 28th Aug 2023 | |
| 2a13:df40::/29 | 34.4B × /64 | RIPE NCC | 15th Sept 2023 | |
| 2a13:dfc0::/29 | 34.4B × /64 | RIPE NCC | 15th Sept 2023 | |
| 2a13:e040::/29 | 34.4B × /64 | RIPE NCC | 15th Sept 2023 | |
| 2a14:1100::/29 | 34.4B × /64 | RIPE NCC | 3rd Nov 2023 | |
| 2a14:2480::/29 | 34.4B × /64 | RIPE NCC | 11th Dec 2023 | |
| 2a14:2580::/29 | 34.4B × /64 | RIPE NCC | 11th Dec 2023 | |
| 2a14:42c0::/29 | 34.4B × /64 | RIPE NCC | 19th Apr 2024 | |
| 2a14:62c0::/29 | 34.4B × /64 | RIPE NCC | 10th Jun 2024 | |
| 2a14:6a40::/29 | 34.4B × /64 | RIPE NCC | 17th Jun 2024 | |
| 45.138.12.0/22 | 1k | RIPE NCC | 7th Aug 2019 | |
| 45.148.36.0/22 | 1k | RIPE NCC | 2nd Sept 2019 | |
| 46.102.251.0/24 | 256 | RIPE NCC | 25th Jun 2010 | |
| 46.36.200.0/24 | 256 | RIPE NCC | 10th Jan 2024 | |
| 62.233.51.0/24 | 256 | RIPE NCC | 11th Jan 2024 | |
| 83.138.50.0/24 | 256 | RIPE NCC | 12th Aug 2021 | |
| 84.46.200.0/24 | 256 | RIPE NCC | 11th Oct 2004 | |
| 85.136.196.0/22 | 1k | RIPE NCC | 3rd Nov 2004 | |
| 85.137.176.0/22 | 1k | RIPE NCC | 3rd Nov 2004 | |
| 85.137.208.0/22 | 1k | RIPE NCC | 3rd Nov 2004 | |
| 85.137.215.0/24 | 256 | RIPE NCC | 3rd Nov 2004 | |
| 85.8.206.0/24 | 256 | RIPE NCC | 26th Jun 2026 | |
| 86.38.110.0/24 | 256 | RIPE NCC | 19th May 2005 | |
| 86.38.191.0/24 | 256 | RIPE NCC | 19th May 2005 | |
| 86.38.235.0/24 | 256 | RIPE NCC | 19th May 2005 | |
| 89.107.9.0/24 | 256 | RIPE NCC | 19th Aug 2021 | |
| 89.116.153.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.116.177.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.116.184.0/23 | 512 | RIPE NCC | 3rd May 2006 | |
| 89.116.56.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.116.8.0/22 | 1k | RIPE NCC | 3rd May 2006 | |
| 89.116.96.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.11.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.126.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.129.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.137.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.214.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.219.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.251.0/24 | 256 | RIPE NCC | 3rd May 2006 | |
| 89.117.68.0/24 | 256 | RIPE NCC | 3rd May 2006 |