Application Performance Updates & Release Notes

Follow

98 updates curated from 1 source by the Releasebot Team. Last updated: Nov 4, 2026

Get this feed:
  • Nov 4, 2026
    • Date parsed from source:
      Nov 4, 2026
    • First seen by Releasebot:
      Nov 4, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    Load Balancing, Cloudflare Tunnel, Cloudflare Mesh - Steer Cloudflare One users and private networks to the same endpoint with session affinity and hash steering in private load balancers

    Application Performance adds session affinity for private load balancers, keeping users on a healthy endpoint for stateful apps. Hash steering and IP-cookie affinity work across Cloudflare Tunnel, Mesh, and WAN, with client traffic identified by device or source IP.

    Private load balancers can now keep each user on the same endpoint. This helps with applications that keep session state on a single server.

    How it works

    Cloudflare One Client or Cloudflare WAN site
    Connects to 100.112.0.0
    Private load balancer
    Picks a healthy endpoint based on your steering policy

    Health monitors · Steering · Session affinity

    Pool 1 · Cloudflare Tunnel
    10.0.0.1 · vnet-a

    Pool 2 · Cloudflare Mesh node
    10.1.0.1 · default

    Pool 3 · Cloudflare WAN
    10.2.0.1 · default

    Endpoint = IP address + virtual network

    Two options are available

    • Hash endpoint steering. In the dashboard, set a pool's Endpoint steering to Hash. Each user is mapped to an endpoint within the pool.
    • Session affinity. With the API, set session_affinity to ip_cookie on the load balancer. Each user stays on the same endpoint while it remains healthy and your pools do not change. Refer to Session affinity.

    For traffic from the Cloudflare One Client, Cloudflare identifies the user by their device, so a user stays on the same endpoint even if their IP address changes. For other traffic, such as from a Cloudflare WAN site, Cloudflare uses the source IP address.

    This works for endpoints reached through Cloudflare Tunnel, Cloudflare Mesh, and Cloudflare WAN. Affinity pins the endpoint, not the cloudflared or Mesh replica that carries the traffic.

    To learn how private load balancing fits with your connectors, refer to Load balance private network traffic.

    Original source
  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 6, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    DNS - Cloudflare Services for Private Origins is generally available

    Application Performance reports Cloudflare Services for Private Origins is now generally available, proxying public hostnames to private-network origins over Cloudflare connectivity.

    Cloudflare Services for Private Origins is generally available. Proxy public hostnames to origins in your private network over Cloudflare WAN, Cloudflare Tunnel, or Cloudflare Mesh. Refer to Private origins and the announcement blog post ↗︎.

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Cloudflare and hundreds of other software products.

    Create account
  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 2, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    DNS - New DNS records experience is now the default for everyone

    Application Performance reports Cloudflare’s new DNS records experience is now the default on all plans, replacing the classic page. Users can also change an existing record’s type directly in the dashboard.

    The new DNS records experience announced in May is now the default for all users on all plans, including Enterprise. The classic DNS records page has been retired and is no longer available in the Cloudflare dashboard.

    Changing a record's type

    When the new experience first launched, it did not support changing the type of an existing DNS record. Based on your feedback, we have since added this, so you can now change a record's type (for example, from A to CNAME) directly from the DNS records page. Under the hood, the dashboard uses the batch DNS records endpoint for this.

    Questions or feedback

    If you run into an issue with the new experience, contact your account team or Cloudflare Support.

    Original source
  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 2, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    SSL/TLS - Keyless SSL supports TLS 1.3 with ECDSA certificates

    Application Performance adds TLS 1.3 support for Keyless SSL with ECDSA certificates while keeping private keys on your server.

    Keyless SSL supports TLS 1.3 for ECDSA certificates. When TLS 1.3 is enabled on your zone, visitors connecting to a hostname that serves a Keyless ECDSA certificate negotiate TLS 1.3, and your private keys stay on your own key server.

    Keyless SSL connections that use RSA certificates continue to negotiate up to TLS 1.2.

    For details, refer to the Keyless SSL limitations.

    Original source
  • Oct 29, 2026
    • Date parsed from source:
      Oct 29, 2026
    • First seen by Releasebot:
      Nov 2, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    Data Localization Suite, SSL/TLS - View your data localization settings in one dashboard page

    Application Performance adds a Data Localization Suite Overview to the Cloudflare dashboard, bringing regional traffic, customer metadata, and geo key settings into one read-only view with links to relevant 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
  • Similar to Application Performance with recent updates:

  • Oct 28, 2026
    • Date parsed from source:
      Oct 28, 2026
    • First seen by Releasebot:
      Oct 28, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    China Network, Challenges, Bots - China-native Challenge Pages for the China Network

    Application Performance now serves Turnstile challenge widgets in Mainland China for faster, more reliable Cloudflare China Network challenges.

    Challenge Pages served through the Cloudflare China Network now use Turnstile widgets hosted in Mainland China. This means that visitors in Mainland China can complete challenges faster and more reliably because widgets no longer need to make cross-border requests.

    You do not need to take any action: this change applies automatically when a China Network zone presents a Challenge Page. Visitors served by Cloudflare's global network will continue to receive the global Challenge Page experience.

    For more information, refer to Interstitial Challenge Pages and Cloudflare China Network.

    Original source
  • Oct 26, 2026
    • Date parsed from source:
      Oct 26, 2026
    • First seen by Releasebot:
      Oct 26, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    DNS - Advanced Nameservers use a nameserver type

    Application Performance reports Cloudflare’s DNS settings API now supports the `cloudflare.advanced` nameserver type, replacing `foundation_dns` as the preferred value for new writes while retaining the boolean as a deprecated compatibility alias during the transition.

    Advanced Nameservers API update

    Starting today, the DNS settings endpoints gradually begin to represent Advanced Nameservers with nameservers.type: "cloudflare.advanced". The rollout is expected to take seven days. Previously, the API used the "foundation_dns": true setting for this configuration.

    Before the rollout reaches an account, the endpoints continue to return nameservers.type: "cloudflare.standard" for Advanced Nameservers. The endpoints accept nameservers.type: "cloudflare.advanced" in PATCH requests for entitled accounts throughout the rollout. The zone settings JSON for /zones/{zone_id}/dns_settings is:

    {
      "nameservers": {
        "type": "cloudflare.advanced"
      },
      "foundation_dns": true
    }
    

    Cloudflare will make an equivalent change to /accounts/{account_id}/dns_settings at the same time.

    The foundation_dns boolean remains available as a deprecated compatibility alias in zone and account-default settings. Use nameservers.type: "cloudflare.advanced" for new writes.

    You can continue to read and write foundation_dns during this transition. If a PATCH request includes both values, they must match. The API rejects conflicting values.

    Update clients that treat nameservers.type as a closed enum to recognize the "cloudflare.advanced" value.

    This API update does not change your Foundation DNS subscription or whether Advanced Nameservers are enabled on your zones. It does not require a zone migration.

    In a future API change, Cloudflare will remove the foundation_dns parameter from the API endpoint. After migrating to nameservers.type, remove handling for the boolean from your client.

    Original source
  • Oct 14, 2026
    • Date parsed from source:
      Oct 14, 2026
    • First seen by Releasebot:
      Oct 15, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    DNS - Configure Advanced Custom Nameservers with nameserver sets (beta)

    Application Performance adds beta nameserver sets for Cloudflare Enterprise accounts, enabling reusable custom nameserver configurations with flexible IPv4 and IPv6 addresses and Advanced anycast options for improved resiliency. Legacy custom nameserver sets remain supported.

    Nameserver sets are now available in beta to Enterprise accounts. A nameserver set groups two to five custom nameserver names with Cloudflare-assigned IP addresses. You can assign the set to zones in the same account.

    Enterprise customers using Cloudflare DNS can create Advanced Custom Nameserver sets. These sets distribute addresses across Advanced anycast network groups to improve resiliency.

    Compared to legacy custom_ns sets, modern nameserver sets offer several advantages:

    • Sets are reusable objects. Accounts are no longer limited to 5 numbered sets. Create a set once and assign it to one or more zones in the same account.
    • Custom address counts. Assign each nameserver up to 3 IPv4 and 3 IPv6 addresses. This allows for more flexible setups.
    • Diverse addresses. IPv4 and IPv6 addresses are now both selected from a diverse set of prefixes for increased redundancy.
    • Support for Advanced Custom Nameservers. Set advanced to true to allocate addresses from Advanced anycast network groups, providing the same benefits as Cloudflare branded Advanced nameservers to your custom nameservers.
    • Explicit changes. Sets are immutable, so adding or removing a nameserver name never changes the configuration of zones that already use a set.

    Create a set by sending a POST request to /accounts/{account_id}/dns_settings/nameserver_sets with the following body:

    {
      "advanced": true,
      "ip_set": 1,
      "nameservers": [
        { "name": "ns1.example.com" },
        { "name": "ns2.example.com" },
        { "name": "ns3.example.com" }
      ]
    }
    

    Then, send a PATCH request to /zones/{zone_id}/dns_settings with the returned nameserver set ID:

    {
      "nameservers": {
        "type": "custom",
        "nameserver_set_id": "0123456789abcdef0123456789abcdef"
      }
    }
    

    This configures the zone to use the nameserver set.

    For more information, including other setup steps, refer to Nameserver sets.

    Legacy custom_ns sets remain supported. A single account can use both.

    Original source
  • Oct 13, 2026
    • Date parsed from source:
      Oct 13, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    Cloudflare Web Analytics - Deeper Core Web Vitals Diagnostics: LCP & INP Sub-Part Metrics in Real User Monitoring

    Application Performance now breaks down Core Web Vitals in Web Analytics, revealing LCP and INP phases alongside separate TCP and TLS timings. Users can explore the metrics in dashboards or query percentile data through the GraphQL Analytics 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

    Go to Real user monitoring ↗

    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 6, 2026
    • Date parsed from source:
      Oct 6, 2026
    • First seen by Releasebot:
      Oct 6, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    DNS - Warnings when approaching your DNS records quota

    Application Performance adds DNS records quota warnings in the Cloudflare dashboard

    The DNS records page in the Cloudflare dashboard now shows a warning once you have used 85% of your DNS records quota.

    The warning reflects the quota that applies to you. If your zone has its own quota, the warning shows that zone's usage. If your account uses an account-level DNS records quota, the warning shows your usage across all zones in the account.

    Original source
  • Sep 28, 2026
    • Date parsed from source:
      Sep 28, 2026
    • First seen by Releasebot:
      Sep 29, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    Cache - Invalidate cached content instead of purging it

    Application Performance adds cache invalidation for Cloudflare, letting users mark content stale and revalidate it on the next request instead of purging it. It supports URLs, tags, hostnames, prefixes, and everything, with dashboard and API access.

    You can now invalidate cached content instead of purging it. Invalidation marks matching content as stale. On the next request, Cloudflare revalidates the content with your origin. If your origin responds with 304 Not Modified, Cloudflare reuses the cached content instead of downloading it again.

    Use invalidation to refresh a group of assets when only some of them have changed. For example, invalidate all content that shares a cache tag. Cloudflare reuses unchanged assets instead of downloading them again. This requires your origin to return an ETag or Last-Modified header and support conditional requests.

    Invalidation supports the same selectors as purge: URLs, cache tags, hostnames, URL prefixes, and everything. To invalidate content, send a POST request to the new invalidate_cache endpoint:

    curl --request POST \
    "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/invalidate_cache" \
    --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
    --header "Content-Type: application/json" \
    --data '{"tags":["product-images"]}'
    

    In the dashboard, use Invalidate Cache on the Caching > Configuration page.

    Your cache settings determine whether Cloudflare serves stale content while it revalidates. Cloudflare can also serve invalidated content stale if your origin returns a 5xx error or cannot be reached. To stop serving cached content, purge it instead.

    Invalidation requests count toward the same rate limits as purge requests.

    Purge behavior for Cache Reserve also changes with this release. For details, refer to Cache Reserve purge behavior.

    For more information, refer to Invalidate cached content.

    Original source
  • Sep 28, 2026
    • Date parsed from source:
      Sep 28, 2026
    • First seen by Releasebot:
      Sep 29, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    Cache - Purge now forces a cache miss for Cache Reserve content

    Application Performance adds new Cache Reserve purge behavior, making purges force a cache miss while introducing a separate invalidate cache flow to revalidate content and better manage origin egress, storage costs, and Cache Reserve operations.

    Purge requests now force a cache miss for Cache Reserve content, regardless of purge type. Previously, purging by cache tag, hostname, prefix, or everything marked matching Cache Reserve content for revalidation. Purging by URL already removed content from Cache Reserve and is unchanged.

    This change applies to purge requests from the API and the dashboard. Cache Reserve now handles purges the same way as the edge cache.

    Cost impact

    After a purge, the next request for affected content is a Cache Reserve miss. Your origin must deliver the content in full, even if it has not changed. Cloudflare then writes the content to Cache Reserve again, which is billed as a Class A operation.

    Purging by tag, hostname, prefix, or everything does not delete content from Cache Reserve right away. Matching content continues to incur storage costs until a later request replaces it or its retention period ends.

    If you frequently purge Cache Reserve content by tag, hostname, prefix, or everything, review the effect on your origin egress and Cache Reserve usage.

    Keep revalidating Cache Reserve content

    To keep content in Cache Reserve and revalidate it instead, send the same request to the new invalidate_cache endpoint:

    curl --request POST \
    "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/invalidate_cache" \
    --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
    --header "Content-Type: application/json" \
    --data '{"tags":["product-images"]}'
    

    In the dashboard, use Invalidate Cache on the Caching > Configuration page.

    If your origin responds with 304 Not Modified, Cloudflare reuses the stored content instead of fetching it from your origin again. Compared with purging, invalidation reduces origin egress but not Cache Reserve operations. Updating the stored content after a 304 response is still a Class A operation. Invalidating by URL also updates the stored content when you send the request, which is a Class A operation.

    Unlike the previous purge behavior, invalidation can serve stale content while it revalidates if your cache settings allow it. This applies only to copies in the edge cache, not to content served from Cache Reserve. Cloudflare can also serve invalidated content stale if your origin returns a 5xx error or cannot be reached. For details, refer to Invalidate cached content.

    Original source
  • Sep 14, 2026
    • Date parsed from source:
      Sep 14, 2026
    • First seen by Releasebot:
      Sep 29, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    DNS - Shadowed record warnings are now available for all zones

    Application Performance adds warnings for shadowed DNS records across all zones, helping users spot records that may no longer resolve as expected. It also exposes shadow metadata in DNS API responses for easier troubleshooting and visibility into delegations and glue records.

    Cloudflare now displays warnings for shadowed records in all zones. A record is shadowed when a subdomain delegation gives authority for its name, or a name below it, to another set of nameservers. The record remains present, but your zone is not authoritative for it thus Cloudflare will not respond with it to matching DNS queries. These warnings help you find records that may no longer resolve from the expected zone.

    Shadow metadata is also available in DNS records API responses when you set include_shadow_metadata=true. The metadata identifies the delegating NS records and, when applicable, whether an A or AAAA record is glue. For more information, refer to Shadowed records.

    Original source
  • Sep 2, 2026
    • Date parsed from source:
      Sep 2, 2026
    • First seen by Releasebot:
      Sep 14, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    Cache - Configure Origin Range Requests with the Rulesets API

    Application Performance adds Origin Range Requests support in the Rulesets API for Cache Rules, letting Cloudflare fetch large files from origin in cache-aligned byte ranges and control behavior with on, off, or default settings.

    The Rulesets API now supports Origin Range Requests in Cache Rules.

    This setting lets Cloudflare fetch large files from your origin in cache-aligned byte ranges. Cloudflare may expand a client range and issue several single-range origin requests.

    Set origin_range_requests.mode to on, off, or default for any traffic matched by a Cache Rule.

    To override Cloudflare's default Origin Range Requests behavior, set the mode to off. The following rule turns off generated origin range requests for all traffic without changing cache eligibility:

    {
    "expression": "true",
    "action": "set_cache_settings",
    "action_parameters": {
    "origin_range_requests": {
    "mode": "off"
    }
    }
    }
    

    Origin Range Requests do not make otherwise ineligible content cacheable. If your origin ignores Range and returns a complete 200 OK, Cloudflare can use the response but must download the complete file. Origins should honor Accept-Encoding: identity and return consistent, unencoded partial responses.

    For configuration details and mode behavior, refer to Origin Range Requests in Cache Rules. For client responses and the complete origin contract, refer to Range request behavior.

    Original source
  • Aug 31, 2026
    • Date parsed from source:
      Aug 31, 2026
    • First seen by Releasebot:
      Sep 11, 2026
    Cloudflare logo

    Application Performance by Cloudflare

    Load Balancing - Load Balancing now supports pool sets

    Application Performance adds API support for Cloudflare Load Balancing pool sets, enabling location-specific routing, steering policies, weights, and fallback behavior by data center, country, or region. It also supports active-active distribution, regional failover, and fixed HTTP responses for proxied traffic.

    Cloudflare Load Balancing now supports pool sets through the API. Pool sets combine geographic matching with location-specific traffic steering. One load balancer can now use different routing behavior for different locations.

    Each pool set can match a Cloudflare data center, country, or region. It then supplies the candidate pools and can apply its own steering policy, pool weights, and fallback pool. Cloudflare evaluates pool sets in array order and applies the first matching pool set.

    For example, this pool set uses Dynamic Latency steering for traffic from Germany:

    {
      "pool_sets": [
        {
          "name": "germany-lowest-latency",
          "match": { "topology": { "countries": ["DE"] } },
          "overrides": {
            "pools": [
              "0930eec54a4c7ae6616985b79f678210",
              "c8b4f5a6d7e84910a2b3c4d5e6f70819"
            ],
            "steering_policy": "dynamic_latency"
          }
        }
      ]
    }
    

    Use pool sets for active-active traffic distribution, location-specific failover, and regional routing policies. For proxied traffic, a pool set can also return a fixed HTTP response instead of selecting a pool.

    For configuration details and more examples, refer to Pool sets.

    Original source
Releasebot

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.