Country
—
ASN LANDING PAGE
VODAFONEQATAR - Vodafone Qatar P.Q.S.C
Last updated · Apr 4, 2026
Country
—
Total prefixes
99
IPv4 prefixes
67
IPv6 prefixes
32
VODAFONEQATAR - Vodafone Qatar P.Q.S.C currently shows 99 prefixes and 45 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.
VODAFONEQATAR - Vodafone Qatar P.Q.S.C 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.
AS8966
AS8966
—
AS39386
AS39386
—
AS200612
AS200612
—
AS174
AS174
—
AS5511
AS5511
—
AS6939
AS6939
—
AS8781
AS8781
—
AS35280
AS35280
—
AS49544
AS49544
—
AS57187
AS57187
—
AS36236
AS36236
—
AS8529
AS8529
—
AS23764
AS23764
—
AS45489
AS45489
—
AS211559
AS211559
—
AS14593
AS14593
—
AS15412
AS15412
—
AS17557
AS17557
—
AS28821
AS28821
—
AS60185
AS60185
—
AS14789
AS14789
—
AS29384
AS29384
—
AS47901
AS47901
—
AS54253
AS54253
—
AS204806
AS204806
—
AS208542
AS208542
—
AS208944
AS208944
—
AS215624
AS215624
—
AS400696
AS400696
—
| Prefix | Name | Country |
|---|---|---|
| 103.17.0.0/22 | AS48728 | — |
| 103.17.3.0/24 | AS48728 | — |
| 103.199.88.0/22 | AS48728 | — |
| 103.199.88.0/24 | AS48728 | — |
| 103.199.89.0/24 | AS48728 | — |
| 103.199.90.0/24 | AS48728 | — |
| 103.225.75.0/24 | AS48728 | — |
| 103.23.125.0/24 | AS48728 | — |
| 212.70.106.0/24 | AS48728 | — |
| 212.70.107.0/24 | AS48728 | — |
| 212.70.108.0/24 | AS48728 | — |
| 212.70.109.0/24 | AS48728 | — |
| 212.70.110.0/24 | AS48728 | — |
| 212.70.111.0/24 | AS48728 | — |
| 212.70.112.0/24 | AS48728 | — |
| 212.70.113.0/24 | AS48728 | — |
| 212.70.114.0/24 | AS48728 | — |
| 212.70.115.0/24 | AS48728 | — |
| 212.70.116.0/24 | AS48728 | — |
| 212.70.117.0/24 | AS48728 | — |
| 212.70.118.0/24 | AS48728 | — |
| 212.70.119.0/24 | AS48728 | — |
| 212.70.126.0/24 | AS48728 | — |
| 212.70.127.0/24 | AS48728 | — |
| 212.70.96.0/19 | AS48728 | — |
| 212.70.96.0/24 | AS48728 | — |
| 212.70.97.0/24 | AS48728 | — |
| 212.70.98.0/24 | AS48728 | — |
| 212.70.99.0/24 | AS48728 | — |
| 2a04:7f80:1000::/40 | AS48728 | — |
| 2a04:7f80:100::/48 | AS48728 | — |
| 2a04:7f80:10::/44 | AS48728 | — |
| 2a04:7f80:2000::/40 | AS48728 | — |
| 2a04:7f80:20::/44 | AS48728 | — |
| 2a04:7f80:2::/47 | AS48728 | — |
| 2a04:7f80:30::/44 | AS48728 | — |
| 2a04:7f80:40::/45 | AS48728 | — |
| 2a04:7f80:48::/45 | AS48728 | — |
| 2a04:7f80:4::/47 | AS48728 | — |
| 2a04:7f80:50::/45 | AS48728 | — |
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.
AS48728 is an autonomous system number used to identify an independently operated network. The current page associates it with VODAFONEQATAR - Vodafone Qatar P.Q.S.C 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 AS48728. 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 AS48728, 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.