AS212128
LLC HORIZON — horizon-telecom.ru
Summary
Country |
![]() |
Organization | LLC HORIZON |
Domain | horizon-telecom.ru |
Number of IPv4 | 4,096 |
Number of IPv6 | 3.0107× 1030 |
AS Type | Hosting |
Registry | RIPE NCC |
Allocated | December 18, 2020 (about 4 years ago) |
Updated | December 18, 2024 (about 4 months ago) |
IP Ranges
AS212128 announces 8 IPv4 ranges and 40 IPv6 ranges.
That's a total of 4,096 IPv4 addresses and 3.0107× 1030 IPv6 addresses.
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
46.161.4.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
81.19.138.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.19.219.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.195.132.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
91.220.157.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
147.45.128.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
176.103.83.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
194.165.2.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
2a09:54c6:a100::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-LIR |
2a09:6906::/32 |
![]() |
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
2a0d:95c3::/32 |
![]() |
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
2a0e:5904::/32 |
![]() |
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
2a0f:85c1:88b::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ASSIGNED |
2a10:cbc0::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a10:cbc1::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a10:cbc2::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a10:cbc3::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a10:cbc4::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a10:cbc5::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a10:cbc6::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a10:cbc7::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e380::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e381::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e382::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e383::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e384::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e385::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e386::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a11:e387::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:1240::/32 |
![]() |
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
2a12:1801::/32 |
![]() |
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
2a12:3b47::/32 |
![]() |
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
2a12:70c0::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:70c1::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:70c2::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:70c3::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:70c4::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:70c5::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:70c6::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a12:70c7::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e00::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e01::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e02::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e03::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e04::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e05::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e06::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
2a13:7e07::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-LIR |
Peers
AS212128 does not have any direct peering agreements. Instead, its global connectivity is achieved through transit providers. While this setup ensures comprehensive reach, future peering could reduce latency and optimize route efficiency.
Upstreams
AS212128 connects to the global Internet via at least 1 upstream provider. In this setup, AS212128 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS212128 currently has no downstream networks, meaning it does not serve as a transit provider to customer networks.