Country
—
ASN LANDING PAGE
HORIZON-SCOPE-IQ - Horizon Scope Mobile Telecom WLL
Last updated · Apr 4, 2026
Country
—
Total prefixes
98
IPv4 prefixes
92
IPv6 prefixes
6
HORIZON-SCOPE-IQ - Horizon Scope Mobile Telecom WLL currently shows 98 prefixes and 27 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
HORIZON-SCOPE-IQ - Horizon Scope Mobile Telecom WLL is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS59588
AS59588
—
AS200485
AS200485
—
AS209173
AS209173
—
AS57908
AS57908
—
AS14789
AS14789
—
AS208131
AS208131
—
AS57958
AS57958
—
AS197390
AS197390
—
AS203257
AS203257
—
AS209733
AS209733
—
AS52059
AS52059
—
AS204473
AS204473
—
AS205814
AS205814
—
AS209036
AS209036
—
AS215917
AS215917
—
AS211534
AS211534
—
AS54994
AS54994
—
AS201320
AS201320
—
AS6
AS6
—
AS206190
AS206190
—
AS205889
AS205889
—
AS211908
AS211908
—
AS48407
AS48407
—
| Prefix | Name | Country |
|---|---|---|
| 138.124.156.0/23 | AS203217 | — |
| 138.124.156.0/24 | AS203217 | — |
| 138.124.157.0/24 | AS203217 | — |
| 138.124.158.0/23 | AS203217 | — |
| 138.124.158.0/24 | AS203217 | — |
| 138.124.159.0/24 | AS203217 | — |
| 144.86.228.0/23 | AS203217 | — |
| 144.86.228.0/24 | AS203217 | — |
| 144.86.229.0/24 | AS203217 | — |
| 144.86.230.0/23 | AS203217 | — |
| 144.86.230.0/24 | AS203217 | — |
| 144.86.231.0/24 | AS203217 | — |
| 151.236.174.0/23 | AS203217 | — |
| 154.43.166.0/24 | AS203217 | — |
| 154.43.176.0/23 | AS203217 | — |
| 154.43.176.0/24 | AS203217 | — |
| 154.43.177.0/24 | AS203217 | — |
| 154.43.178.0/23 | AS203217 | — |
| 154.43.178.0/24 | AS203217 | — |
| 154.43.179.0/24 | AS203217 | — |
| 185.112.188.0/23 | AS203217 | — |
| 185.112.188.0/24 | AS203217 | — |
| 185.112.189.0/24 | AS203217 | — |
| 185.112.190.0/23 | AS203217 | — |
| 185.112.190.0/24 | AS203217 | — |
| 185.112.191.0/24 | AS203217 | — |
| 185.138.120.0/23 | AS203217 | — |
| 185.138.120.0/24 | AS203217 | — |
| 185.138.121.0/24 | AS203217 | — |
| 185.138.122.0/23 | AS203217 | — |
| 185.138.122.0/24 | AS203217 | — |
| 185.138.123.0/24 | AS203217 | — |
| 185.194.10.0/23 | AS203217 | — |
| 185.194.10.0/24 | AS203217 | — |
| 185.194.11.0/24 | AS203217 | — |
| 185.194.8.0/23 | AS203217 | — |
| 185.194.9.0/24 | AS203217 | — |
| 185.20.196.0/23 | AS203217 | — |
| 185.20.196.0/24 | AS203217 | — |
| 185.20.197.0/24 | AS203217 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS203217 is an autonomous system number used to identify an independently operated network. The current page associates it with HORIZON-SCOPE-IQ - Horizon Scope Mobile Telecom WLL in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS203217. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS203217, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.