Analytics Updates & Release Notes
147 updates curated from 1 source by the Releasebot Team. Last updated: Nov 11, 2026
- Nov 9, 2026
- Date parsed from source:Nov 9, 2026
- First seen by Releasebot:Nov 11, 2026
Redesigned Bots Directory on Cloudflare Radar, now powered by BotBase
Analytics expands Cloudflare Radar’s Bots Directory with BotBase data, redesigned bot pages, searchable operators, and richer API details for bot categories, access levels, content use, and documentation links.
The Cloudflare Radar Bots Directory ↗︎ now uses BotBase, Cloudflare's catalog of the bots and agents it tracks, and has a new design matching the Radar homepage.
Each bot page has a new Identity section showing the bot's access level, content use, Web Bot Auth verification, and user agents. Bot operators are also searchable from the Radar site search.
API
The List bots and Get bot details endpoints now describe each bot with:
- categories: a bot can now have more than one category. Categories follow BotBase's groups, which add COMMERCE, and some older categories are now part of broader groups.
- accessLevel: DIRECT if the bot reaches websites under its own identity, or INTERMEDIARY if it acts on behalf of another agent or a person.
- contentUse: full if the content it fetches is kept and reused (for example, for model training or a search index), reference if it is cited or linked back to the source, or immediate if it is used once to answer a user's request.
- documentationUrl and operatorWebsiteUrl (bot details only).
category and operatorUrl are deprecated in favor of categories and documentationUrl.
Visit the Bots Directory ↗︎ on Cloudflare Radar.
Original source - Nov 3, 2026
- Date parsed from source:Nov 3, 2026
- First seen by Releasebot:Nov 4, 2026
Zero Wire, a hub for investigating critical Internet vulnerabilities
Analytics adds Cloudflare Radar’s Zero Wire, a hub for investigating Internet vulnerabilities and threats with evidence-based briefings, remediation guidance, Cloudflare coverage details, and updates teams can follow by RSS.
Cloudflare Radar now includes Zero Wire ↗︎, a hub for investigating critical Internet vulnerabilities and threats. Each briefing separates confirmed facts from open questions, lists remediation steps, and shows what Cloudflare observes about the threat.
Briefings
Briefings are grouped by urgency. Needs attention covers active incidents, new guidance, or unresolved scope that security teams should review now. Reference keeps stable briefings available, even if not every affected system has been patched. Each card shows the recommended action and summarizes what happened, why it matters, and what to do.
Each briefing page expands on the card with an update chronology and an overview, followed by:
- What to do now: remediation steps, plus a prompt to copy into an AI agent with access to your infrastructure, asking for an evidence-based assessment of affected systems and exposure.
- Cloudflare coverage: the Cloudflare products that protect against the threat, and any impact on Cloudflare's own services.
- Evidence and sources: vendor advisories, CVE records, the CISA Known Exploited Vulnerabilities (KEV) catalog, and Radar charts, such as requests matching the related Cloudflare WAF rules.
Follow updates
Search briefings by CVE, name, or tag, or browse every briefing with a given tag. To follow new briefings and updates, subscribe to the Zero Wire RSS feed ↗︎ or to the feed of a single tag. New briefings also appear in the Caught on Radar ↗︎ section of the Radar homepage.
Send questions or feedback from any briefing page, or at [email protected].
For more details, read the blog post ↗︎ or visit Zero Wire ↗︎.
Original source All of your release notes in one feed
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Oct 30, 2026
- Date parsed from source:Oct 30, 2026
- First seen by Releasebot:Nov 2, 2026
Cloudflare WAN supports regional Gateway HTTP inspection
Analytics reports that Cloudflare WAN traffic can now use a selected Gateway processing region for TLS decryption and HTTP inspection, helping organizations control where sensitive traffic is processed and support data sovereignty goals.
Cloudflare WAN traffic can now use a Gateway processing region with Regional Services. HTTPS traffic enters a Cloudflare data center (that may be outside the selected region) via an IPsec or GRE tunnel, or through Direct CNI, and remains encrypted until Gateway forwards it to the selected region for TLS decryption and HTTP inspection. This feature gives organizations control over where their sensitive traffic is processed, supporting their data sovereignty goals.
This feature requires unified routing. The processing region applies to Gateway HTTP traffic and does not apply to Gateway DNS or network policy processing.
Contact your account team to configure a processing region. For supported regions, configuration details, and limitations, refer to Data residency for Cloudflare One.
Original source - Oct 29, 2026
- Date parsed from source:Oct 29, 2026
- First seen by Releasebot:Nov 2, 2026
View your data localization settings in one dashboard page
Analytics highlights Cloudflare’s new Data Localization Suite Overview, which brings Regional Services, Customer Metadata Boundary, and Geo Key Manager settings into one read-only dashboard view with links to manage settings and documentation.
The Cloudflare dashboard now includes a Data Localization Suite Overview, a read-only view of the data localization settings on your account. It shows your Regional Services, Customer Metadata Boundary, and Geo Key Manager settings in one place, so you no longer need to check several dashboard pages and APIs to see where your traffic is processed and where your logs and private keys are stored.
To find it, go to Application Security > Data Localization Suite, or search for "DLS" in the dashboard.
The Overview has a tab for each product:
- Regional Services: regionalized hostnames (filter by region or zone), regionalized IP bindings, and regionalized Spectrum applications, each with its region.
- Customer Metadata Boundary: whether the boundary is on, the region (US or EU), and whether out-of-region access is allowed.
- Geo Key Manager: every custom certificate with a geo policy, with its hostname, zone, region, and status.
Each item links to the dashboard page where you change its setting, and each tab links to the product's documentation.
To learn more, refer to the Data Localization Suite documentation.
Original source - Oct 27, 2026
- Date parsed from source:Oct 27, 2026
- First seen by Releasebot:Nov 2, 2026
SQL API introspection: `include_attributes` parameter
Analytics adds an SQL API introspection option to discover attribute keys and types from the previous seven days of account data. The clearer `include_attributes` and `attributes` names replace deprecated custom-attribute fields, which remain supported.
The SQL API introspection endpoint has a new
include_attributesquery parameter. Setting it to true discovers the keys of a dataset's attributes JSON column, and their types, from the preceding seven days of your account's data. Discovered keys are returned in the dataset's attributes response field.Some datasets store additional key-value data in an attributes JSON column, which you query with exact-key lookups such as
attributes['http.method']. The previous way to discover these keys,include_custom_attributes, returned names in acustom_attributesfield. The new names make it clearer that each returned name is a key you access through the attributes column.include_custom_attributesandcustom_attributesare deprecated but still work. Update integrations to useinclude_attributesandattributes.curl \ --get \ "https://api.cloudflare.com/client/v4/analytics/sql/introspection" \ --header "Authorization: Bearer <API_TOKEN>" \ --data-urlencode "account_tag=<ACCOUNT_TAG>" \ --data-urlencode "dataset_name=events.httpRequests" \ --data-urlencode "include_attributes=true"For more information, refer to Attributes.
Original source Similar to Analytics with recent updates:
- Notion updates157 release notes · Latest Nov 15, 2026
- OpenAI updates313 release notes · Latest Nov 18, 2026
- Application Security updates221 release notes · Latest Nov 18, 2026
- Agent Framework updates76 release notes · Latest Nov 13, 2026
- Cloudflare AI updates210 release notes · Latest Nov 18, 2026
- Anthropic updates79 release notes · Latest Oct 14, 2026
- Oct 23, 2026
- Date parsed from source:Oct 23, 2026
- First seen by Releasebot:Oct 24, 2026
Redesigned Cloudflare Radar homepage
Analytics redesigns Cloudflare Radar’s homepage with an interactive global Internet map, curated data insights, and an updated interface that makes trends easier to explore for broad audiences while retaining depth for technical users.
The Cloudflare Radar homepage has been redesigned to make global Internet data easier to explore for broader audiences, including journalists, policymakers, and everyday users, while preserving the depth that technical users rely on.
- Interactive map: Shows Internet traffic and outages around the world, and acts as a starting point for exploring specific countries and trends.
- Curated insights section: Tabbed navigation that highlights summary statistics across Radar data, with a call to action to explore each area in depth.
- Updated interface: Built with Kumo ↗︎ components, the same ones used across Cloudflare products.
As we continue the redesign, all Radar pages will see improvements. Share feedback at [email protected].
For more details, read the blog post ↗︎ or visit Cloudflare Radar ↗︎.
Original source - Oct 21, 2026
- Date parsed from source:Oct 21, 2026
- First seen by Releasebot:Nov 2, 2026
Account-scoped HTTP request logs in Logpush
Analytics adds account-scoped HTTP request logs to Cloudflare Logpush, letting one job deliver logs across every zone in an account.
Cloudflare Logpush now supports HTTP request logs as an account-scoped dataset. Use one job to deliver logs for every zone in an account instead of maintaining a separate job for each zone.
Create the job at the account level in the Cloudflare dashboard or through the Logpush API. The ZoneName field identifies the source zone in each log entry.
Custom fields remain configured per zone. An account-scoped job honors the custom fields configuration for each zone but does not support account-wide custom fields configuration.
For setup details, refer to API configuration.
Original source - Oct 13, 2026
- Date parsed from source:Oct 13, 2026
- First seen by Releasebot:Oct 13, 2026
Deeper Core Web Vitals Diagnostics: LCP & INP Sub-Part Metrics in Real User Monitoring
Analytics now breaks down LCP and INP into diagnostic phases and separates TCP connection time from TLS handshake time in Web Analytics RUM, helping users pinpoint page performance issues in dashboards or through the GraphQL API.
The Core Web Vitals tell you whether a page is slow but beyond perceived load time, layout instability, or responsiveness they do not guide you to the problematic area directly. To help you with this, Real User Monitoring (RUM) in Web Analytics now breaks Largest Contentful Paint (LCP) and Interaction to Next Paint (INP) into their respective sub-parts. It also splits connection time into TCP and TLS. You can see this visualised in the dashboard or query it through the GraphQL Analytics API.
LCP sub-parts
LCP is broken into four phases, so you can see which one is impacting your perceived load time:
- Time to First Byte: how long the browser waits for the HTML document (timeToFirstByte in GraphQL).
- Resource load delay: how long the browser takes to discover the LCP resource after the document starts arriving (lcpResourceLoadDelay).
- Resource load duration: how long it takes to download that resource (lcpResourceLoadTime).
- Element render delay: the gap between the resource arriving and the element appearing on screen (lcpElementRenderDelay).
You do not have to remember all this detail, there are tooltips available to guide you next to each sub-part metric in the dashboard.
INP sub-parts
INP is broken into three phases, guiding you to the area slowing down responsiveness:
- Input delay: how long an interaction (click, tap or key press) is blocked before it can be processed (inpInputDelay).
- Processing duration: how long your event handlers take to run (inpProcessingDuration).
- Presentation delay: how long the browser takes to render the next frame after the handlers finish (inpPresentationDelay).
TCP and TLS timing
The page load timing breakdown now separates connection setup from the TLS handshake, so you can tell a slow network path from a slow TLS negotiation:
- Connection time (excluding TLS) (connectionTimeWithoutTLS)
- TLS handshake time: (tlsTime).
Note: we've retained connectionTime in the GraphQL API so you can still analyze the combined time.
How to query the GraphQL data
The sub-parts are available on rumWebVitalsEventsAdaptiveGroups as percentiles, for example: lcpResourceLoadDelayP50 or inpInputDelayP50. The connection split is available on rumPerformanceEventsAdaptiveGroups as connectionTimeWithoutTLSP50 and tlsTimeP50, and so on for the other percentiles.
The percentiles available are: P25, P50, P75, P90, P95, P99, P999. All values are in microseconds. A negative value means the data is not available.
How to get started
Head to the 'Core Web Vitals' section, here you can scroll down the report to see the sub-parts. The 'Page Load' section contains the Connection and TLS negotiation durations.
For more on the data, refer to the Web Analytics docs and the GraphQL Analytics API docs.
Original source - Oct 7, 2026
- Date parsed from source:Oct 7, 2026
- First seen by Releasebot:Oct 7, 2026
Query Log Explorer datasets from Observability Logs
Analytics brings Log Explorer datasets into the Logs page in Cloudflare Observability, unifying them with Workers Observability, shared filters, SQL editing, and visualizations while keeping saved queries and datasets working.
Log Explorer datasets are now queried from the Logs page under Observability in the Cloudflare dashboard. The Logs page brings Log Explorer and Workers Observability datasets together with a shared filter builder, SQL editor, and visualizations.
As part of this change, the Log Explorer menu is no longer shown in the dashboard navigation.
- Your enabled datasets, saved queries, and SQL queries continue to work on the Logs page.
- To manage datasets, open the dataset selector on the Logs page and select Configure next to the Log Explorer datasets.
- The previous Log Search page remains available at its direct URL.
For more information, refer to Log Search and the Logs overview.
Original source - Oct 2, 2026
- Date parsed from source:Oct 2, 2026
- First seen by Releasebot:Oct 21, 2026
SQL API (Beta)
Analytics now offers Cloudflare’s SQL API in beta, bringing SQL queries for analytics and observability data through one HTTP endpoint. It supports common query operations, automatic sample weighting, and access from Workers without an API token, with direct querying available on all plans.
The SQL API is now available in beta. It provides a single HTTP endpoint for querying Cloudflare analytics and observability data using SQL. Supported dataset types include event datasets (such as HTTP requests and security events), state datasets (such as D1 storage), log datasets (such as Workers logs), and Workers Analytics Engine datasets.
The SQL API supports SELECT queries with filtering, aggregation, LIKE, CASE, BETWEEN, IS NULL, and ordering. Adaptively sampled datasets apply sample weights automatically for COUNT, SUM, and AVG. You can also query from a Cloudflare Worker using the Workers binding without managing an API token.
The SQL API powers Monitors and is available for direct querying on all plans.
For syntax, datasets, and limits, refer to SQL API.
Original source - Oct 2, 2026
- Date parsed from source:Oct 2, 2026
- First seen by Releasebot:Oct 2, 2026
30 days of analytics data on every plan
Analytics adds 30 days of analytics history for every plan, with Free and Pro domains keeping at least 31 days for adaptive datasets. It also brings domain analytics into one dashboard view with shared filters and time ranges across Traffic, Performance, Security, Cache, Origin, DNS, and Visitors.
Every plan now gets at least 30 days of analytics data. Adaptive analytics datasets, such as HTTP requests, security events, and DNS analytics, retain at least 31 days of data for Free and Pro domains, and you can query up to 30 days in a single request. Previously, Free and Pro domains could see between 24 hours and 8 days of history depending on the dataset.
A full month of history lets you investigate an issue after it happens, compare today with the same day in previous weeks, and tell a one-time spike from a longer trend. The change applies in the Cloudflare dashboard, in Custom Dashboards, and through the GraphQL Analytics API.
Domain analytics also now live in one place. In the Cloudflare dashboard, select a domain and go to Analytics to see Traffic, Performance, Security, Cache, Origin, DNS, and Visitors as tabs that share one time range and one set of filters. Account-level analytics are under Observability > Analytics.
This change does not alter which datasets or fields your plan can access. Aggregated datasets, such as httpRequests1hGroups, keep their existing per-plan limits. To check the exact retention and query window for a zone or account, query the settings for each dataset.
For plan-specific limits, refer to Security Analytics, Security Events, and GraphQL Analytics API limits.
Original source - Oct 2, 2026
- Date parsed from source:Oct 2, 2026
- First seen by Releasebot:Oct 2, 2026
Workers Observability logs and traces in Custom Dashboards
Analytics adds Custom Dashboards support for Workers Observability data, with new Logs and Traces datasets that let teams chart Worker activity alongside HTTP traffic, security events, and other analytics. It also expands Custom Dashboards to up to 100 dashboards per account.
You can now build Custom Dashboards charts from Workers Observability data. Two new datasets, Workers Observability — Logs and Workers Observability — Traces (OTel), let you chart Worker invocations, log levels, errors, CPU and wall time, span counts, and durations next to HTTP traffic, security events, and other analytics datasets.
This gives you one dashboard for an application that spans Cloudflare's network and your Workers. For example, you can put request volume, WAF blocks, and Worker error rates on the same view, filter all three by time range, and spot whether a spike in errors lines up with a change in traffic.
The datasets are available for every Worker in your account that has Workers Logs or Workers Traces turned on. Custom Dashboards also now allow up to 100 dashboards for every account.
To get started, refer to Workers Observability data in Custom Dashboards.
Original source - Sep 30, 2026
- Date parsed from source:Sep 30, 2026
- First seen by Releasebot:Oct 2, 2026
Logpush is now available on all plans with usage-based pricing
Analytics adds wider Logpush availability across Free, Pro, Business, and Enterprise plans with usage-based pricing, self-service setup for smaller plans, and general availability for Logpush Transformers.
Cloudflare Logpush is now available on Free, Pro, Business, and Enterprise plans with usage-based pricing. Free, Pro, and Business customers can enable Logpush through self-service. Enterprise customers continue to work with their account team. Logpush Transformers are also now generally available.
Each account receives included monthly usage before charges apply:
- Internal exports: 25 GB per month, then $0.03 per additional GB.
- External exports: 25 GB per month, then $0.10 per additional GB.
- Transformations: 1 GB per month, then $0.04 per additional GB.
R2 and Pipelines use the internal destination rate. All other destinations use the external destination rate.
Existing Enterprise contracts retain their current Logpush pricing through renewal. Workers Logpush for Workers Trace Events retains request-based pricing, and OpenTelemetry destinations retain event-based Workers Observability pricing.
For complete rates, measurement details, and billing examples, refer to Logpush pricing.
Original source - Sep 30, 2026
- Date parsed from source:Sep 30, 2026
- First seen by Releasebot:Oct 2, 2026
Transformers are now generally available
Analytics adds generally available Transformers for supported Logpush datasets, letting users filter, reshape, redact, compute fields, and add metadata with SQL before delivery. Available in Transformer Studio or via the Cloudflare API.
Transformers are now generally available for supported Logpush datasets on Free, Pro, Business, and Enterprise plans. Use SQL to filter records, reshape fields, redact sensitive values, compute new fields, or add metadata before Logpush delivers each batch.
Create and preview Transformers in Transformer Studio or through the Cloudflare API, then attach them to eligible account-scoped or zone-scoped Logpush jobs that use NDJSON output. Cloudflare validates each query against the dataset schema before saving it.
Each account includes 1 GB of transformation input per month. Additional input costs $0.04 per GB. For setup instructions, supported SQL, limits, and examples, refer to Transformers. For billing details, refer to Logpush pricing.
Original source - Sep 18, 2026
- Date parsed from source:Sep 18, 2026
- First seen by Releasebot:Sep 21, 2026
Filter DDoS attack traffic from Logpush jobs
Analytics adds Logpush DDoS traffic exclusion to reduce attack traffic in delivered logs.
Logpush jobs can now exclude identified distributed denial-of-service (DDoS) attack traffic. This option reduces attack traffic in delivered logs.
It supports the http_requests, firewall_events, and network_analytics_logs datasets.
In the dashboard, select Exclude DDoS attack traffic under Advanced Options. With the API, add this field to a job request:
{ "filter_attack_traffic": true }For more information, refer to API configuration.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.