Country
—
ASN LANDING PAGE
AS16350
ECHELON-AS - Root Holding B.V.
Last updated · Apr 4, 2026
Total prefixes
3
IPv4 prefixes
2
IPv6 prefixes
1
ASN summary
How to read the scale of AS16350
ECHELON-AS - Root Holding B.V. currently shows 3 prefixes and 40 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 AS16350?
ECHELON-AS - Root Holding B.V. 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 AS16350 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
AS16350 ASN lookupAS16350 BGPAS16350 peersAS16350 prefixesAS16350 upstreamsECHELON-AS - Root Holding B.V. ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Detailed data for this ASN is not available right now.
Peers
AS20562
AS20562
—
AS20847
AS20847
—
AS6939
AS6939
—
AS174
AS174
—
AS20485
AS20485
—
AS29632
AS29632
—
AS37100
AS37100
—
AS8218
AS8218
—
AS8298
AS8298
—
AS25091
AS25091
—
AS49434
AS49434
—
AS205112
AS205112
—
AS1103
AS1103
—
AS1140
AS1140
—
AS3212
AS3212
—
AS3333
AS3333
—
AS5713
AS5713
—
AS6204
AS6204
—
AS6696
AS6696
—
AS7713
AS7713
—
AS12859
AS12859
—
AS14907
AS14907
—
AS20932
AS20932
—
AS24482
AS24482
—
AS34019
AS34019
—
AS34927
AS34927
—
AS37721
AS37721
—
AS39249
AS39249
—
AS39351
AS39351
—
AS42541
AS42541
—
AS45489
AS45489
—
AS48185
AS48185
—
AS48646
AS48646
—
AS49544
AS49544
—
AS51185
AS51185
—
AS56987
AS56987
—
AS58299
AS58299
—
AS62167
AS62167
—
AS64475
AS64475
—
AS137409
AS137409
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 185.6.160.0/22 | AS16350 | — |
| 217.119.224.0/20 | AS16350 | — |
| 2a02:1398::/32 | AS16350 | — |
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 AS16350 represent?
AS16350 is an autonomous system number used to identify an independently operated network. The current page associates it with ECHELON-AS - Root Holding B.V. 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 AS16350 page?
They help explain the scale, interconnection depth, and route structure of AS16350. 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 AS16350?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS16350, 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.