[CNI] Added dataplane 2 info

public/__redirects

@@ -403,6 +403,7 @@
 /network-interconnect/express-cni/create-interconnects/ /network-interconnect/ 301
 /network-interconnect/express-cni/ /network-interconnect/ 301
 /network-interconnect/pni-and-peering/ /network-interconnect/ 301
+/network-interconnect/static/cni-locations-04-08-2025.pdf /network-interconnect/static/cni-locations-30-10-2025.pdf 301
 
 # Constellation
 /constellation/ /workers-ai/ 301

src/content/docs/network-interconnect/index.mdx

@@ -16,33 +16,35 @@ Connect your network infrastructure directly to Cloudflare
 
 <Plan type="enterprise" />
 
-Cloudflare Network Interconnect (CNI) allows you to connect your network infrastructure directly to Cloudflare — rather than using the public Internet — for a more reliable and secure experience. With CNI, you can bring Cloudflare's full suite of network functions to your physical network edge.
+Cloudflare Network Interconnect (CNI) allows you to connect your network infrastructure directly to Cloudflare — rather than using the public Internet — for a more performant and secure experience. With CNI, you can bring Cloudflare's full suite of network functions to your network edge.
 
-## Why Use CNI? Key Benefits
+## Why Use CNI? Key benefits
 
 Enterprises use CNI to achieve:
 - **Enhanced Performance**: Gain lower latency and more consistent network throughput.
 - **Increased Security**: Reduce your network's attack surface by connecting privately and avoiding the public Internet.
 
-## Connection Types
+## Connection types
 
 Choose the model that best fits your infrastructure and operational needs.
 
-| | Direct Interconnect | Partner Interconnect |
-| - | - | - |
-| **Port type** | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners. |
-| **Operations** | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment. | Your partner manages the connection logistics, often through a software-defined networking portal. |
-| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability. | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. |
+| | Direct Interconnect | Partner Interconnect | Cloud Interconnect |
+| --- | --- | --- | --- |
+| **Port type** | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners. | A private connection between a customer's cloud environments (for example, AWS, Google Cloud) and Cloudflare |
+| **Operations** | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment. | Your partner manages the connection logistics, often through a software-defined networking portal. | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. |
+| **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability. | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services. |
 
 ## Dataplane
 
 Cloudflare's data centers may support one or more interconnect dataplanes. The dataplane is the type of equipment that terminates your direct connection:
-- **Dataplane v1.0**: A peering connection to a Cloudflare edge data center that supports GRE tunnels for connecting with the Magic Networking overlay.
-- **Dataplane v1.1**: An enhanced version of the 1.0 dataplane that supports GRE-less delivery for Magic Transit Direct Server Return.
+- **Dataplane v1**: A peering connection to a Cloudflare edge data center that supports GRE tunnels for connecting with the Magic Networking overlay.
+- **Dataplane v1.1**: An enhanced version of the v1 dataplane that supports GRE-less delivery for Magic Transit Direct Server Return.
+- **Dataplane v2 (beta)**: Is based on the Customer Connectivity Router (CCR), which is specifically designed for customer connectivity. It provides simplified routing without GRE tunneling and supports a 1,500-byte MTU bidirectionally.
 
-When you review the [available locations](/network-interconnect/static/cni-locations-04-08-2025.pdf) (PDF), you can see which dataplane version(s) are available.
 
-## Product Use Cases
+When you review the [available locations](/network-interconnect/static/cni-locations-30-10-2025.pdf) (PDF), you can see which dataplane version(s) are available.
+
+## Product use cases
 
 <Render file="cni-product-use-cases" product="networking-services" />
 
@@ -63,3 +65,4 @@ Magic Transit is a network security and performance solution that offers DDoS pr
 <RelatedProduct header="Magic WAN" href="/magic-wan/" product="magic-wan">
 Improve security and performance for your entire corporate network, reducing cost and operation complexity.
 </RelatedProduct>
+

src/content/docs/network-interconnect/monitoring-and-alerts.mdx

@@ -7,6 +7,18 @@ sidebar:
 
 import { Render, DashButton } from "~/components"
 
