Country
—
ASN LANDING PAGE
JTCL-JP-AS JCOM Co.
Last updated · Apr 4, 2026
Country
—
Total prefixes
293
IPv4 prefixes
231
IPv6 prefixes
62
JTCL-JP-AS JCOM Co. currently shows 293 prefixes and 31 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.
JTCL-JP-AS JCOM Co. 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.
AS9617
AS9617
—
AS4721
AS4721
—
AS9378
AS9378
—
AS18136
AS18136
—
AS24276
AS24276
—
AS18134
AS18134
—
AS23788
AS23788
—
AS45675
AS45675
—
AS9614
AS9614
—
AS7686
AS7686
—
AS23790
AS23790
—
AS45690
AS45690
—
AS23635
AS23635
—
AS24290
AS24290
—
AS23808
AS23808
—
AS17961
AS17961
—
AS18283
AS18283
—
AS24255
AS24255
—
AS7524
AS7524
—
AS17534
AS17534
—
AS9351
AS9351
—
| Prefix | Name | Country |
|---|---|---|
| 110.128.0.0/13 | AS9824 | — |
| 110.128.0.0/16 | AS9824 | — |
| 110.129.0.0/16 | AS9824 | — |
| 110.129.128.0/18 | AS9824 | — |
| 110.129.192.0/18 | AS9824 | — |
| 110.130.0.0/16 | AS9824 | — |
| 110.131.0.0/16 | AS9824 | — |
| 110.132.0.0/16 | AS9824 | — |
| 110.133.0.0/17 | AS9824 | — |
| 110.133.128.0/17 | AS9824 | — |
| 110.134.0.0/16 | AS9824 | — |
| 110.134.0.0/18 | AS9824 | — |
| 110.134.64.0/18 | AS9824 | — |
| 110.135.0.0/16 | AS9824 | — |
| 110.135.128.0/18 | AS9824 | — |
| 110.135.192.0/18 | AS9824 | — |
| 116.214.16.0/21 | AS9824 | — |
| 116.220.0.0/16 | AS9824 | — |
| 116.220.0.0/17 | AS9824 | — |
| 116.220.128.0/17 | AS9824 | — |
| 116.221.0.0/16 | AS9824 | — |
| 116.221.0.0/17 | AS9824 | — |
| 116.221.128.0/17 | AS9824 | — |
| 116.222.0.0/16 | AS9824 | — |
| 116.222.0.0/17 | AS9824 | — |
| 116.222.0.0/18 | AS9824 | — |
| 116.222.128.0/17 | AS9824 | — |
| 116.222.128.0/18 | AS9824 | — |
| 116.222.192.0/18 | AS9824 | — |
| 116.222.64.0/18 | AS9824 | — |
| 116.223.0.0/16 | AS9824 | — |
| 116.223.0.0/17 | AS9824 | — |
| 116.223.128.0/17 | AS9824 | — |
| 116.64.0.0/16 | AS9824 | — |
| 116.64.0.0/17 | AS9824 | — |
| 116.64.128.0/17 | AS9824 | — |
| 116.65.0.0/16 | AS9824 | — |
| 116.65.0.0/17 | AS9824 | — |
| 116.65.128.0/17 | AS9824 | — |
| 119.168.0.0/16 | AS9824 | — |
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.
AS9824 is an autonomous system number used to identify an independently operated network. The current page associates it with JTCL-JP-AS JCOM Co. 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 AS9824. 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 AS9824, 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.