Country
—
ASN LANDING PAGE
IBOSS-AS-AP IBOSS Inc.
Last updated · Apr 4, 2026
Country
—
Total prefixes
37
IPv4 prefixes
25
IPv6 prefixes
12
IBOSS-AS-AP IBOSS Inc. currently shows 37 prefixes and 23 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.
IBOSS-AS-AP IBOSS 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.
Detailed data for this ASN is not available right now.
AS15830
AS15830
—
AS21859
AS21859
—
AS140641
AS140641
—
AS8529
AS8529
—
AS8452
AS8452
—
AS38195
AS38195
—
AS3356
AS3356
—
AS2914
AS2914
—
AS4826
AS4826
—
AS37100
AS37100
—
AS7473
AS7473
—
AS1299
AS1299
—
AS3491
AS3491
—
AS7474
AS7474
—
AS17676
AS17676
—
AS6453
AS6453
—
AS4455
AS4455
—
AS4755
AS4755
—
AS31216
AS31216
—
AS43531
AS43531
—
AS137409
AS137409
—
AS24482
AS24482
—
AS55720
AS55720
—
| Prefix | Name | Country |
|---|---|---|
| 103.111.180.0/23 | AS137922 | — |
| 103.111.182.0/24 | AS137922 | — |
| 103.111.183.0/24 | AS137922 | — |
| 124.40.55.0/24 | AS137922 | — |
| 136.228.216.0/24 | AS137922 | — |
| 136.228.218.0/24 | AS137922 | — |
| 136.228.222.0/24 | AS137922 | — |
| 136.228.223.0/24 | AS137922 | — |
| 136.228.229.0/24 | AS137922 | — |
| 136.228.230.0/23 | AS137922 | — |
| 136.228.239.0/24 | AS137922 | — |
| 136.228.241.0/24 | AS137922 | — |
| 136.228.243.0/24 | AS137922 | — |
| 138.43.97.0/24 | AS137922 | — |
| 149.19.35.0/24 | AS137922 | — |
| 149.19.44.0/24 | AS137922 | — |
| 149.19.50.0/24 | AS137922 | — |
| 149.19.57.0/24 | AS137922 | — |
| 163.120.69.0/24 | AS137922 | — |
| 163.120.75.0/24 | AS137922 | — |
| 163.120.79.0/24 | AS137922 | — |
| 163.120.94.0/23 | AS137922 | — |
| 170.128.88.0/24 | AS137922 | — |
| 170.128.89.0/24 | AS137922 | — |
| 170.128.91.0/24 | AS137922 | — |
| 2402:a0c0:1::/48 | AS137922 | — |
| 2402:a0c0:2::/48 | AS137922 | — |
| 2402:a0c0:3::/48 | AS137922 | — |
| 2402:a0c0:4::/48 | AS137922 | — |
| 2402:a0c0:5::/48 | AS137922 | — |
| 2402:a0c0:6::/48 | AS137922 | — |
| 2402:a0c0::/48 | AS137922 | — |
| 2a03:b8c0:11::/48 | AS137922 | — |
| 2a03:b8c0:16::/48 | AS137922 | — |
| 2a03:b8c0:17::/48 | AS137922 | — |
| 2a03:b8c0:18::/48 | AS137922 | — |
| 2a03:b8c0:27::/48 | AS137922 | — |
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.
AS137922 is an autonomous system number used to identify an independently operated network. The current page associates it with IBOSS-AS-AP IBOSS 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 AS137922. 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 AS137922, 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.