Country
—
ASN LANDING PAGE
STCN STNet
Last updated · Apr 4, 2026
Country
—
Total prefixes
55
IPv4 prefixes
54
IPv6 prefixes
1
STCN STNet currently shows 55 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.
STCN STNet 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.
AS4637
AS4637
—
AS1299
AS1299
—
AS2516
AS2516
—
AS2497
AS2497
—
AS2519
AS2519
—
AS6939
AS6939
—
AS17676
AS17676
—
AS8298
AS8298
—
AS6057
AS6057
—
AS10010
AS10010
—
AS37468
AS37468
—
AS8220
AS8220
—
AS50763
AS50763
—
AS3399
AS3399
—
AS24482
AS24482
—
AS37721
AS37721
—
AS18260
AS18260
—
AS49544
AS49544
—
AS1103
AS1103
—
AS12779
AS12779
—
AS12859
AS12859
—
AS51185
AS51185
—
AS59105
AS59105
—
AS213241
AS213241
—
AS5405
AS5405
—
AS6777
AS6777
—
AS7195
AS7195
—
AS7575
AS7575
—
AS34019
AS34019
—
AS35280
AS35280
—
AS39120
AS39120
—
AS199524
AS199524
—
AS1828
AS1828
—
AS4713
AS4713
—
AS4777
AS4777
—
AS9304
AS9304
—
AS12637
AS12637
—
AS17639
AS17639
—
AS18106
AS18106
—
AS20562
AS20562
—
| Prefix | Name | Country |
|---|---|---|
| 101.1.128.0/17 | AS7522 | — |
| 103.3.12.0/22 | AS7522 | — |
| 110.2.192.0/20 | AS7522 | — |
| 110.2.208.0/20 | AS7522 | — |
| 115.30.128.0/17 | AS7522 | — |
| 115.31.0.0/18 | AS7522 | — |
| 119.150.0.0/20 | AS7522 | — |
| 119.150.16.0/20 | AS7522 | — |
| 119.150.240.0/20 | AS7522 | — |
| 122.129.160.0/19 | AS7522 | — |
| 122.145.48.0/20 | AS7522 | — |
| 122.145.64.0/19 | AS7522 | — |
| 122.145.96.0/20 | AS7522 | — |
| 122.248.64.0/19 | AS7522 | — |
| 123.230.0.0/16 | AS7522 | — |
| 123.254.0.0/18 | AS7522 | — |
| 125.215.64.0/19 | AS7522 | — |
| 125.215.96.0/19 | AS7522 | — |
| 133.123.0.0/16 | AS7522 | — |
| 150.52.0.0/16 | AS7522 | — |
| 175.103.224.0/19 | AS7522 | — |
| 183.176.0.0/16 | AS7522 | — |
| 2001:318::/32 | AS7522 | — |
| 202.11.160.0/22 | AS7522 | — |
| 202.240.176.0/23 | AS7522 | — |
| 202.243.187.0/24 | AS7522 | — |
| 202.246.114.0/24 | AS7522 | — |
| 202.255.16.0/21 | AS7522 | — |
| 202.67.16.0/20 | AS7522 | — |
| 202.70.208.0/20 | AS7522 | — |
| 202.84.80.0/20 | AS7522 | — |
| 203.112.32.0/19 | AS7522 | — |
| 203.139.192.0/19 | AS7522 | — |
| 210.142.224.0/19 | AS7522 | — |
| 210.157.224.0/19 | AS7522 | — |
| 210.159.176.0/20 | AS7522 | — |
| 211.132.64.0/19 | AS7522 | — |
| 211.7.224.0/19 | AS7522 | — |
| 218.231.48.0/20 | AS7522 | — |
| 218.40.112.0/20 | AS7522 | — |
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.
AS7522 is an autonomous system number used to identify an independently operated network. The current page associates it with STCN STNet 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 AS7522. 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 AS7522, 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.