Country
—
ASN LANDING PAGE
BECKMAN-COULTER-ASN - BECKMAN COULTER
Last updated · Apr 4, 2026
Country
—
Total prefixes
89
IPv4 prefixes
89
IPv6 prefixes
0
BECKMAN-COULTER-ASN - BECKMAN COULTER currently shows 89 prefixes and 32 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.
BECKMAN-COULTER-ASN - BECKMAN COULTER 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.
AS7018
AS7018
—
AS3257
AS3257
—
AS9318
AS9318
—
AS327782
AS327782
—
AS33363
AS33363
—
AS3356
AS3356
—
AS8220
AS8220
—
AS9498
AS9498
—
AS16735
AS16735
—
AS39156
AS39156
—
AS45820
AS45820
—
AS6181
AS6181
—
AS17222
AS17222
—
AS174
AS174
—
AS10796
AS10796
—
AS577
AS577
—
AS812
AS812
—
AS6730
AS6730
—
AS16019
AS16019
—
AS29208
AS29208
—
AS8359
AS8359
—
AS11404
AS11404
—
AS33491
AS33491
—
AS1221
AS1221
—
AS2764
AS2764
—
AS19332
AS19332
—
AS13367
AS13367
—
AS33652
AS33652
—
AS33668
AS33668
—
AS33651
AS33651
—
AS33667
AS33667
—
AS286
AS286
—
| Prefix | Name | Country |
|---|---|---|
| 134.217.0.0/22 | AS35928 | — |
| 134.217.112.0/23 | AS35928 | — |
| 134.217.112.0/24 | AS35928 | — |
| 134.217.113.0/24 | AS35928 | — |
| 134.217.114.0/24 | AS35928 | — |
| 134.217.115.0/24 | AS35928 | — |
| 134.217.132.0/23 | AS35928 | — |
| 134.217.132.0/24 | AS35928 | — |
| 134.217.133.0/24 | AS35928 | — |
| 134.217.134.0/24 | AS35928 | — |
| 134.217.140.0/24 | AS35928 | — |
| 134.217.141.0/24 | AS35928 | — |
| 134.217.142.0/24 | AS35928 | — |
| 134.217.148.0/24 | AS35928 | — |
| 134.217.149.0/24 | AS35928 | — |
| 134.217.150.0/24 | AS35928 | — |
| 134.217.162.0/23 | AS35928 | — |
| 134.217.163.0/24 | AS35928 | — |
| 134.217.164.0/22 | AS35928 | — |
| 134.217.166.0/24 | AS35928 | — |
| 134.217.173.0/24 | AS35928 | — |
| 134.217.174.0/24 | AS35928 | — |
| 134.217.176.0/24 | AS35928 | — |
| 134.217.177.0/24 | AS35928 | — |
| 134.217.180.0/22 | AS35928 | — |
| 134.217.180.0/23 | AS35928 | — |
| 134.217.180.0/24 | AS35928 | — |
| 134.217.181.0/24 | AS35928 | — |
| 134.217.182.0/23 | AS35928 | — |
| 134.217.182.0/24 | AS35928 | — |
| 134.217.184.0/24 | AS35928 | — |
| 134.217.185.0/24 | AS35928 | — |
| 134.217.186.0/23 | AS35928 | — |
| 134.217.186.0/24 | AS35928 | — |
| 134.217.187.0/24 | AS35928 | — |
| 134.217.189.0/24 | AS35928 | — |
| 134.217.190.0/24 | AS35928 | — |
| 134.217.192.0/22 | AS35928 | — |
| 134.217.192.0/23 | AS35928 | — |
| 134.217.192.0/24 | AS35928 | — |
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.
AS35928 is an autonomous system number used to identify an independently operated network. The current page associates it with BECKMAN-COULTER-ASN - BECKMAN COULTER 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 AS35928. 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 AS35928, 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.