Country
—
ASN LANDING PAGE
VNL1-AS
Last updated · Apr 4, 2026
Country
—
Total prefixes
472
IPv4 prefixes
463
IPv6 prefixes
9
VNL1-AS currently shows 472 prefixes and 43 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.
VNL1-AS 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.
AS328585
AS328585
—
AS327986
AS327986
—
AS328256
AS328256
—
AS328780
AS328780
—
AS329550
AS329550
—
AS9498
AS9498
—
AS37347
AS37347
—
AS328387
AS328387
—
AS211188
AS211188
—
AS329503
AS329503
—
AS36040
AS36040
—
AS328940
AS328940
—
AS329706
AS329706
—
AS329182
AS329182
—
AS327891
AS327891
—
AS328528
AS328528
—
AS37018
AS37018
—
AS327708
AS327708
—
AS136907
AS136907
—
AS37230
AS37230
—
AS329083
AS329083
—
AS13335
AS13335
—
AS329191
AS329191
—
AS6453
AS6453
—
AS328696
AS328696
—
AS327729
AS327729
—
AS37020
AS37020
—
AS37588
AS37588
—
AS329476
AS329476
—
AS141180
AS141180
—
AS329123
AS329123
—
AS328823
AS328823
—
AS37506
AS37506
—
| Prefix | Name | Country |
|---|---|---|
| 105.112.0.0/24 | AS36873 | — |
| 105.112.1.0/24 | AS36873 | — |
| 105.112.10.0/24 | AS36873 | — |
| 105.112.100.0/22 | AS36873 | — |
| 105.112.100.0/23 | AS36873 | — |
| 105.112.100.0/24 | AS36873 | — |
| 105.112.101.0/24 | AS36873 | — |
| 105.112.102.0/23 | AS36873 | — |
| 105.112.102.0/24 | AS36873 | — |
| 105.112.103.0/24 | AS36873 | — |
| 105.112.104.0/21 | AS36873 | — |
| 105.112.104.0/22 | AS36873 | — |
| 105.112.104.0/23 | AS36873 | — |
| 105.112.104.0/24 | AS36873 | — |
| 105.112.105.0/24 | AS36873 | — |
| 105.112.106.0/23 | AS36873 | — |
| 105.112.106.0/24 | AS36873 | — |
| 105.112.107.0/24 | AS36873 | — |
| 105.112.108.0/22 | AS36873 | — |
| 105.112.108.0/23 | AS36873 | — |
| 105.112.108.0/24 | AS36873 | — |
| 105.112.109.0/24 | AS36873 | — |
| 105.112.11.0/24 | AS36873 | — |
| 105.112.110.0/23 | AS36873 | — |
| 105.112.110.0/24 | AS36873 | — |
| 105.112.111.0/24 | AS36873 | — |
| 105.112.112.0/20 | AS36873 | — |
| 105.112.112.0/21 | AS36873 | — |
| 105.112.112.0/22 | AS36873 | — |
| 105.112.112.0/23 | AS36873 | — |
| 105.112.112.0/24 | AS36873 | — |
| 105.112.113.0/24 | AS36873 | — |
| 105.112.114.0/23 | AS36873 | — |
| 105.112.114.0/24 | AS36873 | — |
| 105.112.115.0/24 | AS36873 | — |
| 105.112.116.0/22 | AS36873 | — |
| 105.112.116.0/23 | AS36873 | — |
| 105.112.116.0/24 | AS36873 | — |
| 105.112.117.0/24 | AS36873 | — |
| 105.112.118.0/23 | AS36873 | — |
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.
AS36873 is an autonomous system number used to identify an independently operated network. The current page associates it with VNL1-AS 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 AS36873. 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 AS36873, 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.