docs(cni): clarify maintenance coordination (#33043)

* docs(cni): clarify maintenance coordination

* docs(cni): scope maintenance guidance

* docs(cni): clarify non-routine capacity

* docs(cni): clarify non-routine deployment

* docs(cni): align maintenance notice guidance

* docs(cni): clarify redundant maintenance timing

Author: roshnicdave

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

@@ -0,0 +1,38 @@
+---
+pcx_content_type: concept
+products:
+  - network-interconnect
+title: Maintenance
+description: Understand how Cloudflare coordinates maintenance across resilient CNI deployments.
+sidebar:
+  order: 6
+---
+
+## Planned maintenance
+
+Routine CNI-disruptive maintenance is planned work that can interrupt traffic on an affected CNI connection. Cloudflare coordinates this work across resilient Cloudflare Network Interconnect (CNI) deployments, including across CNI locations.
+
+### Timing and scheduling
+
+For Dataplane v2 connectivity in multi-homed PoPs only:
+
+- **Routine maintenance**: Minimum one week notice.
+- **Emergency maintenance**: Best-effort notice, which may be less than one week.
+- Routine maintenance on redundant devices at the same location will occur on different days.
+- Routine maintenance is not rescheduled to accommodate customer schedule preferences.
+
+| CNI deployment                                                                                                   | During routine CNI-disruptive maintenance |
+| ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
+| One CNI connection at one location                                                                               | The connection can be interrupted.        |
+| Two CNI connections on separate devices at one location                                                          | One connection remains in service.        |
+| Four CNI connections across two coordinated locations, with two connections on separate devices at each location | Three connections remain in service.      |
+
+## Emergency and non-routine maintenance
+
+Non-routine maintenance, such as maintenance that affects an entire PoP, can affect all CNI connections at the affected location. For the four-connection deployment with two connections at each of two locations, a full-PoP non-routine event at one location can interrupt two connections, leaving two in service. Cloudflare avoids performing non-routine maintenance at multiple coordinated locations at the same time.
+
+Cloudflare coordinates emergency maintenance across locations where feasible.
+
+## Receive maintenance notifications
+
+To configure circuit-specific or point-of-presence (PoP) maintenance notifications, refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts/).

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

@@ -3,38 +3,14 @@ pcx_content_type: concept
 products:
   - network-interconnect
 title: Operational guidance
-description: Maintenance windows and troubleshooting guidance for CNI
+description: Validate CNI failover and troubleshoot connectivity issues.
 sidebar:
   order: 7
 ---
 
-## Understanding maintenance and availability
+For maintenance expectations and notifications, refer to [Maintenance](/network-interconnect/maintenance/).
 
-Also refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts).
-
-Regular network maintenance may impact Cloudflare Network Interconnect (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). Cloudflare does not guarantee coordinated maintenance between PoP locations.
-
-## Maintenance expectations
-
-### Notice periods
-
-For Dataplane v2 connectivity in multi-homed PoPs only:
-
-- **Routine maintenance**: Minimum two business days notice.
-- **Emergency maintenance**: Best-effort notice, which may be less than two business days.
-
-To receive advance alerts, configure [CNI maintenance notifications](/network-interconnect/monitoring-and-alerts/).
-
-### Scheduling patterns
-
-- Maintenance on redundant devices at the same location may occur on consecutive days with a minimum 16-hour gap between windows.
-- Cloudflare does not coordinate maintenance timing between different PoP locations.
-- Routine maintenance is generally not rescheduled to accommodate customer schedule preferences.
-
-### Customer responsibility
+## Customer responsibility
 
 Your CNI deployment must tolerate an unplanned outage on any single circuit at any time. This means:
 
@@ -52,4 +28,4 @@ If no system-wide problems are reported, gather the following information before
 - **Identification**: The CNI IP address or point-to-point prefix for the impacted CNI. If your CNI is part of a Magic setup, please also provide the name of the Magic Transit/WAN interconnect as listed in your dashboard.
 - **Physical Layer**: Light levels of the CNI link (if applicable).
 - **Service Impact**: Confirmation whether Magic Transit / WAN traffic was affected.
-- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).
+- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn).