Country
—
ASN LANDING PAGE
X-DSL-NET1
Last updated · Apr 4, 2026
Country
—
Total prefixes
91
IPv4 prefixes
85
IPv6 prefixes
6
X-DSL-NET1 currently shows 91 prefixes and 44 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.
X-DSL-NET1 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.
AS37271
AS37271
—
AS3223
AS3223
—
AS37680
AS37680
—
AS6939
AS6939
—
AS174
AS174
—
AS25091
AS25091
—
AS58453
AS58453
—
AS3303
AS3303
—
AS35280
AS35280
—
AS37468
AS37468
—
AS20764
AS20764
—
AS34549
AS34549
—
AS20562
AS20562
—
AS3214
AS3214
—
AS29075
AS29075
—
AS33891
AS33891
—
AS50304
AS50304
—
AS3741
AS3741
—
AS3216
AS3216
—
AS4455
AS4455
—
AS24482
AS24482
—
AS34177
AS34177
—
AS34927
AS34927
—
AS37100
AS37100
—
AS37497
AS37497
—
AS37721
AS37721
—
AS39120
AS39120
—
AS39351
AS39351
—
AS41327
AS41327
—
AS52320
AS52320
—
AS328206
AS328206
—
AS6204
AS6204
—
AS12969
AS12969
—
AS39122
AS39122
—
AS62275
AS62275
—
AS137409
AS137409
—
AS1031
AS1031
—
AS1828
AS1828
—
AS3170
AS3170
—
AS5713
AS5713
—
| Prefix | Name | Country |
|---|---|---|
| 192.142.128.0/20 | AS36916 | — |
| 192.142.144.0/20 | AS36916 | — |
| 192.142.160.0/20 | AS36916 | — |
| 192.142.176.0/20 | AS36916 | — |
| 192.142.184.0/21 | AS36916 | — |
| 192.142.198.0/23 | AS36916 | — |
| 192.142.230.0/23 | AS36916 | — |
| 192.142.240.0/21 | AS36916 | — |
| 192.142.64.0/19 | AS36916 | — |
| 192.142.96.0/19 | AS36916 | — |
| 216.132.156.0/22 | AS36916 | — |
| 216.132.236.0/22 | AS36916 | — |
| 216.132.244.0/22 | AS36916 | — |
| 216.132.252.0/22 | AS36916 | — |
| 2c0f:fcb0:2000::/36 | AS36916 | — |
| 2c0f:fcb0:3000::/36 | AS36916 | — |
| 2c0f:fcb0:5000::/36 | AS36916 | — |
| 2c0f:fcb0:6000::/36 | AS36916 | — |
| 2c0f:fcb0:9000::/36 | AS36916 | — |
| 2c0f:fcb0::/32 | AS36916 | — |
| 41.138.92.0/22 | AS36916 | — |
| 41.180.0.0/17 | AS36916 | — |
| 41.180.0.0/20 | AS36916 | — |
| 41.180.10.0/23 | AS36916 | — |
| 41.180.104.0/23 | AS36916 | — |
| 41.180.106.0/23 | AS36916 | — |
| 41.180.108.0/23 | AS36916 | — |
| 41.180.110.0/23 | AS36916 | — |
| 41.180.112.0/21 | AS36916 | — |
| 41.180.12.0/22 | AS36916 | — |
| 41.180.120.0/21 | AS36916 | — |
| 41.180.132.0/22 | AS36916 | — |
| 41.180.140.0/22 | AS36916 | — |
| 41.180.144.0/22 | AS36916 | — |
| 41.180.148.0/22 | AS36916 | — |
| 41.180.156.0/22 | AS36916 | — |
| 41.180.16.0/20 | AS36916 | — |
| 41.180.16.0/21 | AS36916 | — |
| 41.180.160.0/22 | AS36916 | — |
| 41.180.168.0/22 | AS36916 | — |
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.
AS36916 is an autonomous system number used to identify an independently operated network. The current page associates it with X-DSL-NET1 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 AS36916. 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 AS36916, 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.