Analytics Release Notes
Last updated: Apr 4, 2026
- Apr 2, 2026
- Date parsed from source:Apr 2, 2026
- First seen by Releasebot:Apr 4, 2026
BigQuery as Logpush destination
Analytics adds BigQuery as a native Logpush destination for Cloudflare logs.
Cloudflare Logpush now supports BigQuery as a native destination.
Logs from Cloudflare can be sent to Google Cloud BigQuery via Logpush. The destination can be configured through the Logpush UI in the Cloudflare dashboard or by using the Logpush API.
For more information, refer to the Destination Configuration documentation.
Original source Report a problem - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 1, 2026
Routing Section Expansion on Cloudflare Radar
Analytics Radar expands its Routing section with dedicated Overview, RPKI, and Anomalies pages, adding deeper routing stats, a Top 100 ASes ranking, new RPKI validation views, and stacked IPv4 and IPv6 trends for a more organized look at the global routing ecosystem.
Routing
Radar now features an expanded Routing section with dedicated sub-pages, providing a more organized and in-depth view of the global routing ecosystem. This restructuring lays the groundwork for additional routing features and widgets coming in the near future.
The single Routing page has been split into three focused sub-pages:
- Overview — Routing statistics, IP address space trends, BGP announcements, and the new Top 100 ASes ranking.
- RPKI — RPKI validation status, ASPA deployment trends, and per-ASN ASPA provider details.
- Anomalies — BGP route leaks, origin hijacks, and Multi-Origin AS (MOAS) conflicts.
The routing overview now includes a Top 100 ASes table ranking autonomous systems by customer cone size, IPv4 address space, or IPv6 address space. Users can switch between rankings using a segmented control.
The RPKI sub-page introduces a RPKI validation view for per-ASN pages, showing prefixes grouped by RPKI validation status (Valid, Invalid, Unknown) with visibility scores.
The IP address space chart now displays both IPv4 and IPv6 trends stacked vertically and is available on global, country, and AS views.
Check out the Radar routing section to explore the data, and stay tuned for more routing insights coming soon.
Original source Report a problem All of your release notes in one feed
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Mar 26, 2026
- Date parsed from source:Mar 26, 2026
- First seen by Releasebot:Mar 27, 2026
URL Scanner improvements on Cloudflare Radar
Analytics ships URL Scanner improvements with live screenshots, PDF and JSON exports, a redesigned summary layout, clearer file downloads, and richer IP address details for more informative, shareable scan reports.
Radar ships several improvements to the URL Scanner that make scan reports more informative and easier to share:
- Live screenshots — the summary card now includes an option to capture a live screenshot of the scanned URL on demand using the Browser Rendering API.
- Save as PDF — a new button generates a print-optimized document aggregating all tab contents (Summary, Security, Network, Behavior, and Indicators) into a single file.
- Download as JSON — raw scan data is available as a JSON download for programmatic use.
- Redesigned summary layout — page information and security details are now displayed side by side with the screenshot, with a layout that adapts to narrower viewports.
- File downloads — downloads are separated into a dedicated card with expandable rows showing each file's source URL and SHA256 hash.
- Detailed IP address data — the Network tab now includes additional detail per IP address observed during the scan.
Explore these improvements on the Cloudflare Radar URL Scanner.
Original source Report a problem - Mar 25, 2026
- Date parsed from source:Mar 25, 2026
- First seen by Releasebot:Mar 26, 2026
Logpush — More granular timestamps
Analytics adds higher-precision Logpush timestamps, letting users output millisecond or nanosecond formats in the Cloudflare dashboard and API for more accurate log data.
Logpush now supports higher-precision timestamp formats for log output. You can configure jobs to output timestamps at millisecond or nanosecond precision. This is available in both the Logpush UI in the Cloudflare dashboard and the Logpush API.
To use the new formats, set
timestamp_formatin your Logpush job'soutput_options:rfc3339ms—2024-02-17T23:52:01.123Zrfc3339ns—2024-02-17T23:52:01.123456789Z
Default timestamp formats apply unless explicitly set. The dashboard defaults to
rfc3339and the API defaults tounixnano.For more information, refer to the Log output options documentation.
Original source Report a problem - Mar 18, 2026
- Date parsed from source:Mar 18, 2026
- First seen by Releasebot:Mar 18, 2026
Real-time logo match preview
Analytics releases Logo Match Preview, adding pre-save visibility for visual assets to the Brand Protection dashboard. It shows sample matches from recently detected sites, lets users adjust similarity from 75% to 100% with real-time refresh, and review logos before finalizing queries.
We are introducing
Logo Match Preview, bringing the same pre-save visibility to visual assets that was previously only available for string-based queries. This update allows you to fine-tune your brand detection strategy before committing to a live monitor.
What’s new:
- Upload your brand logo and immediately see a sample of potential matches from recently detected sites before finalizing the query
- Adjust your similarity score (from 75% to 100%) and watch the results refresh in real-time to find the balance between broad detection and noise reduction
- Review the specific logos triggered by your current settings to ensure your query is capturing the right level of brand infringement
If you are ready to test your brand assets, go to the
Original source Report a problem
Brand Protection dashboard ↗
to try the new preview tool. - Mar 9, 2026
- Date parsed from source:Mar 9, 2026
- First seen by Releasebot:Mar 13, 2026
New MCP Portal Logs dataset and new fields across multiple Logpush datasets in Cloudflare Logs
Cloudflare expands data visibility with a new MCP Portal Logs dataset and new and updated fields across multiple Logpush datasets, enriching telemetry for HTTP, DNS, firewall events, WARP, and Zero Trust logs. This marks shipped product updates and broader field coverage.
New dataset
- MCP Portal Logs: A new dataset with fields including ClientCountry, ClientIP, ColoCode, Datetime, Error, Method, PortalAUD, PortalID, PromptGetName, ResourceReadURI, ServerAUD, ServerID, ServerResponseDurationMs, ServerURL, SessionID, Success, ToolCallName, UserEmail, and UserID.
New fields in existing datasets
- DEX Application Tests: HTTPRedirectEndMs, HTTPRedirectStartMs, HTTPResponseBody, and HTTPResponseHeaders.
- DEX Device State Events: ExperimentalExtra.
- Firewall Events: FraudUserID.
- Gateway HTTP: AppControlInfo and ApplicationStatuses.
- Gateway DNS: InternalDNSDurationMs.
- HTTP Requests: FraudEmailRisk, FraudUserID, and PayPerCrawlStatus.
- Network Analytics Logs: DNSQueryName, DNSQueryType, and PFPCustomTag.
- WARP Toggle Changes: UserEmail.
- WARP Config Changes: UserEmail.
- Zero Trust Network Session Logs: SNI.
For the complete field definitions for each dataset, refer to Logpush datasets.
Original source Report a problem - Mar 6, 2026
- Date parsed from source:Mar 6, 2026
- First seen by Releasebot:Mar 10, 2026
Workflow steps now expose retry attempt number via step context
Cloudflare Workflows adds per-step retry visibility with ctx.attempt, letting developers see the current attempt during step.do() calls. This enhances logging, observability, progressive backoff, and conditional logic in workflows, with 1-indexed attempt numbers for clearer retry insight.
Cloudflare Workflows retry per-step
Cloudflare Workflows allows you to configure specific retry logic for each step in your workflow execution. Now, you can access which retry attempt is currently executing for calls to step.do() :
await step.do("my-step", async (ctx) => { // ctx.attempt is 1 on first try, 2 on first retry, etc. console.log(`Attempt ${ctx.attempt}`) }) ;You can use the step context for improved logging & observability, progressive backoff, or conditional logic in your workflow definition.
Note that the current attempt number is 1-indexed. For more information on retry behavior, refer to Sleeping and Retrying.
Original source Report a problem - Mar 6, 2026
- Date parsed from source:Mar 6, 2026
- First seen by Releasebot:Mar 9, 2026
Real-time transcription in RealtimeKit now supports 10 languages with regional variants
Cloudflare announces real-time transcription in RealtimeKit now supports 10 languages with regional variants powered by Nova-3 on Workers AI. Transcripts run end-to-end on Cloudflare's network reducing latency. Users set language per meeting and benefit from automatic multilingual detection.
Real-time transcription in RealtimeKit now supports 10 languages with regional variants
in RealtimeKit now supports 10 languages with regional variants, powered by
Deepgram Nova-3 running on
Workers AI .During a meeting, participant audio is routed through
AI Gateway to Nova-3 on Workers AI — so transcription runs on Cloudflare's network end-to-end, reducing latency compared to routing through external speech-to-text services.Set the language when
creating a meeting via
ai_config.transcription.language :{ "ai_config" : { "transcription" : { "language" : "fr" } } }Supported languages include English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian, and Dutch — with regional variants like
en-AU , en-GB , en-IN , en-NZ , es-419 , fr-CA , de-CH , pt-BR , and
pt-PT . Use
multi for automatic multilingual detection.If you are building voice agents or real-time translation workflows, your agent can now transcribe in the caller's language natively — no extra services or routing logic needed.
- Transcription docs
- Nova-3 model page
- Workers AI
- AI Gateway
- Mar 6, 2026
- Date parsed from source:Mar 6, 2026
- First seen by Releasebot:Mar 6, 2026
Region Filtering, AS Traffic Volume, and Navigation Improvements on Cloudflare Radar
Cloudflare Radar introduces region filtering for location-aware pages, a traffic volume view for top ASes and locations, expanded Data Explorer dimensions, and breadcrumb navigation for easier browsing.
Region filtering
All location-aware pages now support filtering by region, including continents, geographic subregions (Middle East ↗, Eastern Asia ↗, , etc.), political regions (EU ↗, African Union ↗), and US Census regions/divisions (for example, New England ↗, US Northeast ↗).
Traffic volume by top autonomous systems and locations
A new traffic volume view shows the top autonomous systems and countries/territories for a given location. This is useful for quickly determining which network providers in a location may be experiencing connectivity issues, or how traffic is distributed across a region.
The new AS and location dimensions have also been added to the Data Explorer ↗ for the HTTP, DNS, and NetFlows datasets. Combined with other available filters, this provides a powerful tool for generating unique insights.
Finally, breadcrumb navigation is now available on most pages, allowing easier navigation between parent and related pages.
Check out these features on Cloudflare Radar ↗ .
Original source Report a problem - Mar 4, 2026
- Date parsed from source:Mar 4, 2026
- First seen by Releasebot:Mar 5, 2026
- Modified by Releasebot:Mar 6, 2026
Browser Rendering: 3x higher REST API request rate
Cloudflare increases REST API rate limits for Workers Paid plans to 10 rps; browser tasks now faster while Bindings limits coming soon.
REST API rate limits for Workers Paid plans
REST API rate limits for Workers Paid plans have been increased from 3 requests per second (180/min) to 10 requests per second (600/min). No action is needed to benefit from the higher limit.
The REST API lets you perform common browser tasks with a single API call, and you can now do it at a higher rate.
If you use the Workers Bindings method, increases to concurrent browser and new browser limits are coming soon. Stay tuned.
For full details, refer to the Browser Rendering limits page.
Original source Report a problem