AS203217
Horizon Scope Mobile Telecom Wll — horizonscope.com
Summary
Country |
![]() |
Organization | Horizon Scope Mobile Telecom Wll |
Domain | horizonscope.com |
Number of IPv4 | 12,800 |
Number of IPv6 | 6.3383× 1029 |
AS Type | ISP |
Registry | RIPE NCC |
Allocated | March 07, 2016 (about 9 years ago) |
Updated | March 26, 2025 (about 25 days ago) |
IP Ranges
AS203217 announces 50 IPv4 ranges and 6 IPv6 ranges.
That's a total of 12,800 IPv4 addresses and 6.3383× 1029 IPv6 addresses.
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
38.3.232.0/24 |
![]() |
256 | ARIN | ALLOCATION |
38.3.233.0/24 |
![]() |
256 | ARIN | ALLOCATION |
38.3.234.0/24 |
![]() |
256 | ARIN | ALLOCATION |
38.3.235.0/24 |
![]() |
256 | ARIN | ALLOCATION |
38.3.236.0/24 |
![]() |
256 | ARIN | ALLOCATION |
38.3.237.0/24 |
![]() |
256 | ARIN | ALLOCATION |
38.3.238.0/24 |
![]() |
256 | ARIN | ALLOCATION |
38.3.239.0/24 |
![]() |
256 | ARIN | ALLOCATION |
45.8.72.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
45.8.73.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
81.161.228.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
93.180.216.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
93.180.217.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
93.180.218.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
93.180.219.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
93.180.220.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
93.180.221.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
93.180.223.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
138.124.156.0/24 |
![]() |
256 | RIPE NCC | LEGACY |
138.124.157.0/24 |
![]() |
256 | RIPE NCC | LEGACY |
138.124.158.0/24 |
![]() |
256 | RIPE NCC | LEGACY |
138.124.159.0/24 |
![]() |
256 | RIPE NCC | LEGACY |
144.86.228.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
144.86.229.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
144.86.230.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
144.86.231.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.20.196.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.20.197.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.20.198.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.20.199.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.65.252.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
185.112.188.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.112.189.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.112.190.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.112.191.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.138.120.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.138.121.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.138.122.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.138.123.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.194.9.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.194.10.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.254.13.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
185.254.14.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
195.133.220.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
195.133.221.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
195.133.222.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
195.133.223.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
199.74.189.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
199.74.191.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
204.157.179.0/24 |
![]() |
256 | ARIN | REASSIGNMENT |
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
2a0b:1880::/29 |
![]() |
6.3383× 1029 | RIPE NCC | ASSIGNED |
2a0b:1880::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ASSIGNED |
2a0b:1880:1::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
2a0b:1880:2::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
2a0b:1880:3::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
2a0b:1880:4::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
Peers
AS203217 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
AS203217 connects to the global Internet via at least 3 upstream providers. In this setup, AS203217 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS203217 serves as a transit provider the following ASes, delivering the BGP routes needed for global connectivity. This downstream relationship underscores AS203217's role in extending Internet access beyond its own infrastructure.