Country
—
ASN LANDING PAGE
EMTEL-AS-AP
Last updated · Apr 10, 2026
Country
—
Total prefixes
171
IPv4 prefixes
169
IPv6 prefixes
2
EMTEL-AS-AP currently shows 171 prefixes and 58 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.
EMTEL-AS-AP 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.
AS4788
AS4788
—
AS37468
AS37468
—
AS37100
AS37100
—
AS6461
AS6461
—
AS20562
AS20562
—
AS6453
AS6453
—
AS6939
AS6939
—
AS8758
AS8758
—
AS34549
AS34549
—
AS29691
AS29691
—
AS48362
AS48362
—
AS5405
AS5405
—
AS8298
AS8298
—
AS20485
AS20485
—
AS20764
AS20764
—
AS34019
AS34019
—
AS34927
AS34927
—
AS35280
AS35280
—
AS6057
AS6057
—
AS12779
AS12779
—
AS24961
AS24961
—
AS34177
AS34177
—
AS50673
AS50673
—
AS29632
AS29632
—
AS205112
AS205112
—
AS24482
AS24482
—
AS25091
AS25091
—
AS42541
AS42541
—
AS58299
AS58299
—
AS64475
AS64475
—
AS209823
AS209823
—
AS553
AS553
—
AS1836
AS1836
—
AS3212
AS3212
—
AS8218
AS8218
—
AS25220
AS25220
—
AS28716
AS28716
—
AS31510
AS31510
—
AS35360
AS35360
—
AS39351
AS39351
—
| Prefix | Name | Country |
|---|---|---|
| 102.160.0.0/14 | AS30999 | — |
| 102.160.0.0/18 | AS30999 | — |
| 102.160.0.0/20 | AS30999 | — |
| 102.160.112.0/21 | AS30999 | — |
| 102.160.120.0/21 | AS30999 | — |
| 102.160.128.0/18 | AS30999 | — |
| 102.160.128.0/20 | AS30999 | — |
| 102.160.144.0/20 | AS30999 | — |
| 102.160.16.0/20 | AS30999 | — |
| 102.160.160.0/20 | AS30999 | — |
| 102.160.176.0/20 | AS30999 | — |
| 102.160.192.0/18 | AS30999 | — |
| 102.160.192.0/20 | AS30999 | — |
| 102.160.208.0/20 | AS30999 | — |
| 102.160.224.0/20 | AS30999 | — |
| 102.160.240.0/21 | AS30999 | — |
| 102.160.248.0/21 | AS30999 | — |
| 102.160.32.0/20 | AS30999 | — |
| 102.160.48.0/20 | AS30999 | — |
| 102.160.64.0/18 | AS30999 | — |
| 102.160.64.0/20 | AS30999 | — |
| 102.160.80.0/20 | AS30999 | — |
| 102.160.96.0/20 | AS30999 | — |
| 102.161.0.0/18 | AS30999 | — |
| 102.161.0.0/20 | AS30999 | — |
| 102.161.112.0/20 | AS30999 | — |
| 102.161.128.0/18 | AS30999 | — |
| 102.161.16.0/20 | AS30999 | — |
| 102.161.192.0/18 | AS30999 | — |
| 102.161.192.0/20 | AS30999 | — |
| 102.161.208.0/20 | AS30999 | — |
| 102.161.224.0/20 | AS30999 | — |
| 102.161.240.0/20 | AS30999 | — |
| 102.161.32.0/20 | AS30999 | — |
| 102.161.48.0/20 | AS30999 | — |
| 102.161.64.0/18 | AS30999 | — |
| 102.161.64.0/20 | AS30999 | — |
| 102.161.80.0/20 | AS30999 | — |
| 102.161.96.0/20 | AS30999 | — |
| 102.162.0.0/18 | AS30999 | — |
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.
AS30999 is an autonomous system number used to identify an independently operated network. The current page associates it with EMTEL-AS-AP 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 AS30999. 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 AS30999, 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.