---
title: Breakout traffic · Cloudflare Magic WAN docs
description: Breakout traffic allows you to define which applications should
  bypass Cloudflare's security filtering.
lastUpdated: 2025-11-04T17:07:51.000Z
chatbotDeprioritize: false
source_url:
  html: https://developers.cloudflare.com/magic-wan/configuration/connector/network-options/application-based-policies/breakout-traffic/
  md: https://developers.cloudflare.com/magic-wan/configuration/connector/network-options/application-based-policies/breakout-traffic/index.md
---

Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Magic WAN Connector can detect. This can take several minutes.

Warning

Breakout traffic will not work for applications that use DNS-over-HTTPS.

```mermaid
		flowchart LR
		accTitle: In this example, the applications go directly to the Internet, skipping Cloudflare's security. filtering
		a(Magic WAN Connector) --> b(Cloudflare) -->|Filtered traffic|c(Internet)

		a-- Breakout traffic ---d(Application1) & e(Application2) --> c

		classDef orange fill:#f48120,color: black
		class a,b orange
		
```

*In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet*

A note on security

We recommend [routing](https://www.cloudflare.com/learning/network-layer/what-is-routing/) all traffic through our global network for comprehensive security filtering and access controls. However, there may be specific cases where you want a subset of traffic to bypass Cloudflare's security filtering and route it directly to the Internet. You can scope this breakout traffic to specific applications from the Cloudflare dashboard.

Refer to [Traffic steering](https://developers.cloudflare.com/magic-wan/reference/traffic-steering/) to learn how Cloudflare routes traffic.

## Add an application to your account

Before you can add or remove Breakout traffic applications to your Magic WAN Connector, you need to create an account-level list with the applications that you want to configure. Currently, adding to or modifying this list is only possible via API, through the [`managed_app_id`](https://developers.cloudflare.com/api/resources/magic_transit/subresources/apps/methods/create/) endpoint.

To add applications to your account:

Send a `POST` request to add new apps to your account.

Required API token permissions

At least one of the following [token permissions](https://developers.cloudflare.com/fundamentals/api/reference/permissions/) is required:

* `Magic WAN Write`
* `Magic Transit Write`

```bash
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/apps" \
  --request POST \
  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
  --json '{
    "managed_app_id": "<APP_ID>",
    "name": "<APP_NAME>",
    "type": "<APP_TYPE>"
  }'
```

```json
{
  "result": {
    "account_app_id": "eb09v665c0784618a3e4ba9809258fd4",
    "name": "<APP_NAME>",
    "type": "<APP_TYPE>",
  },
  "success": true,
  "errors": [],
  "messages": []
}
```

You can now add this new app to the Breakout traffic list in your Magic WAN Connector.

### Add an application to Magic WAN Connector

You need to configure Breakout traffic applications for each of your existing sites, as this is a per-site configuration.

* Dashboard

  1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
  2. Select **Networking** > **Magic WAN** > **Connector on-ramps (beta)**.

  1) Select the Magic WAN Connector you want to configure > **Edit**.
  2) Select **Traffic Steering**.
  3) In **Breakout traffic**, select **Assign application traffic**.
  4) Select one or more applications that should bypass Cloudflare filtering from the list. You can also use the search box.

  1. (Optional) You can also pin an application to a WAN port. In **Preferred breakout port**, select the WAN you want to assign your applications to. Refer to [Designate WAN ports for breakout apps](#designate-wan-ports-for-breakout-apps) for more information.

  1) Select **Save**.

  The traffic for the application you chose will now go directly to the Internet and bypass Cloudflare's filtering.

* API

  Note

  You will need your [account ID](https://developers.cloudflare.com/fundamentals/account/find-account-and-zone-ids/) and [API token](https://developers.cloudflare.com/fundamentals/api/get-started/account-owned-tokens/) to use the API.

  1. Send a `GET` [request](https://developers.cloudflare.com/api/resources/magic_transit/subresources/apps/methods/list/) to list the applications associated with an account.

     Required API token permissions

     At least one of the following [token permissions](https://developers.cloudflare.com/fundamentals/api/reference/permissions/) is required:

     * `Magic WAN Write`
     * `Magic WAN Read`
     * `Magic Transit Read`
     * `Magic Transit Write`

     ```bash
     curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/apps" \
       --request GET \
       --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
     ```

     ```json
       {
         "result": [
           {
             "managed_app_id": "<APP_ID>",
             "name": "<APP_NAME>",
             "type": "File Sharing",
             "hostnames": [
               "<app_name.com>",
               "<app-name.info>"
             ]
           }
         ]
       }
     ```

     Take note of the `"managed_app_id"` value for any application you want to add.

  2. Send a `POST` request to add new apps to the Breakout traffic policy.

     Required API token permissions

     At least one of the following [token permissions](https://developers.cloudflare.com/fundamentals/api/reference/permissions/) is required:

     * `Magic WAN Write`
     * `Magic Transit Write`

     ```bash
     curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/app_configs" \
       --request POST \
       --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
       --json '{
         "managed_app_id": "<MANAGED_APP_ID>",
         "breakout": true
       }'
     ```

     ```json
     {
       "result": {
         "account_app_id": "<APP_ID>",
         "name": "<APP_NAME>",
         "type": "<BREAKOUT_OR_PRIORITY>"
       },
       "success": true,
       "errors": [],
       "messages": []
     }
     ```

### Delete an application from Magic WAN Connector

* Dashboard

  1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
  2. Select **Networking** > **Magic WAN** > **Connector on-ramps (beta)**.

  1) Select the Connector you want to configure > **Edit**.
  2) Select **Traffic Steering**.
  3) In **Breakout traffic**, find the application you want to delete > select the **three dots** next to it > **Remove application traffic**.
  4) (Optional) If you have several pages of applications, you can use the search box to quickly find the application you are looking for.

