--- license: cc-by-4.0 pretty_name: Cloudflare Domain Traffic Analytics Snapshot language: - en tags: - tabular - time-series - web-analytics - cloudflare - dns - cdn - cybersecurity - traffic-analysis - anomaly-detection - seo - parquet - duckdb - pandas - polars configs: - config_name: accounts data_files: - split: train path: data/accounts.parquet - config_name: data_dictionary data_files: - split: train path: data/data_dictionary.parquet - config_name: dns_analytics data_files: - split: train path: data/dns_analytics.parquet - config_name: dns_records data_files: - split: train path: data/dns_records.parquet - config_name: email_routing_rules data_files: - split: train path: data/email_routing_rules.parquet - config_name: firewall_events data_files: - split: train path: data/firewall_events.parquet - config_name: http_daily data_files: - split: train path: data/http_daily.parquet - config_name: http_dimension_groups data_files: - split: train path: data/http_dimension_groups.parquet - config_name: http_hourly data_files: - split: train path: data/http_hourly.parquet - config_name: http_hourly_browser_map data_files: - split: train path: data/http_hourly_browser_map.parquet - config_name: http_hourly_content_type_map data_files: - split: train path: data/http_hourly_content_type_map.parquet - config_name: http_hourly_country_map data_files: - split: train path: data/http_hourly_country_map.parquet - config_name: http_hourly_http_version_map data_files: - split: train path: data/http_hourly_http_version_map.parquet - config_name: http_hourly_ip_class_map data_files: - split: train path: data/http_hourly_ip_class_map.parquet - config_name: http_hourly_ssl_map data_files: - split: train path: data/http_hourly_ssl_map.parquet - config_name: http_hourly_status_map data_files: - split: train path: data/http_hourly_status_map.parquet - config_name: http_hourly_threat_pathing_map data_files: - split: train path: data/http_hourly_threat_pathing_map.parquet - config_name: metric_availability data_files: - split: train path: data/metric_availability.parquet - config_name: redirect_list_items data_files: - split: train path: data/redirect_list_items.parquet - config_name: redirect_lists data_files: - split: train path: data/redirect_lists.parquet - config_name: ruleset_rules data_files: - split: train path: data/ruleset_rules.parquet - config_name: rulesets data_files: - split: train path: data/rulesets.parquet - config_name: rum_pageload_groups data_files: - split: train path: data/rum_pageload_groups.parquet - config_name: rum_performance_groups data_files: - split: train path: data/rum_performance_groups.parquet - config_name: rum_web_vitals_groups data_files: - split: train path: data/rum_web_vitals_groups.parquet - config_name: speed_availability data_files: - split: train path: data/speed_availability.parquet - config_name: speed_pages data_files: - split: train path: data/speed_pages.parquet - config_name: ssl_certificate_packs data_files: - split: train path: data/ssl_certificate_packs.parquet - config_name: web_analytics_rules data_files: - split: train path: data/web_analytics_rules.parquet - config_name: web_analytics_sites data_files: - split: train path: data/web_analytics_sites.parquet - config_name: zone_settings data_files: - split: train path: data/zone_settings.parquet - config_name: zones data_files: - split: train path: data/zones.parquet --- # 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 ```python 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") ``` ```sql -- 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](https://developers.cloudflare.com/analytics/graphql-api/), [Web Analytics metrics](https://developers.cloudflare.com/web-analytics/data-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.