Datacenter intelligence record
Cloudflare AS13335
Usually allowCloudflare · AS13335 · CDN / edge / security proxy · US
CDN / Edge
AS13335
CDN / Edge Network
CA, US
Confidence: High
- Provider
- Cloudflare
- ASN
- AS13335
- Country
- US
- Classification
- CDN / Edge Traffic
Handling Guidance
Usually allow- Log by default. Do not block Cloudflare globally unless you are protecting a specific origin endpoint and understand the proxy relationship.
- Datacenter matches are network-origin signals, not bot identities. Use them with request paths, cadence, user-agent evidence, and customer rules.
- Browser-looking traffic from cloud, hosting, VPS, CDN, transit, or automated infrastructure should be evaluated as infrastructure-origin traffic rather than automatically treated as a normal residential visitor.
Record Details
Provider and network data- Provider
- Cloudflare
- Organization
- Cloudflare, Inc.
- ASN
- AS13335
- ASN name
- CLOUDFLARENET
- Network
- CLOUDFLARENET
- Country
- US
- Region
- CA
- Services
- CDN, reverse proxy, security, DNS, edge network
- Provider type
- CDN / edge network
- Network type
- CDN / Edge / Security Proxy
- Classification
- CDN / Edge Traffic
- Traffic label
- CDN / Edge
- Confidence
- High
- Risk
- Low
- Default action
- Log
- Rules supported
- allow, block, rate-limit, log
- Last verified
- 2026-06-25
- Status
- Active
Detection and Behavior
Operational guidance- Common traffic pattern: Cloudflare traffic often appears as server, VPS, cloud, CDN, transit, or automated infrastructure rather than a residential browser session.
- Detection notes: Match by ASN AS13335. Combine network identity with user-agent, path, rate, country, and rule outcomes before enforcement.
- Behavior thresholds: Flag when request volume, identical user-agent reuse, API/feed scraping, login probing, search abuse, or repeated non-human path traversal exceeds normal visitor behavior.
- Human monitoring relevance: Useful for separating datacenter-origin requests from real human visitor traffic. Agency human monitoring should not classify hosting/cloud requests as normal residential humans without additional signals.
- Recommended action: Log by default. Do not block Cloudflare globally unless you are protecting a specific origin endpoint and understand the proxy relationship.
- Notes: Cloudflare is not a bot. It is an edge/CDN/security network. Treat source IPs carefully because visitors may appear behind Cloudflare.
Intelligence Summary
- Cloudflare is tracked by Botcrawl as cdn / edge / security proxy associated with AS13335. Traffic from this network should be evaluated as infrastructure-origin traffic rather than automatically treated as a normal residential visitor.
- Cloudflare traffic often appears as server, VPS, cloud, CDN, transit, or automated infrastructure rather than a residential browser session.
- Log by default. Do not block Cloudflare globally unless you are protecting a specific origin endpoint and understand the proxy relationship.
Evidence and Source
- Primary source: https://www.cloudflare.com/ips/
- Secondary source: https://developers.cloudflare.com/fundamentals/concepts/cloudflare-ip-addresses/
- Provider URL: https://www.cloudflare.com/
Use This Signal In Edge
Botcrawl EdgeBotcrawl Edge combines BotDB user-agent intelligence with datacenter provider signals, live volume, globe monitoring, analytics, API access, webhooks, and allow, block, rate-limit, or log rules across connected sites.