* API

  Note

  You will need your [account ID](https://developers.cloudflare.com/fundamentals/account/find-account-and-zone-ids/) and [API token](https://developers.cloudflare.com/fundamentals/api/get-started/account-owned-tokens/) to use the API.

  You need to delete Breakout traffic applications for each of your existing sites, as this is a per-site configuration.

  1. Send a [`GET` request](https://developers.cloudflare.com/api/resources/magic_transit/subresources/apps/methods/list/) to list the applications associated with a site.

     Required API token permissions

     At least one of the following [token permissions](https://developers.cloudflare.com/fundamentals/api/reference/permissions/) is required:

     * `Magic WAN Write`
     * `Magic WAN Read`
     * `Magic Transit Read`
     * `Magic Transit Write`

     ```bash
     curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/app_configs" \
       --request GET \
       --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
     ```

     ```json
       {
         "result": [
           {
             "id": "<APP_ID>",
             "site_id": "<SITE_ID>",
             "managed_app_id": "<APP_NAME>",
             "breakout": true
           }
         ]
       }
     ```

     Take note of the `"id"` value for the application that want to delete.

  2. Send a `DELETE` request to delete an application from the Breakout traffic policy.

     ```bash
     curl "https://api.cloudflare.com/client/v4/accounts/%7Baccount_id%7D/magic/sites/%7Bsite_id%7D/app_configs/%7Bid%7D" \
       --request DELETE
     ```

     ```json
     {
         "result": {
             "id": "<APP_ID>",
             "site_id": "<SITE_ID>",
             "managed_app_id": "<APP_NAME>",
             "breakout": true
         },
         "success": true,
         "errors": [],
         "messages": []
     }
     ```

## Designate WAN ports for breakout apps

You can pin applications to a specific WAN port in Magic WAN Connector when you need control over which WAN port your applications egress from the device. In case your preferred WAN port goes down, Magic WAN Connector automatically fails over to a standard configured WAN port priority.

With this preferred breakout port, customers have direct control over their local Internet breakout traffic. You can designate a specific WAN uplink as the primary path for your critical applications configured to bypass the Cloudflare network. This provides the predictability and control needed for performance-sensitive applications, ensuring your critical traffic always takes the path you choose.

To pin applications to a WAN port:

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
2. Select **Networking** > **Magic WAN** > **Connector on-ramps (beta)**.
3. Select your Connector > **Edit**.

1) In **Traffic steering** > **Breakout Traffic** find the application you want to pin to a WAN port.
2) Select the three dots next to it > **Edit application traffic**.
3) From the **Preferred breakout port** dropdown, select the WAN port you want to assign to the applications.
4) Select **Save**.

## NetFlow exports from Magic WAN Connector to Magic Network Monitoring

You can configure your Magic WAN Connector to export Netflow statistics for local breakout traffic to [Magic Network Monitoring](https://developers.cloudflare.com/magic-network-monitoring). This provides visibility into traffic that leaves your site directly, bypassing the Cloudflare network.

The Magic WAN Connector appliance uses NetFlow v9 to export flow data for breakout traffic only. You can enable and configure this export by setting the Netflow configuration for the associated site via the Cloudflare API.

### Enable NetFlow exports

Note

To export NetFlow statistics, you will need your [account ID](https://developers.cloudflare.com/fundamentals/account/find-account-and-zone-ids/) and [API token](https://developers.cloudflare.com/fundamentals/api/get-started/account-owned-tokens/), as well as the `site_id` associated with your Magic WAN Connector.

1. Send a `PUT` request to the Netflow configuration endpoint for your site.
2. In the JSON body request, you must include the `collector_ip` parameter. To export traffic statistics to Magic Network Monitoring, use the IP address `162.159.65.1`. This is the only field required to enable the feature.

Minimal configuration example:

```bash
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config" \
  --request PUT \
  --json '{
    "collector_ip": "162.159.65.1"
  }'
```

1. You can customize the configuration by adding optional fields to the JSON payload. These fields include:

* `collector_port`: The UDP port for the collector. The default is `2055`.
* `sampling_rate`: The rate at which packets are sampled.
* `active_timeout`: The timeout for active flows in seconds.
* `inactive_timeout`: The timeout for inactive flows in seconds.

Full configuration example:

```bash
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/magic/sites/$SITE_ID/netflow_config" \
  --request PUT \
  --json '{
    "collector_ip": "162.159.65.1",
    "collector_port": 2055,
    "sampling_rate": 100,
    "active_timeout": 60,
    "inactive_timeout": 30
  }'
```

Your Magic WAN Connector will now begin exporting Netflow data for its breakout traffic, which will be ingested and visualized within your Magic Network Monitoring dashboard. You can retrieve the current settings by sending a `GET` request, or disable the export by sending a `DELETE` request to the same endpoint.

## WARP traffic

If you have Magic WAN Connector and WARP clients deployed in your premises, Magic WAN Connector automatically routes WARP traffic to the Internet rather than Magic WAN IPsec tunnels. This prevents traffic from being encapsulated twice.

You may need to configure your firewall to allow this new traffic. Make sure to allow the following IPs and ports:

* **Destination IPs**: `162.159.193.0/24`, `162.159.197.0/24`
* **Destination ports**: `443`, `500`, `1701`, `2408`, `4443`, `4500`, `8095`, `844`

Refer to [WARP with firewall](https://developers.cloudflare.com/cloudflare-one/team-and-resources/devices/warp/deployment/firewall/) for more information on this topic.
