Country
—
ASN LANDING PAGE
SINGNET SingNet
Last updated · Apr 4, 2026
Country
—
Total prefixes
488
IPv4 prefixes
456
IPv6 prefixes
32
SINGNET SingNet currently shows 488 prefixes and 46 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.
SINGNET SingNet 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.
AS9255
AS9255
—
AS9506
AS9506
—
AS45143
AS45143
—
AS140929
AS140929
—
AS9890
AS9890
—
AS197537
AS197537
—
AS140592
AS140592
—
AS56094
AS56094
—
AS13778
AS13778
—
AS38481
AS38481
—
AS24467
AS24467
—
AS23728
AS23728
—
AS45133
AS45133
—
AS38055
AS38055
—
AS7610
AS7610
—
AS24030
AS24030
—
AS14630
AS14630
—
AS10376
AS10376
—
AS6619
AS6619
—
AS140928
AS140928
—
AS7054
AS7054
—
AS138947
AS138947
—
AS135048
AS135048
—
AS141760
AS141760
—
AS17617
AS17617
—
AS13167
AS13167
—
AS38862
AS38862
—
AS10794
AS10794
—
AS152903
AS152903
—
AS140610
AS140610
—
AS132265
AS132265
—
AS46071
AS46071
—
AS3911
AS3911
—
AS206618
AS206618
—
AS17733
AS17733
—
AS45432
AS45432
—
AS132804
AS132804
—
AS133470
AS133470
—
AS133471
AS133471
—
AS1217
AS1217
—
| Prefix | Name | Country |
|---|---|---|
| 101.78.127.0/24 | AS3758 | — |
| 103.186.249.0/24 | AS3758 | — |
| 111.65.100.0/24 | AS3758 | — |
| 111.65.102.0/23 | AS3758 | — |
| 111.65.104.0/21 | AS3758 | — |
| 111.65.108.0/22 | AS3758 | — |
| 111.65.112.0/20 | AS3758 | — |
| 115.42.128.0/17 | AS3758 | — |
| 115.42.181.0/24 | AS3758 | — |
| 115.42.185.0/24 | AS3758 | — |
| 115.42.195.0/24 | AS3758 | — |
| 115.42.196.0/24 | AS3758 | — |
| 115.42.204.0/24 | AS3758 | — |
| 115.42.206.0/24 | AS3758 | — |
| 115.42.217.0/24 | AS3758 | — |
| 115.42.219.0/24 | AS3758 | — |
| 115.42.222.0/24 | AS3758 | — |
| 115.42.251.0/24 | AS3758 | — |
| 115.42.255.0/24 | AS3758 | — |
| 115.66.20.0/23 | AS3758 | — |
| 115.66.33.0/24 | AS3758 | — |
| 115.66.56.0/21 | AS3758 | — |
| 116.12.128.0/17 | AS3758 | — |
| 116.12.137.0/24 | AS3758 | — |
| 116.12.138.0/24 | AS3758 | — |
| 116.12.147.0/24 | AS3758 | — |
| 116.12.154.0/24 | AS3758 | — |
| 116.12.156.0/24 | AS3758 | — |
| 116.12.205.0/24 | AS3758 | — |
| 116.12.206.0/24 | AS3758 | — |
| 116.12.214.0/24 | AS3758 | — |
| 116.12.226.0/24 | AS3758 | — |
| 116.12.229.0/24 | AS3758 | — |
| 116.12.234.0/24 | AS3758 | — |
| 116.12.235.0/24 | AS3758 | — |
| 116.12.238.0/24 | AS3758 | — |
| 116.12.243.0/24 | AS3758 | — |
| 116.14.123.0/24 | AS3758 | — |
| 116.14.132.0/23 | AS3758 | — |
| 116.14.48.0/23 | AS3758 | — |
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.
AS3758 is an autonomous system number used to identify an independently operated network. The current page associates it with SINGNET SingNet 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 AS3758. 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 AS3758, 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.