Country
—
ASN LANDING PAGE
AS201701
FFRL-AS - Freifunk Rheinland e.V.
Last updated · Apr 4, 2026
Total prefixes
8
IPv4 prefixes
4
IPv6 prefixes
4
ASN summary
How to read the scale of AS201701
FFRL-AS - Freifunk Rheinland e.V. 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 AS201701?
FFRL-AS - Freifunk Rheinland e.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 AS201701 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
AS201701 ASN lookupAS201701 BGPAS201701 peersAS201701 prefixesAS201701 upstreamsFFRL-AS - Freifunk Rheinland e.V. ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS6939
AS6939
—
AS24961
AS24961
—
AS50629
AS50629
—
AS9136
AS9136
—
AS9002
AS9002
—
AS5405
AS5405
—
AS47147
AS47147
—
AS8881
AS8881
—
AS3320
AS3320
—
AS29670
AS29670
—
AS35625
AS35625
—
AS25091
AS25091
—
AS8298
AS8298
—
AS137409
AS137409
—
AS29632
AS29632
—
AS35280
AS35280
—
AS39351
AS39351
—
AS41327
AS41327
—
AS680
AS680
—
AS1828
AS1828
—
AS8758
AS8758
—
AS20485
AS20485
—
AS20764
AS20764
—
AS24482
AS24482
—
AS25220
AS25220
—
AS34019
AS34019
—
AS34927
AS34927
—
AS51185
AS51185
—
AS58299
AS58299
—
AS64475
AS64475
—
AS199938
AS199938
—
AS205112
AS205112
—
AS6057
AS6057
—
AS6797
AS6797
—
AS12779
AS12779
—
AS13237
AS13237
—
AS14840
AS14840
—
AS29075
AS29075
—
AS29140
AS29140
—
AS29691
AS29691
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 185.66.192.0/22 | AS201701 | — |
| 185.66.193.0/24 | AS201701 | — |
| 185.66.194.0/24 | AS201701 | — |
| 185.66.195.0/24 | AS201701 | — |
| 2a03:2260:1000::/36 | AS201701 | — |
| 2a03:2260:2000::/36 | AS201701 | — |
| 2a03:2260:3000::/36 | AS201701 | — |
| 2a03:2260::/30 | AS201701 | — |
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 AS201701 represent?
AS201701 is an autonomous system number used to identify an independently operated network. The current page associates it with FFRL-AS - Freifunk Rheinland e.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 AS201701 page?
They help explain the scale, interconnection depth, and route structure of AS201701. 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 AS201701?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS201701, 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.