Country
—
ASN LANDING PAGE
MDNET - Mach Dilemma
Last updated · Apr 4, 2026
Country
—
Total prefixes
49
IPv4 prefixes
10
IPv6 prefixes
39
MDNET - Mach Dilemma currently shows 49 prefixes and 20 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.
MDNET - Mach Dilemma 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.
Detailed data for this ASN is not available right now.
AS20473
AS20473
—
AS36236
AS36236
—
AS6939
AS6939
—
AS47787
AS47787
—
AS8298
AS8298
—
AS1003
AS1003
—
AS1828
AS1828
—
AS9002
AS9002
—
AS18106
AS18106
—
AS24482
AS24482
—
AS34927
AS34927
—
AS35280
AS35280
—
AS49544
AS49544
—
AS56662
AS56662
—
AS58057
AS58057
—
AS137409
AS137409
—
AS200454
AS200454
—
AS212024
AS212024
—
AS394256
AS394256
—
AS400587
AS400587
—
| Prefix | Name | Country |
|---|---|---|
| 103.196.36.0/23 | AS40138 | — |
| 103.196.36.0/24 | AS40138 | — |
| 103.196.37.0/24 | AS40138 | — |
| 103.196.38.0/24 | AS40138 | — |
| 198.72.6.0/24 | AS40138 | — |
| 2402:e580:73e9::/48 | AS40138 | — |
| 2402:e580:73ea::/48 | AS40138 | — |
| 2402:e580:73eb::/48 | AS40138 | — |
| 2402:e580:73ee::/48 | AS40138 | — |
| 2402:e580:73ef::/48 | AS40138 | — |
| 2402:e580:73f0::/48 | AS40138 | — |
| 2402:e580:73f1::/48 | AS40138 | — |
| 2402:e580:73f2::/48 | AS40138 | — |
| 2402:e580:73f3::/48 | AS40138 | — |
| 2402:e580:73f6::/48 | AS40138 | — |
| 2402:e580:73f7::/48 | AS40138 | — |
| 2402:e580:73f8::/48 | AS40138 | — |
| 2402:e580:73f9::/48 | AS40138 | — |
| 2402:e580:744d::/48 | AS40138 | — |
| 2402:e580:744e::/48 | AS40138 | — |
| 2402:e580:744f::/48 | AS40138 | — |
| 2402:e580:7450::/48 | AS40138 | — |
| 2402:e580:7451::/48 | AS40138 | — |
| 2402:e580:7452::/48 | AS40138 | — |
| 2402:e580:7453::/48 | AS40138 | — |
| 2402:e580:7456::/48 | AS40138 | — |
| 2402:e580:745a::/48 | AS40138 | — |
| 2402:e580:74b1::/48 | AS40138 | — |
| 2402:e580:74b2::/48 | AS40138 | — |
| 2402:e580:74b3::/48 | AS40138 | — |
| 2402:e580:74b5::/48 | AS40138 | — |
| 2402:e580:74b6::/48 | AS40138 | — |
| 2402:e580:74b7::/48 | AS40138 | — |
| 2402:e580:74b8::/48 | AS40138 | — |
| 2402:e580:74b9::/48 | AS40138 | — |
| 2402:e580:74ba::/48 | AS40138 | — |
| 2402:e580:77d3::/48 | AS40138 | — |
| 2402:e580:77d7::/48 | AS40138 | — |
| 2402:e580:77de::/48 | AS40138 | — |
| 2402:e580:7836::/48 | AS40138 | — |
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.
AS40138 is an autonomous system number used to identify an independently operated network. The current page associates it with MDNET - Mach Dilemma 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 AS40138. 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 AS40138, 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.