Country
—
ASN LANDING PAGE
NATOLAB - Black Mesa Corporation
Last updated · Apr 4, 2026
Country
—
Total prefixes
37
IPv4 prefixes
15
IPv6 prefixes
22
NATOLAB - Black Mesa Corporation currently shows 37 prefixes and 32 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.
NATOLAB - Black Mesa Corporation 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.
AS38008
AS38008
—
AS6939
AS6939
—
AS20473
AS20473
—
AS50131
AS50131
—
AS34927
AS34927
—
AS36236
AS36236
—
AS49544
AS49544
—
AS10111
AS10111
—
AS206499
AS206499
—
AS137409
AS137409
—
AS9002
AS9002
—
AS25091
AS25091
—
AS8298
AS8298
—
AS394256
AS394256
—
AS1828
AS1828
—
AS7575
AS7575
—
AS18106
AS18106
—
AS24482
AS24482
—
AS34854
AS34854
—
AS34872
AS34872
—
AS51185
AS51185
—
AS52025
AS52025
—
AS58057
AS58057
—
AS58299
AS58299
—
AS210937
AS210937
—
AS213151
AS213151
—
AS400587
AS400587
—
| Prefix | Name | Country |
|---|---|---|
| 103.152.112.0/23 | AS46997 | — |
| 103.152.112.0/24 | AS46997 | — |
| 103.152.113.0/24 | AS46997 | — |
| 103.175.98.0/23 | AS46997 | — |
| 103.175.98.0/24 | AS46997 | — |
| 103.175.99.0/24 | AS46997 | — |
| 103.186.163.0/24 | AS46997 | — |
| 134.195.100.0/23 | AS46997 | — |
| 134.195.100.0/24 | AS46997 | — |
| 134.195.101.0/24 | AS46997 | — |
| 141.193.21.0/24 | AS46997 | — |
| 2001:470:139::/48 | AS46997 | — |
| 23.247.136.0/23 | AS46997 | — |
| 23.247.136.0/24 | AS46997 | — |
| 23.247.137.0/24 | AS46997 | — |
| 2400:a6a0:200::/40 | AS46997 | — |
| 2406:4440:20::/44 | AS46997 | — |
| 2406:4440:40::/44 | AS46997 | — |
| 2406:4440:d6ff::/48 | AS46997 | — |
| 2602:fd92:c20::/44 | AS46997 | — |
| 2602:fd92:c20::/45 | AS46997 | — |
| 2602:fd92:c28::/45 | AS46997 | — |
| 2602:feda:30::/44 | AS46997 | — |
| 2602:feda:38::/45 | AS46997 | — |
| 2602:feda:3::/48 | AS46997 | — |
| 2602:feda:4::/48 | AS46997 | — |
| 2602:feda:60::/44 | AS46997 | — |
| 2602:feda:8::/48 | AS46997 | — |
| 2602:feda::/48 | AS46997 | — |
| 2602:feda:a3::/48 | AS46997 | — |
| 2602:feda:dd0::/44 | AS46997 | — |
| 2602:feda:f100::/40 | AS46997 | — |
| 2602:feda:f200::/44 | AS46997 | — |
| 2602:feda:f300::/40 | AS46997 | — |
| 2602:feda:f300::/41 | AS46997 | — |
| 2602:feda:f300::/44 | AS46997 | — |
| 44.68.205.0/24 | AS46997 | — |
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.
AS46997 is an autonomous system number used to identify an independently operated network. The current page associates it with NATOLAB - Black Mesa Corporation 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 AS46997. 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 AS46997, 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.