Lightcap/cloudflare-domain-traffic-analytics

Cloudflare Domain Traffic Analytics Snapshot

This repository is a structured snapshot of Cloudflare data across 200 zones. It combines domain inventory, redirect configuration, DNS metadata, Web Analytics setup, HTTP time series, request dimension groups, real-user page-load and Web Vitals metrics, DNS analytics, Speed API availability, and firewall aggregates where Cloudflare exposes them into analysis-ready Parquet tables.

The collection window for traffic tables is 2026-04-01T02:00:00Z to 2026-05-01T02:00:00Z UTC. The snapshot was generated at 2026-05-01T02:17:36Z.

Curated by Faruk Alpay. Contact: alpay@lightcap.ai.

The shape is intentionally relational: domains live in zones, redirects live in redirect_list_items, hourly and daily traffic live in http_hourly and http_daily, and high-cardinality request slices live in http_dimension_groups. That makes the data easy to query with DuckDB, Polars, Pandas, Spark, or datasets.load_dataset() without unpacking nested API responses.

Cloudflare GraphQL field availability is discovered per zone before querying. Unsupported firewall fields are not queried, so the public tables do not contain API failure rows; coverage and skipped field lists are recorded in metadata/collection_manifest.json and metadata/cloudflare_graphql_capabilities.json.

Tables

• accounts: 1 rows
• data_dictionary: 42 rows
• dns_analytics: 73,645 rows
• dns_records: 288 rows
• email_routing_rules: 201 rows
• firewall_events: 67,118 rows
• http_daily: 6,070 rows
• http_dimension_groups: 156,543 rows
• http_hourly: 10,585 rows
• http_hourly_browser_map: 902 rows
• http_hourly_content_type_map: 15,173 rows
• http_hourly_country_map: 20,939 rows
• http_hourly_http_version_map: 13,196 rows
• http_hourly_ip_class_map: 13,435 rows
• http_hourly_ssl_map: 19,638 rows
• http_hourly_status_map: 17,946 rows
• http_hourly_threat_pathing_map: 34 rows
• metric_availability: 6 rows
• redirect_list_items: 50 rows
• redirect_lists: 1 rows
• ruleset_rules: 36,664 rows
• rulesets: 783 rows
• rum_pageload_groups: 303 rows
• rum_performance_groups: 278 rows
• rum_web_vitals_groups: 165 rows
• speed_availability: 200 rows
• speed_pages: 1 rows
• ssl_certificate_packs: 200 rows
• web_analytics_rules: 12 rows
• web_analytics_sites: 12 rows
• zone_settings: 11,200 rows
• zones: 200 rows

schema/data_dictionary.json mirrors the table descriptions and important column notes. metadata/collection_manifest.json records the collection window, Cloudflare API surfaces, limits, and redaction boundary.

Quick Start

from datasets import load_dataset

hourly = load_dataset("Lightcap/cloudflare-domain-traffic-analytics", "http_hourly", split="train")
paths = load_dataset("Lightcap/cloudflare-domain-traffic-analytics", "http_dimension_groups", split="train")
zones = load_dataset("Lightcap/cloudflare-domain-traffic-analytics", "zones", split="train")

-- DuckDB example after cloning the repo or downloading files
SELECT
  zone_name,
  date_trunc('day', CAST(datetime_hour AS TIMESTAMP)) AS day,
  sum(requests) AS requests,
  max(unique_visitors) AS hourly_unique_peak
FROM 'data/http_hourly.parquet'
GROUP BY 1, 2
ORDER BY requests DESC;

Notes

• Cloudflare exposes aggregate visitor metrics here, not person-level sessions. unique_visitors is the Cloudflare uniq.uniques value for the chosen interval.
• RUM performance tables include page-load and rendering timings. They do not represent how long a visitor stayed on a page.
• Returning visitors, dwell time, bounce rate, and exit pages are not published as direct Cloudflare metrics in this export. metric_availability records those gaps explicitly instead of filling them with estimates.
• Full client IPs, full user-agent strings, query strings, session hashes, and hidden proxied DNS origins are excluded from the public files.
• Firewall event IPs and user agents, when available from Cloudflare, are represented as stable hashes rather than raw values.
• Proxied DNS record content is represented by a stable SHA-256 hash. Public redirect targets remain visible because they are part of the observable redirect graph.
• Rows with is_limit_boundary = true reached the configured Cloudflare API limit for that grouping and should be treated as potentially truncated.

Cloudflare references: GraphQL Analytics API, Web Analytics metrics.

Suggested Analyses

Traffic seasonality, bot-heavy domains, redirect concentration, anomaly detection, domain portfolio routing, DNS hygiene, cache behavior, country/ASN distribution, status-code drift, and launch-date inference from first observed traffic all work directly from the published tables.