Country
—
ASN LANDING PAGE
TDNC Community Network Center Inc.
Last updated · Apr 4, 2026
Country
—
Total prefixes
38
IPv4 prefixes
37
IPv6 prefixes
1
TDNC Community Network Center Inc. currently shows 38 prefixes and 52 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.
TDNC Community Network Center Inc. 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.
AS6939
AS6939
—
AS2518
AS2518
—
AS2519
AS2519
—
AS2516
AS2516
—
AS2497
AS2497
—
AS4713
AS4713
—
AS25091
AS25091
—
AS34549
AS34549
—
AS35280
AS35280
—
AS8220
AS8220
—
AS3214
AS3214
—
AS20764
AS20764
—
AS50304
AS50304
—
AS34177
AS34177
—
AS34927
AS34927
—
AS29075
AS29075
—
AS48362
AS48362
—
AS20562
AS20562
—
AS52320
AS52320
—
AS4455
AS4455
—
AS41327
AS41327
—
AS3170
AS3170
—
AS6424
AS6424
—
AS14630
AS14630
—
AS25160
AS25160
—
AS31742
AS31742
—
AS39351
AS39351
—
AS48070
AS48070
—
AS60068
AS60068
—
AS62167
AS62167
—
AS1267
AS1267
—
AS14840
AS14840
—
AS37721
AS37721
—
AS7195
AS7195
—
AS12969
AS12969
—
AS13237
AS13237
—
AS20485
AS20485
—
AS28792
AS28792
—
AS35266
AS35266
—
AS37680
AS37680
—
| Prefix | Name | Country |
|---|---|---|
| 103.131.120.0/22 | AS9354 | — |
| 103.40.104.0/22 | AS9354 | — |
| 104.92.64.0/22 | AS9354 | — |
| 125.2.128.0/18 | AS9354 | — |
| 125.2.192.0/20 | AS9354 | — |
| 133.149.80.0/20 | AS9354 | — |
| 157.5.0.0/19 | AS9354 | — |
| 202.157.224.0/21 | AS9354 | — |
| 202.157.232.0/23 | AS9354 | — |
| 202.157.234.0/23 | AS9354 | — |
| 202.157.236.0/23 | AS9354 | — |
| 202.157.238.0/23 | AS9354 | — |
| 202.157.240.0/22 | AS9354 | — |
| 202.157.244.0/22 | AS9354 | — |
| 202.157.248.0/22 | AS9354 | — |
| 202.157.252.0/22 | AS9354 | — |
| 210.158.144.0/20 | AS9354 | — |
| 210.251.192.0/20 | AS9354 | — |
| 210.251.208.0/20 | AS9354 | — |
| 211.1.192.0/19 | AS9354 | — |
| 211.2.64.0/18 | AS9354 | — |
| 219.100.224.0/23 | AS9354 | — |
| 219.100.226.0/24 | AS9354 | — |
| 219.118.128.0/19 | AS9354 | — |
| 219.99.0.0/19 | AS9354 | — |
| 221.118.0.0/18 | AS9354 | — |
| 221.118.128.0/18 | AS9354 | — |
| 221.118.192.0/18 | AS9354 | — |
| 221.118.64.0/18 | AS9354 | — |
| 222.229.96.0/19 | AS9354 | — |
| 223.252.64.0/20 | AS9354 | — |
| 223.252.80.0/20 | AS9354 | — |
| 2405:7000::/32 | AS9354 | — |
| 27.113.224.0/20 | AS9354 | — |
| 61.87.112.0/20 | AS9354 | — |
| 61.87.64.0/20 | AS9354 | — |
| 61.87.80.0/20 | AS9354 | — |
| 61.87.96.0/20 | AS9354 | — |
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.
AS9354 is an autonomous system number used to identify an independently operated network. The current page associates it with TDNC Community Network Center Inc. 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 AS9354. 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 AS9354, 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.