Skip to content

Changelog

New updates and improvements at Cloudflare.

Cloudflare One
hero image
  1. You can now use CASB webhooks in Cloudflare One to send posture finding instances to external systems such as chat platforms, ticketing systems, SIEMs, SOAR tools, and custom automation services.

    This gives security teams a simple way to route CASB posture findings into the tools and workflows they already use for triage and response.

    To get started, go to Integrations > Webhooks in the Cloudflare One dashboard to create a webhook destination. After you configure a webhook, open a posture finding instance and select Send webhook to send it.

    Key capabilities

    • Flexible authentication — Configure destinations using None, Basic Auth, Bearer Auth, Static Headers, or HMAC-Signing.
    • Built-in testing — Use Test delivery to send a test request before sending a live finding instance.
    • Posture finding workflows — Send posture finding instances directly from the finding details workflow in Cloud & SaaS findings.
    • HTTPS destinations — Configure webhook destinations with public https:// URLs.

    Learn more

    CASB webhooks are now available in Cloudflare One.

  1. Cloudflare One's User Risk Scoring now incorporates direct signals from Gateway DNS traffic patterns. This update allows security teams to automatically elevate a user's risk score when they visit high-risk or malicious domains, providing a more holistic view of internal threats.

    Why this matters

    Browsing activity is a primary indicator of potential compromise. By tying Gateway DNS logs to specific users, administrators can now flag individuals interacting with:

    • Security threats: Domains associated with malware, phishing, or command-and-control (C2) centers.
    • High-risk content: Categories such as questionable content or violence that may violate corporate compliance.

    Even if a Gateway policy is set to Block the traffic, the interaction is still captured as a "hit" to ensure the user's risk profile reflects the attempted activity.

    New risk behaviors

    Two new behaviors are now available in the dashboard:

    • Suspicious Security Domain Visited: Triggers when a user visits a domain in the security threats or security risk categories.
    • High risk domain visited: Triggers when a user visits domains categorized as questionable content, violence, or CIPA.

    To learn more and get started, refer to the User Risk Scoring documentation.

  1. A new GA release for the Windows Cloudflare One Client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements.

    The next stable release for Windows will introduce the new Cloudflare One Client UI, providing a cleaner and more intuitive design as well as easier access to common actions and information.

    Changes and improvements

    • Fixed an issue causing Windows client tunnel interface initialization failure which prevented clients from establishing a tunnel for connection.
    • Consumer-only CLI commands are now clearly distinguished from Zero Trust commands.
    • Added detailed QUIC connection metrics to diagnostic logs for better troubleshooting.
    • Added monitoring for tunnel statistics collection timeouts.
    • Switched tunnel congestion control algorithm for local proxy mode to Cubic for improved reliability across platforms.
    • Fixed packet capture failing on tunnel interface when the tunnel interface is renamed by SCCM VPN boundary support.
    • Fixed unnecessary registration deletion caused by RDP connections in multi-user mode.
    • Fixed increased tunnel interface start-up time due to a race between duplicate address detection (DAD) and disabling NetBT.
    • Fixed tunnel failing to connect when the system DNS search list contains unexpected characters.
    • Empty MDM files are now rejected instead of being incorrectly accepted as a single MDM config.
    • Fixed an issue in local proxy mode where the client could become unresponsive due to upstream connection timeouts.
    • Fixed an issue where the emergency disconnect status of a prior organization persisted after a switch to a different organization.
    • Fixed initiating managed network detections checks when no network is available, which caused device profile flapping.
    • Fixed an issue where degraded Windows Management Instrumentation (WMI) state could put the client in a failed connection state loop during initialization.

    Known issues

    • For Windows 11 24H2 users, Microsoft has confirmed a regression that may lead to performance issues like mouse lag, audio cracking, or other slowdowns. Cloudflare recommends users experiencing these issues upgrade to a minimum Windows 11 24H2 version KB5062553 or higher for resolution. This warning will be omitted from future release notes. This Windows update was released in July 2025.

    • Devices with KB5055523 installed may receive a warning about Win32/ClickFix.ABA being present in the installer. To resolve this false positive, update Microsoft Security Intelligence to version 1.429.19.0 or later. This warning will be omitted from future release notes. This Microsoft Security Intelligence update was released in May 2025.

    • DNS resolution may be broken when the following conditions are all true:

      • The client is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
      • A custom DNS server address is configured on the primary network adapter.
      • The custom DNS server address on the primary network adapter is changed while the client is connected.

      To work around this issue, reconnect the client by selecting Disconnect and then Connect in the client user interface.

  1. Cloudflare One Appliance now supports Link Aggregation Control Protocol (LACP), allowing you to bundle up to six physical LAN ports into a single logical interface. Link aggregation increases available bandwidth and eliminates single points of failure on the LAN side of the appliance.

    This feature is available in beta on physical appliance hardware with the latest OS. No entitlement is required.

    To configure a Link Aggregation Group, refer to Configure link aggregation groups.

  1. Cloudflare Email Security now supports DANE (DNS-based Authentication of Named Entities) for MX deployments. This enhancement strengthens email transport security by enabling DNSSEC-backed certificate verification for our regional MX records.

    • Regional MX hostnames now publish DANE TLSA records backed by DNSSEC, enabling DANE-capable SMTP senders to cryptographically validate certificate identities before establishing TLS connections—moving beyond opportunistic encryption to verified encrypted delivery.
    • DANE support is automatically available for all customers using regional MX deployments. No additional configuration is required; DANE-capable mail infrastructure will automatically validate MX certificates using the published records.

    This applies to all Email Security packages:

    • Advantage
    • Enterprise
    • Enterprise + PhishGuard
  1. A new GA release for the macOS Cloudflare One Client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements.

    The next stable release for macOS will introduce the new Cloudflare One Client UI, providing a cleaner and more intuitive design as well as easier access to common actions and information.

    Changes and improvements

    • Empty MDM files are now rejected instead of being incorrectly accepted as a single MDM config.
    • Fixed an issue in local proxy mode where the client could become unresponsive due to upstream connection timeouts.
    • Fixed an issue where the emergency disconnect status of a prior organization persisted after a switch to a different organization.
    • Consumer-only CLI commands are now clearly distinguished from Zero Trust commands.
    • Added detailed QUIC connection metrics to diagnostic logs for better troubleshooting.
    • Added monitoring for tunnel statistics collection timeouts.
    • Switched tunnel congestion control algorithm for local proxy mode to Cubic for improved reliability across platforms.
    • Fixed initiating managed network detections checks when no network is available, which caused device profile flapping.
  1. A new GA release for the Linux Cloudflare One Client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements.

    The next stable release for Linux will introduce the new Cloudflare One Client UI, providing a cleaner and more intuitive design as well as easier access to common actions and information.

    Changes and improvements

    • Empty MDM files are now rejected instead of being incorrectly accepted as a single MDM config.
    • Fixed an issue in local proxy mode where the client could become unresponsive due to upstream connection timeouts.
    • Fixed an issue where the emergency disconnect status of a prior organization persisted after a switch to a different organization.
    • Consumer-only CLI commands are now clearly distinguished from Zero Trust commands.
    • Added detailed QUIC connection metrics to diagnostic logs for better troubleshooting.
    • Added monitoring for tunnel statistics collection timeouts.
    • Switched tunnel congestion control algorithm for local proxy mode to Cubic for improved reliability across platforms.
    • Fixed initiating managed network detections checks when no network is available, which caused device profile flapping.
  1. Access authentication logs and Gateway activity logs (DNS, Network, and HTTP) now feature a refreshed user interface that gives you more flexibility when viewing and analyzing your logs.

    Screenshot of the new logs UI showing DNS query logs with customizable columns and filtering options

    The updated UI includes:

    • Filter by field - Select any field value to add it as a filter and narrow down your results.
    • Customizable fields - Choose which fields to display in the log table. Querying for fewer fields improves log loading performance.
    • View details - Select a timestamp to view the full details of a log entry.
    • Switch to classic view - Return to the previous log viewer interface if needed.

    For more information, refer to Access authentication logs and Gateway activity logs.

  1. Cloudflare Gateway now supports OIDC Claims as a selector in Firewall, Resolver, and Egress policies. Administrators can use custom OIDC claims from their identity provider to build fine-grained, identity-based traffic policies across all Gateway policy types.

    With this update, you can:

    • Filter traffic in DNS, HTTP, and Network firewall policies based on OIDC claim values.
    • Apply custom resolver policies to route DNS queries to specific resolvers depending on a user's OIDC claims.
    • Control egress policies to assign dedicated egress IPs based on OIDC claim attributes.

    For example, you can create a policy that routes traffic differently for users with department=engineering in their OIDC claims, or restrict access to certain destinations based on a user's role claim.

    To get started, configure custom OIDC claims on your identity provider and use the OIDC Claims selector in the Gateway policy builder.

    For more information, refer to Identity-based policies.

  1. MCP server portals can now route traffic through Cloudflare Gateway for richer HTTP request logging and data loss prevention (DLP) scanning.

    When Gateway routing is turned on, portal traffic appears in your Gateway HTTP logs. You can create Gateway HTTP policies with DLP profiles to detect and block sensitive data sent to upstream MCP servers.

    To enable Gateway routing, go to Access controls > AI controls, edit the portal, and turn on Route traffic through Cloudflare Gateway under Basic information.

    Route MCP server portal traffic through Cloudflare Gateway

    For more details, refer to Route traffic through Gateway.

  1. In the Cloudflare One dashboard, the overview page for a specific Cloudflare Tunnel now shows all replicas of that tunnel and supports streaming logs from multiple replicas at once.

    View replicas and stream logs from multiple connectors

    Previously, you could only stream logs from one replica at a time. With this update:

    • Replicas on the tunnel overview — All active replicas for the selected tunnel now appear on that tunnel's overview page under Connectors. Select any replica to stream its logs.
    • Multi-connector log streaming — Stream logs from multiple replicas simultaneously, making it easier to correlate events across your infrastructure during debugging or incident response. To try it out, log in to Cloudflare One and go to Networks > Connectors > Cloudflare Tunnels. Select View logs next to the tunnel you want to monitor.

    For more information, refer to Tunnel log streams and Deploy replicas.

  1. A new Beta release for the macOS WARP client is now available on the beta releases downloads page.

    This release contains minor fixes and introduces a brand new visual style for the client interface. The new Cloudflare One Client interface changes connectivity management from a toggle to a button and brings useful connectivity settings to the home screen. The redesign also introduces a collapsible navigation bar. When expanded, more client information can be accessed including connectivity, settings, and device profile information. If you have any feedback or questions, visit the Cloudflare Community forum and let us know.

    Changes and improvements

    • Empty MDM files are now rejected instead of being incorrectly accepted as a single MDM config.
    • Fixed an issue in proxy mode where the client could become unresponsive due to upstream connection timeouts.
    • Fixed emergency disconnect state from a previous organization incorrectly persisting after switching organizations.
    • Consumer-only CLI commands are now clearly distinguished from Zero Trust commands.
    • Added detailed QUIC connection metrics to diagnostic logs for better troubleshooting.
    • Added monitoring for tunnel statistics collection timeouts.
    • Switched tunnel congestion control algorithm to Cubic for improved reliability across platforms.
    • Fixed initiating managed network detection checks when no network is available, which caused device profile flapping.

    Known issues

    • The client may become stuck in a Connecting state. To resolve this issue, reconnect the client by selecting Disconnect and then Connect in the client user interface. Alternatively, change the client's operation mode.
    • The client may display an empty white screen upon the device waking from sleep. To resolve this issue, exit and then open the client to re-launch it.
    • Canceling login during a single MDM configuration setup results in an empty page with no way to resume authentication. To work around this issue, exit and relaunch the client.
  1. A new Beta release for the Windows WARP client is now available on the beta releases downloads page.

    This release contains minor fixes and introduces a brand new visual style for the client interface. The new Cloudflare One Client interface changes connectivity management from a toggle to a button and brings useful connectivity settings to the home screen. The redesign also introduces a collapsible navigation bar. When expanded, more client information can be accessed including connectivity, settings, and device profile information. If you have any feedback or questions, visit the Cloudflare Community forum and let us know.

    Changes and improvements

    • Consumer-only CLI commands are now clearly distinguished from Zero Trust commands.
    • Added detailed QUIC connection metrics to diagnostic logs for better troubleshooting.
    • Added monitoring for tunnel statistics collection timeouts.
    • Switched tunnel congestion control algorithm to Cubic for improved reliability across platforms.
    • Fixed packet capture failing on tunnel interface when the tunnel interface is renamed by SCCM VPN boundary support.
    • Fixed unnecessary registration deletion caused by RDP connections in multi-user mode.
    • Fixed increased tunnel interface start-up time due to a race between duplicate address detection (DAD) and disabling NetBT.
    • Fixed tunnel failing to connect when the system DNS search list contains unexpected characters.
    • Empty MDM files are now rejected instead of being incorrectly accepted as a single MDM config.
    • Fixed an issue in proxy mode where the client could become unresponsive due to upstream connection timeouts.
    • Fixed emergency disconnect state from a previous organization incorrectly persisting after switching organizations.
    • Fixed initiating managed network detection checks when no network is available, which caused device profile flapping.

    Known issues

    • The client may unexpectedly terminate during captive portal login. To work around this issue, use a web browser to authenticate with the captive portal and then re-launch the client.
    • An error indicating that Microsoft Edge can't read and write to its data directory may be displayed during captive portal login; this error is benign and can be dismissed.
    • The client may become stuck in a Connecting state. To resolve this issue, reconnect the client by selecting Disconnect and then Connect in the client user interface. Alternatively, change the client's operation mode.
    • The client may display an empty white screen upon the device waking from sleep. To resolve this issue, exit and then open the client to re-launch it.
    • Canceling login during a single MDM configuration setup results in an empty page with no way to resume authentication. To work around this issue, exit and relaunch the client.
    • For Windows 11 24H2 users, Microsoft has confirmed a regression that may lead to performance issues like mouse lag, audio cracking, or other slowdowns. Cloudflare recommends users experiencing these issues upgrade to a minimum Windows 11 24H2 version KB5062553 or higher for resolution.
    • Devices with KB5055523 installed may receive a warning about Win32/ClickFix.ABA being present in the installer. To resolve this false positive, update Microsoft Security Intelligence to version 1.429.19.0 or later. This warning will be omitted from future release notes. This Microsoft Security Intelligence update was released in May 2025.
    • DNS resolution may be broken when the following conditions are all true:
      • The client is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
      • A custom DNS server address is configured on the primary network adapter.
      • The custom DNS server address on the primary network adapter is changed while the client is connected. To work around this issue, reconnect the client by selecting Disconnect and then Connect in the client user interface.
  1. You can now use user risk scores in your Access policies. The new User Risk Score selector allows you to create Access policies that respond to user behavior patterns detected by Cloudflare's risk scoring system, including impossible travel, high DLP policy matches, and more.

    For more information, refer to Use risk scores in Access policies.

  1. The Gateway Authorization Proxy and PAC file hosting are now in open beta for all plan types.

    Previously, proxy endpoints relied on static source IP addresses to authorize traffic, providing no user-level identity in logs or policies. The new authorization proxy replaces IP-based authorization with Cloudflare Access authentication, verifying who a user is before applying Gateway filtering without installing the WARP client.

    This is ideal for environments where you cannot deploy a device client, such as virtual desktops (VDI), mergers and acquisitions, or compliance-restricted endpoints.

    Key capabilities

    • Identity-aware proxy traffic — Users authenticate through your identity provider (Okta, Microsoft Entra ID, Google Workspace, and others) via Cloudflare Access. Logs now show exactly which user accessed which site, and you can write identity-based policies like "only the Finance team can access this accounting tool."
    • Multiple identity providers — Display one or multiple login methods simultaneously, giving flexibility for organizations managing users across different identity systems.
    • Cloudflare-hosted PAC files — Create and host PAC files directly in Cloudflare One with pre-configured templates for Okta and Azure, hosted at https://pac.cloudflare-gateway.com/<account-id>/<slug> on Cloudflare's global network.
    • Simplified billing — Each user occupies a seat, exactly like they do with the Cloudflare One Client. No new metrics to track.

    Get started

    1. In Cloudflare One, go to Networks > Resolvers & Proxies > Proxy endpoints.
    2. Create an authorization proxy endpoint and configure Access policies.
    3. Create a hosted PAC file or write your own.
    4. Configure browsers to use the PAC file URL.
    5. Install the Cloudflare certificate for HTTPS inspection.

    For more details, refer to the proxy endpoints documentation and the announcement blog post.

  1. You can now copy Cloudflare One resources as JSON or as a ready-to-use API POST request directly from the dashboard. This makes it simple to transition workflows into API calls, automation scripts, or infrastructure-as-code pipelines.

    To use this feature, click the overflow menu (⋮) on any supported resource and select Copy as JSON or Copy as POST request. The copied output includes only the fields present on your resource, giving you a clean and minimal starting point for your own API calls.

    Initially supported resources:

    • Access applications
    • Access policies
    • Gateway policies
    • Resolver policies
    • Service tokens
    • Identity providers

    We will continue to add support for more resources throughout 2026.

  1. You can now configure clipboard controls for browser-based RDP with Cloudflare Access. Clipboard controls allow administrators to restrict whether users can copy or paste text between their local machine and the remote Windows server.

    Enable users to copy and paste content from their local machine to remote RDP sessions in the Cloudflare One dashboard

    This feature is useful for organizations that support bring-your-own-device (BYOD) policies or third-party contractors using unmanaged devices. By restricting clipboard access, you can prevent sensitive data from being transferred out of the remote session to a user's personal device.

    Configuration options

    Clipboard controls are configured per policy within your Access application. For each policy, you can independently allow or deny:

    • Copy from local client to remote RDP session — Users can copy/paste text from their local machine into the browser-based RDP session.
    • Copy from remote RDP session to local client — Users can copy/paste text from the browser-based RDP session to their local machine.

    By default, both directions are denied for new policies. For existing Access applications created before this feature was available, clipboard access remains enabled to preserve backwards compatibility.

    When a user attempts a restricted clipboard action, the clipboard content is replaced with an error message informing them that the action is not allowed.

    For more information, refer to Clipboard controls for browser-based RDP.

  1. MCP server portals now supports Logpush integration. You can automatically export MCP server portal activity logs to third-party storage destinations or security information and event management (SIEM) tools for analysis and auditing.

    Available log fields

    The MCP server portal logs dataset includes fields such as:

    • Datetime — Timestamp of the request
    • PortalID / PortalAUD — Portal identifiers
    • ServerID / ServerURL — Upstream MCP server details
    • Method — JSON-RPC method (for example, tools/call, prompts/get, resources/read)
    • ToolCallName / PromptGetName / ResourceReadURI — Method-specific identifiers
    • UserID / UserEmail — Authenticated user information
    • Success / Error — Request outcome
    • ServerResponseDurationMs — Response time from upstream server

    For the complete field reference, refer to MCP portal logs.

    Set up Logpush

    To configure Logpush for MCP server portal logs, refer to Logpush integration.

  1. Gateway Protocol Detection now supports seven additional protocols in beta:

    ProtocolNotes
    IMAPInternet Message Access Protocol — email retrieval
    POP3Post Office Protocol v3 — email retrieval
    SMTPSimple Mail Transfer Protocol — email sending
    MYSQLMySQL database wire protocol
    RSYNC-DAEMONrsync daemon protocol
    LDAPLightweight Directory Access Protocol
    NTPNetwork Time Protocol

    These protocols join the existing set of detected protocols (HTTP, HTTP2, SSH, TLS, DCERPC, MQTT, and TPKT) and can be used with the Detected Protocol selector in Network policies to identify and filter traffic based on the application-layer protocol, without relying on port-based identification.

    If protocol detection is enabled on your account, these protocols will automatically be logged when detected in your Gateway network traffic.

    For more information on using Protocol Detection, refer to the Protocol detection documentation.

  1. A new GA release for the Windows WARP client is now available on the stable releases downloads page.

    This release contains minor fixes, improvements, and new features.

    Changes and improvements

    • Improvements to multi-user mode. Fixed an issue where when switching from a pre-login registration to a user registration, Mobile Device Management (MDM) configuration association could be lost.
    • Added a new feature to manage NetBIOS over TCP/IP functionality on the Windows client. NetBIOS over TCP/IP on the Windows client is now disabled by default and can be enabled in device profile settings.
    • Fixed an issue causing failure of the local network exclusion feature when configured with a timeout of 0.
    • Improvement for the Windows client certificate posture check to ensure logged results are from checks that run once users log in.
    • Improvement for more accurate reporting of device colocation information in the Cloudflare One dashboard.
    • Fixed an issue where misconfigured DEX HTTP tests prevented new registrations.
    • Fixed an issue causing DNS requests to fail with clients in Traffic and DNS mode.
    • Improved service shutdown behavior in cases where the daemon is unresponsive.

    Known issues

    • For Windows 11 24H2 users, Microsoft has confirmed a regression that may lead to performance issues like mouse lag, audio cracking, or other slowdowns. Cloudflare recommends users experiencing these issues upgrade to a minimum Windows 11 24H2 KB5062553 or higher for resolution.

    • Devices with KB5055523 installed may receive a warning about Win32/ClickFix.ABA being present in the installer. To resolve this false positive, update Microsoft Security Intelligence to version 1.429.19.0 or later.

    • DNS resolution may be broken when the following conditions are all true:

      • WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
      • A custom DNS server address is configured on the primary network adapter.
      • The custom DNS server address on the primary network adapter is changed while WARP is connected.

      To work around this issue, reconnect the WARP client by toggling off and back on.

  1. A new GA release for the macOS WARP client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements.

    Changes and improvements

    • Fixed an issue causing failure of the local network exclusion feature when configured with a timeout of 0.
    • Improvement for more accurate reporting of device colocation information in the Cloudflare One dashboard.
    • Fixed an issue with DNS server configuration failures that caused tunnel connection delays.
    • Fixed an issue where misconfigured DEX HTTP tests prevented new registrations.
    • Fixed an issue causing DNS requests to fail with clients in Traffic and DNS mode.
  1. A new GA release for the Linux WARP client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements.

    WARP client version 2025.8.779.0 introduced an updated public key for Linux packages. The public key must be updated if it was installed before September 12, 2025 to ensure the repository remains functional after December 4, 2025. Instructions to make this update are available at pkg.cloudflareclient.com.

    Changes and improvements

    • Fixed an issue causing failure of the local network exclusion feature when configured with a timeout of 0.
    • Improvement for more accurate reporting of device colocation information in the Cloudflare One dashboard.
    • Fixed an issue where misconfigured DEX HTTP tests prevented new registrations.
    • Fixed issues causing DNS requests to fail with clients in Traffic and DNS mode or DNS only mode.
  1. You can now easily understand your SaaS security posture findings and why they were detected with Cloudy Summaries in CASB. This feature integrates Cloudflare's Cloudy AI directly into your CASB Posture Findings to automatically generate clear, plain-language summaries of complex security misconfigurations, third-party app risks, and data exposures.

    This allows security teams and IT administrators to drastically reduce triage time by immediately understanding the context, potential impact, and necessary remediation steps for any given finding—without needing to be an expert in every connected SaaS application.

    To view a summary, simply navigate to your Posture Findings in the Cloudflare One dashboard (under Cloud and SaaS findings) and open the finding details of a specific instance of a Finding.

    Cloudy Summaries are supported on all available integrations, including Microsoft 365, Google Workspace, Salesforce, GitHub, AWS, Slack, and Dropbox. See the full list of supported integrations here.

    Key capabilities

    • Contextual explanations — Quickly understand the specifics of a finding with plain-language summaries detailing exactly what was detected, from publicly shared sensitive files to risky third-party app scopes.
    • Clear risk assessment — Instantly grasp the potential security impact of the finding, such as data breach risks, unauthorized account access, or email spoofing vulnerabilities.
    • Actionable guidance — Get clear recommendations and next steps on how to effectively remediate the issue and secure your environment.
    • Built-in feedback — Help improve future AI summarization accuracy by submitting feedback directly using the thumbs-up and thumbs-down buttons.

    Learn more

    Cloudy Summaries in CASB are available to all Cloudflare CASB users today.

  1. Cloudflare Tunnel is now available in the main Cloudflare Dashboard at Networking > Tunnels, bringing first-class Tunnel management to developers using Tunnel for securing origin servers.

    Manage Tunnels in the Core Dashboard

    This new experience provides everything you need to manage Tunnels for public applications, including:

    Choose the right dashboard for your use case

    Core Dashboard: Navigate to Networking > Tunnels to manage Tunnels for:

    Cloudflare One Dashboard: Navigate to Zero Trust > Networks > Connectors to manage Tunnels for:

    Both dashboards provide complete Tunnel management capabilities — choose based on your primary workflow.

    Get started

    New to Tunnel? Learn how to get started with Cloudflare Tunnel or explore advanced use cases like securing SSH servers or running Tunnels in Kubernetes.

  1. Digital Experience Monitoring (DEX) provides visibility into WARP device connectivity and performance to any internal or external application.

    Now, all DEX logs are fully compatible with Cloudflare's Customer Metadata Boundary (CMB) setting for the 'EU' (European Union), which ensures that DEX logs will not be stored outside the 'EU' when the option is configured.

    If a Cloudflare One customer using DEX enables CMB 'EU', they will not see any DEX data in the Cloudflare One dashboard. Customers can ingest DEX data via LogPush, and build their own analytics and dashboards.

    If a customer enables CMB in their account, they will see the following message in the Digital Experience dashboard: "DEX data is unavailable because Customer Metadata Boundary configuration is on. Use Cloudflare LogPush to export DEX datasets."

    Digital Experience Monitoring message when Customer Metadata Boundary for the EU is enabled