Country
—
ASN LANDING PAGE
AS395747
CLOUDFLARENET-SFO05 - Cloudflare
Last updated · Apr 4, 2026
Total prefixes
43
IPv4 prefixes
21
IPv6 prefixes
22
ASN summary
How to read the scale of AS395747
CLOUDFLARENET-SFO05 - Cloudflare currently shows 43 prefixes and 3 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 AS395747?
CLOUDFLARENET-SFO05 - Cloudflare 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 AS395747 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
AS395747 ASN lookupAS395747 BGPAS395747 peersAS395747 prefixesAS395747 upstreamsCLOUDFLARENET-SFO05 - Cloudflare ASNCDN ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Detailed data for this ASN is not available right now.
Peers
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 108.162.209.0/24 | AS395747 | — |
| 162.158.57.0/24 | AS395747 | — |
| 162.158.58.0/24 | AS395747 | — |
| 162.158.64.0/24 | AS395747 | — |
| 162.159.204.0/24 | AS395747 | — |
| 172.64.202.0/24 | AS395747 | — |
| 172.68.136.0/24 | AS395747 | — |
| 172.69.61.0/24 | AS395747 | — |
| 172.70.95.0/24 | AS395747 | — |
| 172.71.136.0/24 | AS395747 | — |
| 172.71.18.0/24 | AS395747 | — |
| 172.71.19.0/24 | AS395747 | — |
| 172.71.91.0/24 | AS395747 | — |
| 198.41.128.0/24 | AS395747 | — |
| 198.41.138.0/24 | AS395747 | — |
| 198.41.139.0/24 | AS395747 | — |
| 2400:cb00:1010::/48 | AS395747 | — |
| 2400:cb00:1011::/48 | AS395747 | — |
| 2400:cb00:1057::/48 | AS395747 | — |
| 2400:cb00:133::/48 | AS395747 | — |
| 2400:cb00:251::/48 | AS395747 | — |
| 2400:cb00:517::/48 | AS395747 | — |
| 2400:cb00:518::/48 | AS395747 | — |
| 2400:cb00:531::/48 | AS395747 | — |
| 2400:cb00:539::/48 | AS395747 | — |
| 2400:cb00:693::/48 | AS395747 | — |
| 2400:cb00:748::/48 | AS395747 | — |
| 2400:cb00:922::/48 | AS395747 | — |
| 2606:4700:f3::/48 | AS395747 | — |
| 2606:54c1:2::/48 | AS395747 | — |
| 2606:54c1:3::/48 | AS395747 | — |
| 2606:54c1:9::/48 | AS395747 | — |
| 2606:54c1:d::/48 | AS395747 | — |
| 2a06:98c0:1c00::/48 | AS395747 | — |
| 2a06:98c0:1c0b::/48 | AS395747 | — |
| 2a06:98c0:1c4a::/48 | AS395747 | — |
| 2a06:98c0:1c59::/48 | AS395747 | — |
| 2a09:bac0:748::/48 | AS395747 | — |
| 8.14.199.0/24 | AS395747 | — |
| 8.17.207.0/24 | AS395747 | — |
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
Cloudflare DNS Primary vs Secondary Guide
Useful for comparing Cloudflare DNS primary and secondary nodes inside the same ASN footprint.
Cloudflare IP Identification Guide
Useful for deciding whether this ASN behaves more like Cloudflare DNS, CDN, WAF, or another edge-delivery role.
Public DNS IP and Network Comparison
Useful for comparing Cloudflare DNS against other public-resolver networks.
Cloudflare DNS vs Public DNS Guide
Useful for comparing Cloudflare DNS against broader public-resolver patterns.
Cloudflare DNS vs ISP DNS Guide
Useful for comparing Cloudflare DNS with local ISP or carrier DNS behavior.
Cloudflare DNS vs Enterprise DNS Guide
Useful for comparing Cloudflare DNS with more enterprise-oriented DNS services.
Frequently asked questions about this ASN page
What does AS395747 represent?
AS395747 is an autonomous system number used to identify an independently operated network. The current page associates it with CLOUDFLARENET-SFO05 - Cloudflare 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 AS395747 page?
They help explain the scale, interconnection depth, and route structure of AS395747. 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 AS395747?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS395747, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
Cloudflare IP Identification Guide
Use ASN, WHOIS, Anycast, and service context to decide whether an IP looks more like Cloudflare DNS, CDN, WAF, or edge-delivery infrastructure.
Cloudflare DNS Primary vs Secondary Guide
Compare 1.1.1.1 and 1.0.0.1 across ASN ownership, Anycast footprint, prefixes, and resolver role to understand Cloudflare DNS primary and secondary nodes.
Cloudflare DNS vs Public DNS Guide
Compare Cloudflare DNS with other public-resolver networks to understand what kind of DNS service 1.1.1.1 represents across ASN ownership, Anycast edge context, deployment footprint, and resolver role.
Cloudflare DNS vs ISP DNS Guide
Compare Cloudflare DNS with ISP or carrier DNS across Anycast context, resolver independence, local cache behavior, and real-world usage.