Author: guillaume

You can now configure Workers to run close to infrastructure in legacy cloud regions to minimize latency to existing services and databases. This is most useful when your Worker makes multiple round trips.

To set a placement hint, set the placement.region property in your Wrangler configuration file:

• wrangler.jsonc

  {
    "placement": {
      "region": "aws:us-east-1",
    },
  }

• wrangler.toml

  [placement]
  region = "aws:us-east-1"

Placement hints support Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure region identifiers. Workers run in the Cloudflare data center with the lowest latency to the specified cloud region.

If your existing infrastructure is not in these cloud providers, expose it to placement probes with placement.host for layer 4 checks or placement.hostname for layer 7 checks. These probes are designed to locate single-homed infrastructure and are not suitable for anycasted or multicasted resources.

• wrangler.jsonc

  {
    "placement": {
      "host": "my_database_host.com:5432",
    },
  }

• wrangler.toml

  [placement]
  host = "my_database_host.com:5432"

• wrangler.jsonc

  {
    "placement": {
      "hostname": "my_api_server.com",
    },
  }

• wrangler.toml

  [placement]
  hostname = "my_api_server.com"

This is an extension of Smart Placement, which automatically places your Workers closer to back-end APIs based on measured latency. When you do not know the location of your back-end APIs or have multiple back-end APIs, set mode: "smart":

• wrangler.jsonc

  {
    "placement": {
      "mode": "smart",
    },
  }

• wrangler.toml

  [placement]
  mode = "smart"

AI Search now includes path filtering for both website and R2 data sources. You can now control which content gets indexed by defining include and exclude rules for paths.

By controlling what gets indexed, you can improve the relevance and quality of your search results. You can also use path filtering to split a single data source across multiple AI Search instances for specialized search experiences.

Path filtering uses micromatch patterns, so you can use * to match within a directory and ** to match across directories.

Configure path filters when creating a new instance or update them anytime from Settings. Check out path filtering to learn more.

AI Search now includes path filtering for both website and R2 data sources. You can now control which content gets indexed by defining include and exclude rules for paths.

By controlling what gets indexed, you can improve the relevance and quality of your search results. You can also use path filtering to split a single data source across multiple AI Search instances for specialized search experiences.

Path filtering uses micromatch patterns, so you can use * to match within a directory and ** to match across directories.

Configure path filters when creating a new instance or update them anytime from Settings. Check out path filtering to learn more.

You can now create AI Search instances programmatically using the API. For example, use the API to create instances for each customer in a multi-tenant application or manage AI Search alongside your other infrastructure.

If you have created an AI Search instance via the dashboard before, you already have a service API token registered and can start creating instances programmatically right away. If not, follow the API guide to set up your first instance.

For example, you can now create separate search instances for each language on your website:

for lang in en fr es de; do
  curl -X POST "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/ai-search/instances" 
    -H "Authorization: Bearer $API_TOKEN" 
    -H "Content-Type: application/json" 
    --data '{
      "id": "docs-'"$lang"'",
      "type": "web-crawler",
      "source": "example.com",
      "source_params": {
        "path_include": ["**/'"$lang"'/**"]
      }
    }'
done

Refer to the REST API reference for additional configuration options.

AI Search now includes path filtering for both website and R2 data sources. You can now control which content gets indexed by defining include and exclude rules for paths.

By controlling what gets indexed, you can improve the relevance and quality of your search results. You can also use path filtering to split a single data source across multiple AI Search instances for specialized search experiences.

Path filtering uses micromatch patterns, so you can use * to match within a directory and ** to match across directories.

Configure path filters when creating a new instance or update them anytime from Settings. Check out path filtering to learn more.

AI Search now includes path filtering for both website and R2 data sources. You can now control which content gets indexed by defining include and exclude rules for paths.

By controlling what gets indexed, you can improve the relevance and quality of your search results. You can also use path filtering to split a single data source across multiple AI Search instances for specialized search experiences.

Path filtering uses micromatch patterns, so you can use * to match within a directory and ** to match across directories.

Configure path filters when creating a new instance or update them anytime from Settings. Check out path filtering to learn more.

AI Search now includes path filtering for both website and R2 data sources. You can now control which content gets indexed by defining include and exclude rules for paths.

By controlling what gets indexed, you can improve the relevance and quality of your search results. You can also use path filtering to split a single data source across multiple AI Search instances for specialized search experiences.

Path filtering uses micromatch patterns, so you can use * to match within a directory and ** to match across directories.

Configure path filters when creating a new instance or update them anytime from Settings. Check out path filtering to learn more.

AI Search now includes path filtering for both website and R2 data sources. You can now control which content gets indexed by defining include and exclude rules for paths.

By controlling what gets indexed, you can improve the relevance and quality of your search results. You can also use path filtering to split a single data source across multiple AI Search instances for specialized search experiences.

Path filtering uses micromatch patterns, so you can use * to match within a directory and ** to match across directories.

Configure path filters when creating a new instance or update them anytime from Settings. Check out path filtering to learn more.

The Network Services menu structure in Cloudflare’s dashboard has been updated to reflect solutions and capabilities instead of product names. This will make it easier for you to find what you need and better reflects how our services work together.

Your existing configurations will remain the same, and you will have access to all of the same features and functionality.

The changes visible in your dashboard may vary based on the products you use. Overall, changes relate to Magic Transit, Magic WAN, and Magic Firewall.

Summary of changes:

• A new ‘Overview’ page provides access to the most common tasks across Magic Transit and Magic WAN.
• Product names have been removed from top-level navigation.
• Magic Transit and Magic WAN configuration is now organized under ‘Routes’ and ‘Connectors’. For example, you will find IP Prefixes under ‘Routes’, and your GRE/IPsec Tunnels under ‘Connectors.’
• Magic Firewall policies are now called ‘Firewall Policies.’
• Magic WAN Connectors and Connector On-Ramps are now referenced in the dashboard as ‘Appliances’ and ‘Appliance profiles.’ They can be found under ‘Connectors > Appliances.’
• Network analytics, network health, and real-time analytics are now available under ‘Insights.’
• Packet Captures are found under ‘Insights > Diagnostics.’
• You can manage your Sites from ‘Insights > Network health.‘
• You can find Magic Network Monitoring under ‘Insights > Network flow.’

If you would like to provide feedback, please use the form in the email sent on January 7th, 2026, titled ‘[FYI] Upcoming Network Services Dashboard Navigation Update.’

We have made it easier to validate connectivity when deploying WARP Connector as part of your software-defined private network.

You can now ping the WARP Connector host directly on its LAN IP address immediately after installation. This provides a fast, familiar way to confirm that the Connector is online and reachable within your network before testing access to downstream services.

Starting with version 2025.10.186.0, WARP Connector responds to traffic addressed to its own LAN IP, giving you immediate visibility into Connector reachability.

Learn more about deploying WARP Connector and building private network connectivity with Cloudflare One.