Country
—
ASN LANDING PAGE
N963-AS-AP N963 PTE. LTD.
Last updated · Apr 4, 2026
Country
—
Total prefixes
86
IPv4 prefixes
78
IPv6 prefixes
8
N963-AS-AP N963 PTE. LTD. currently shows 86 prefixes and 30 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.
N963-AS-AP N963 PTE. LTD. 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.
AS3257
AS3257
—
AS2914
AS2914
—
AS3356
AS3356
—
AS3491
AS3491
—
AS6939
AS6939
—
AS17676
AS17676
—
AS37468
AS37468
—
AS6057
AS6057
—
AS7195
AS7195
—
AS137409
AS137409
—
AS1828
AS1828
—
AS2500
AS2500
—
AS7575
AS7575
—
AS9002
AS9002
—
AS17639
AS17639
—
AS18106
AS18106
—
AS19151
AS19151
—
AS24482
AS24482
—
AS35280
AS35280
—
AS36236
AS36236
—
AS39120
AS39120
—
AS49544
AS49544
—
AS51185
AS51185
—
AS59105
AS59105
—
AS286
AS286
—
AS45489
AS45489
—
AS9304
AS9304
—
AS10099
AS10099
—
AS23764
AS23764
—
| Prefix | Name | Country |
|---|---|---|
| 103.203.51.0/24 | AS963 | — |
| 112.121.184.0/22 | AS963 | — |
| 112.121.184.0/24 | AS963 | — |
| 112.121.185.0/24 | AS963 | — |
| 112.121.186.0/24 | AS963 | — |
| 112.121.187.0/24 | AS963 | — |
| 141.193.154.0/24 | AS963 | — |
| 146.88.128.0/21 | AS963 | — |
| 146.88.128.0/24 | AS963 | — |
| 146.88.129.0/24 | AS963 | — |
| 146.88.130.0/24 | AS963 | — |
| 146.88.131.0/24 | AS963 | — |
| 146.88.132.0/24 | AS963 | — |
| 146.88.133.0/24 | AS963 | — |
| 146.88.134.0/24 | AS963 | — |
| 146.88.135.0/24 | AS963 | — |
| 157.85.224.0/21 | AS963 | — |
| 157.85.224.0/24 | AS963 | — |
| 157.85.225.0/24 | AS963 | — |
| 157.85.226.0/24 | AS963 | — |
| 157.85.227.0/24 | AS963 | — |
| 157.85.228.0/24 | AS963 | — |
| 157.85.229.0/24 | AS963 | — |
| 157.85.230.0/24 | AS963 | — |
| 157.85.231.0/24 | AS963 | — |
| 157.85.236.0/24 | AS963 | — |
| 157.85.237.0/24 | AS963 | — |
| 160.191.132.0/23 | AS963 | — |
| 160.191.132.0/24 | AS963 | — |
| 160.191.133.0/24 | AS963 | — |
| 163.223.198.0/23 | AS963 | — |
| 163.223.198.0/24 | AS963 | — |
| 163.223.199.0/24 | AS963 | — |
| 175.41.21.0/24 | AS963 | — |
| 175.41.22.0/24 | AS963 | — |
| 175.41.23.0/24 | AS963 | — |
| 175.41.24.0/24 | AS963 | — |
| 175.41.25.0/24 | AS963 | — |
| 175.41.26.0/24 | AS963 | — |
| 175.41.27.0/24 | AS963 | — |
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.
AS963 is an autonomous system number used to identify an independently operated network. The current page associates it with N963-AS-AP N963 PTE. LTD. 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 AS963. 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 AS963, 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.