Country
—
ASN LANDING PAGE
OCN NTT DOCOMO BUSINESS
Last updated · Apr 4, 2026
Country
—
Total prefixes
188
IPv4 prefixes
182
IPv6 prefixes
6
OCN NTT DOCOMO BUSINESS currently shows 188 prefixes and 47 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.
OCN NTT DOCOMO BUSINESS 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.
AS2914
AS2914
—
AS2510
AS2510
—
AS20940
AS20940
—
AS131893
AS131893
—
AS21433
AS21433
—
AS7677
AS7677
—
AS7524
AS7524
—
AS9619
AS9619
—
AS38629
AS38629
—
AS16880
AS16880
—
AS37900
AS37900
—
AS3573
AS3573
—
AS18092
AS18092
—
AS38639
AS38639
—
AS136586
AS136586
—
AS45680
AS45680
—
AS23777
AS23777
—
AS17937
AS17937
—
AS131901
AS131901
—
AS18150
AS18150
—
AS49274
AS49274
—
AS2526
AS2526
—
AS18271
AS18271
—
AS24512
AS24512
—
AS7678
AS7678
—
AS23619
AS23619
—
AS23804
AS23804
—
AS38643
AS38643
—
AS54535
AS54535
—
AS59109
AS59109
—
AS141694
AS141694
—
AS152871
AS152871
—
AS4680
AS4680
—
AS7513
AS7513
—
AS18072
AS18072
—
AS23613
AS23613
—
AS55949
AS55949
—
AS131902
AS131902
—
AS131977
AS131977
—
AS17934
AS17934
—
| Prefix | Name | Country |
|---|---|---|
| 103.163.250.0/23 | AS4713 | — |
| 114.144.0.0/12 | AS4713 | — |
| 114.160.0.0/11 | AS4713 | — |
| 118.0.0.0/12 | AS4713 | — |
| 118.16.0.0/13 | AS4713 | — |
| 119.161.104.0/21 | AS4713 | — |
| 121.112.0.0/13 | AS4713 | — |
| 122.1.0.0/16 | AS4713 | — |
| 122.16.0.0/12 | AS4713 | — |
| 123.216.0.0/13 | AS4713 | — |
| 123.224.0.0/14 | AS4713 | — |
| 124.84.0.0/14 | AS4713 | — |
| 124.96.0.0/13 | AS4713 | — |
| 125.170.0.0/16 | AS4713 | — |
| 125.172.0.0/14 | AS4713 | — |
| 125.200.0.0/13 | AS4713 | — |
| 133.153.0.0/16 | AS4713 | — |
| 133.153.22.0/24 | AS4713 | — |
| 138.212.224.0/24 | AS4713 | — |
| 138.212.225.0/24 | AS4713 | — |
| 138.212.227.0/24 | AS4713 | — |
| 138.212.228.0/24 | AS4713 | — |
| 138.212.229.0/24 | AS4713 | — |
| 138.212.230.0/24 | AS4713 | — |
| 138.212.238.0/24 | AS4713 | — |
| 138.212.239.0/24 | AS4713 | — |
| 138.212.241.0/24 | AS4713 | — |
| 138.212.245.0/24 | AS4713 | — |
| 138.212.249.0/24 | AS4713 | — |
| 138.212.252.0/24 | AS4713 | — |
| 150.35.0.0/16 | AS4713 | — |
| 150.35.235.0/24 | AS4713 | — |
| 150.5.64.0/18 | AS4713 | — |
| 150.61.128.0/17 | AS4713 | — |
| 150.61.13.0/24 | AS4713 | — |
| 150.61.17.0/24 | AS4713 | — |
| 150.61.31.0/24 | AS4713 | — |
| 150.61.33.0/24 | AS4713 | — |
| 150.61.35.0/24 | AS4713 | — |
| 150.61.4.0/24 | AS4713 | — |
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.
AS4713 is an autonomous system number used to identify an independently operated network. The current page associates it with OCN NTT DOCOMO BUSINESS 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 AS4713. 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 AS4713, 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.