+## Monitoring
+
+The Cloudflare dashboard shows a list of all previously created interconnects, as well as useful information such as IP addresses, speed, type of interconnect, and status.
+
+The [Status column](https://dash.cloudflare.com/?to=/:account/interconnects/all) in the dashboard shows three different status:
+
+- **Active**: The link operational state at the interconnect port on the Customer Connectivity Router (CCR) is up. This means that the CCR port sees sufficient light levels and has negotiated an Ethernet link.
+- **Unhealthy**: The link operational state at interconnect port is down. This might mean the CCR does not see light, cannot negotiate an Ethernet signal, or the light levels are below -20 dBm. You can take general troubleshooting steps to solve the issue (such as checking cables and status lights for connectivity issues). If you are unable to solve the issue in this way, contact your account team.
+- **Pending**: The link is not yet active. This is expected and can occur for several reasons: the customer has not received a cross-connect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The `Pending` status will disappear after the customer completes the cross-connect and status moves to `Active`.
+
+## Alerts (v1 dataplane only)
+
 You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. It is recommended to subscribe to two types of notifications to stay fully informed.
 
 **CNI Connection Maintenance Alert (beta):** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Magic Networking overlay only.
@@ -25,7 +37,7 @@ You can configure notifications for upcoming CNI maintenance events using the No
 
 1. In the Cloudflare dashboard, go to the **Notifications** page.
 
-<DashButton url="/?to=/:account/notifications" />
+	<DashButton url="/?to=/:account/notifications" />
 
 2. Select **Add**.
 3. From the product drop-down menu, select **Cloudflare Network Interconnect**.
@@ -36,19 +48,24 @@ You can configure notifications for upcoming CNI maintenance events using the No
 
 ### Enable Cloudflare Status Maintenance Notification
 
-1. First, identify the PoP code for your CNI circuit:
-   - In the Cloudflare dashboard, go to the **Configuration** page in Magic Transit or Magic WAN.
-	   - For Magic Transit: <DashButton url="/?to=/:account/magic-transit/configuration" />
-		 - For Magic WAN: <DashButton url="/?to=/:account/magic-wan/configuration" />
-   - Select the **Interconnects** tab.
-   - Select the CNI you want to enable notifications for.
-   - In the menu that appears, note the Data Center code (for example, `gru-b`).
-2. Now, configure the alert:
-   - Go to **Notifications** and select **Add**.
-   - From the product drop-down menu, select **Cloudflare Status**.
-   - Select **Maintenance Notification**.
-   - Give your notification a name and choose your notification method.
-   - Select **Next**.
-   - Optionally, use the **Filter on Event Type** to select only the event types you want to be alerted for (Scheduled, Changed, Canceled).
-   - In **Filter on Points of Presence**, enter the three-letter code for your PoP (for example, for `gru-b`, enter `gru`). You can add multiple PoPs, separated by commas.
-   - Select **Create**.
+First, identify the PoP code for your CNI circuit:
+1. In the Cloudflare dashboard, go to the **Configuration** page in Magic Transit or Magic WAN.
+
+	- **For Magic Transit**: <DashButton url="/?to=/:account/magic-transit/configuration" />
+
+	- **For Magic WAN**: <DashButton url="/?to=/:account/magic-wan/configuration" />
+
+2. Select the **Interconnects** tab.
+3. Select the CNI you want to enable notifications for.
+4. In the menu that appears, note the Data Center code (for example, `gru-b`).
+
+Now, configure the alert:
+
+1. Go to **Notifications** and select **Add**.
+2. From the product drop-down menu, select **Cloudflare Status**.
+3. Select **Maintenance Notification**.
+4. Give your notification a name and choose your notification method.
+5. Select **Next**.
+6. Optionally, use the **Filter on Event Type** to select only the event types you want to be alerted for (Scheduled, Changed, Canceled).
+7. In **Filter on Points of Presence**, enter the three-letter code for your PoP (for example, for `gru-b`, enter `gru`). You can add multiple PoPs, separated by commas.
+8. Select **Create**.

src/content/docs/network-interconnect/operational-guidance.mdx

@@ -13,8 +13,8 @@ Also refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alert
 
 Cloudflare performs regular network maintenance that may impact CNI connectivity.
 
-- **Maintenance Impact**: Maintenance windows average six hours. Customers who are not redundantly connected to diverse devices, for instance in single-homed PoPs, will experience a complete service disruption on CNI in that location.
-- **Designing for Availability**: For critical applications, deploy CNI in locations that support diversity on the device level (multi-homed PoPs) to ensure protection against a single point of hardware failure and routine maintenance. Cloudflare does not guarantee coordinated maintenance between PoP locations. This means connecting to two different PoPs does not ensure protection against coincident service disruption.
+- **Maintenance impact**: Maintenance windows average six hours. Customers who are not redundantly connected to diverse devices, for instance in single-homed PoPs, will experience a complete service disruption on CNI in that location.
+- **Designing for availability**: For critical applications, deploy CNI in locations that support diversity on the device level (multi-homed PoPs). Cloudflare does not guarantee coordinated maintenance between PoP locations.
 
 ## Troubleshooting
 

src/content/partials/networking-services/cni-product-use-cases.mdx

@@ -5,12 +5,12 @@
 CNI provides a private point-to-point IP connection with Cloudflare. There are two dataplanes that come with different technical specifications.
 
 
-|  | Dataplane v1.0 | Dataplane v1.1 |
+|  | Dataplane v1 & 1.1 | Dataplane v2 (beta) |
 | ---- | ---- | ---- |
-| **Magic Transit Direct Server Return (DSR)** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with a GRE tunnel established over the interconnect circuit. | Supported with or without a GRE tunnel established over the interconnect circuit. |
-| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. | Supported with a GRE tunnel established over the interconnect circuit. |
-| **Magic WAN and Zero Trust**  <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. | Supported with or without a GRE tunnel established over the interconnect circuit. |
-| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Supported. All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. |
-| **Application Security and Performance** <br /> Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic networking routing table. | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic networking routing table. |
+| **Magic Transit Direct Server Return (DSR)** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with a GRE tunnel established over the interconnect circuit. For v1.1, supported with or without a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Magic Transit with Egress** <br /> DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. For v1.1, supported with or without a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Magic WAN and Zero Trust**  <br /> Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. For v1.1, supported with or without a GRE tunnel established over the interconnect circuit. | Supported. |
+| **Peering** <br /> Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. <br /><br /> All customers connecting with the edge data center will exchange public routes at that PoP with AS13335. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Not supported. |
+| **Application Security and Performance** <br /> Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. <br /> **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic networking routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. |
 
 For more details refer to the [prerequisites section](/network-interconnect/get-started/#prerequisites).