Country
—
ASN LANDING PAGE
AS60606
BLINDSPOT - PRO-ZETA a.s.
Last updated · Apr 4, 2026
Total prefixes
8
IPv4 prefixes
6
IPv6 prefixes
2
ASN summary
How to read the scale of AS60606
BLINDSPOT - PRO-ZETA a.s. currently shows 8 prefixes and 43 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.
When is an ASN page most useful?
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.
How should you read the country, organization, and role of AS60606?
BLINDSPOT - PRO-ZETA a.s. 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.
What should you inspect next after the AS60606 page?
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.
Search intents this ASN page helps cover
AS60606 ASN lookupAS60606 BGPAS60606 peersAS60606 prefixesAS60606 upstreamsBLINDSPOT - PRO-ZETA a.s. ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS39392
AS39392
—
AS6939
AS6939
—
AS8218
AS8218
—
AS5405
AS5405
—
AS47200
AS47200
—
AS20562
AS20562
—
AS22356
AS22356
—
AS1764
AS1764
—
AS4455
AS4455
—
AS6881
AS6881
—
AS36236
AS36236
—
AS40994
AS40994
—
AS41327
AS41327
—
AS14840
AS14840
—
AS6663
AS6663
—
AS8529
AS8529
—
AS24482
AS24482
—
AS28917
AS28917
—
AS29504
AS29504
—
AS37721
AS37721
—
AS39120
AS39120
—
AS49544
AS49544
—
AS51184
AS51184
—
AS59890
AS59890
—
AS198150
AS198150
—
AS212483
AS212483
—
AS3212
AS3212
—
AS6204
AS6204
—
AS13194
AS13194
—
AS29049
AS29049
—
AS33891
AS33891
—
AS35369
AS35369
—
AS50629
AS50629
—
AS263444
AS263444
—
AS7713
AS7713
—
AS8881
AS8881
—
AS44306
AS44306
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 185.2.42.0/24 | AS60606 | — |
| 2001:67c:e94::/48 | AS60606 | — |
| 2a06:5d80::/32 | AS60606 | — |
| 91.239.200.0/22 | AS60606 | — |
| 91.239.200.0/23 | AS60606 | — |
| 91.239.202.0/23 | AS60606 | — |
| 95.173.203.0/24 | AS60606 | — |
| 95.173.212.0/24 | AS60606 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
WHOIS and IP Ownership Guide
Continue from the ASN page into WHOIS and ownership verification.
Frequently asked questions about this ASN page
What does AS60606 represent?
AS60606 is an autonomous system number used to identify an independently operated network. The current page associates it with BLINDSPOT - PRO-ZETA a.s. in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS60606 page?
They help explain the scale, interconnection depth, and route structure of AS60606. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS60606?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS60606, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
WHOIS vs ASN Ownership Guide
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
WHOIS and IP Ownership Guide
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
BGP and ASN Basics Guide
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Cloud Network and ASN Comparison
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.