Country
—
ASN LANDING PAGE
LOGIXCOMM-AS4 - Logix
Last updated · Apr 4, 2026
Country
—
Total prefixes
178
IPv4 prefixes
172
IPv6 prefixes
6
LOGIXCOMM-AS4 - Logix currently shows 178 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.
LOGIXCOMM-AS4 - Logix 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.
AS11215
AS11215
—
AS40799
AS40799
—
AS394646
AS394646
—
AS401085
AS401085
—
AS29730
AS29730
—
AS11012
AS11012
—
AS11941
AS11941
—
AS62504
AS62504
—
AS27414
AS27414
—
AS54855
AS54855
—
AS398780
AS398780
—
AS40638
AS40638
—
AS53285
AS53285
—
AS397497
AS397497
—
AS399373
AS399373
—
AS397751
AS397751
—
AS397542
AS397542
—
AS55102
AS55102
—
AS53287
AS53287
—
AS18867
AS18867
—
AS398477
AS398477
—
AS19337
AS19337
—
AS14382
AS14382
—
AS36636
AS36636
—
AS397107
AS397107
—
AS397844
AS397844
—
AS63325
AS63325
—
AS20099
AS20099
—
| Prefix | Name | Country |
|---|---|---|
| 139.138.128.0/18 | AS25956 | — |
| 139.138.128.0/21 | AS25956 | — |
| 139.138.136.0/21 | AS25956 | — |
| 139.138.144.0/21 | AS25956 | — |
| 139.138.152.0/21 | AS25956 | — |
| 139.138.160.0/19 | AS25956 | — |
| 162.252.160.0/22 | AS25956 | — |
| 192.52.188.0/22 | AS25956 | — |
| 192.64.92.0/22 | AS25956 | — |
| 193.105.21.0/24 | AS25956 | — |
| 199.115.168.0/22 | AS25956 | — |
| 199.15.164.0/22 | AS25956 | — |
| 199.15.164.0/23 | AS25956 | — |
| 199.15.166.0/23 | AS25956 | — |
| 199.20.32.0/24 | AS25956 | — |
| 199.229.75.0/24 | AS25956 | — |
| 199.241.248.0/21 | AS25956 | — |
| 199.241.252.0/23 | AS25956 | — |
| 199.241.254.0/23 | AS25956 | — |
| 199.48.84.0/24 | AS25956 | — |
| 199.48.85.0/24 | AS25956 | — |
| 199.48.86.0/24 | AS25956 | — |
| 199.48.87.0/24 | AS25956 | — |
| 199.79.190.0/24 | AS25956 | — |
| 206.126.32.0/19 | AS25956 | — |
| 206.126.32.0/20 | AS25956 | — |
| 206.126.48.0/21 | AS25956 | — |
| 206.126.56.0/22 | AS25956 | — |
| 206.126.60.0/22 | AS25956 | — |
| 207.91.128.0/18 | AS25956 | — |
| 207.91.128.0/20 | AS25956 | — |
| 207.91.144.0/20 | AS25956 | — |
| 207.91.160.0/23 | AS25956 | — |
| 207.91.162.0/23 | AS25956 | — |
| 207.91.164.0/22 | AS25956 | — |
| 207.91.168.0/21 | AS25956 | — |
| 207.91.176.0/20 | AS25956 | — |
| 209.189.232.0/21 | AS25956 | — |
| 209.189.232.0/23 | AS25956 | — |
| 209.189.234.0/23 | AS25956 | — |
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.
AS25956 is an autonomous system number used to identify an independently operated network. The current page associates it with LOGIXCOMM-AS4 - Logix 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 AS25956. 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 AS25956, 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.