From 6344b5ee060afb4c7dc51f33db33ef660b11db12 Mon Sep 17 00:00:00 2001 From: Roshni Dave Date: Wed, 26 Aug 2026 08:46:11 -0700 Subject: [PATCH 1/6] docs(cni): clarify maintenance coordination --- .../2025-06-20-cni-maintenance-alerts.mdx | 2 +- .../docs/network-interconnect/get-started.mdx | 2 +- .../docs/network-interconnect/maintenance.mdx | 31 +++++++++++++++++ .../monitoring-and-alerts.mdx | 16 ++++----- .../operational-guidance.mdx | 33 +++---------------- src/content/notifications/index.yaml | 6 ++-- 6 files changed, 48 insertions(+), 42 deletions(-) create mode 100644 src/content/docs/network-interconnect/maintenance.mdx diff --git a/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx b/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx index 395d73292bb..64b31b33924 100644 --- a/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx +++ b/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx @@ -4,6 +4,6 @@ description: Subscribe to email alerts for planned maintenance on CNI v1 circuit date: 2025-06-20 --- -Customers using Cloudflare Network Interconnect with the v1 dataplane can now subscribe to maintenance alert emails. These alerts notify you of planned maintenance windows that may affect your CNI circuits. +Customers using Cloudflare Network Interconnect v1 circuits with Cloudflare Virtual Network can subscribe to maintenance alert emails. These alerts notify you of planned maintenance windows that may affect eligible CNI circuits. For more information, refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts/). diff --git a/src/content/docs/network-interconnect/get-started.mdx b/src/content/docs/network-interconnect/get-started.mdx index 16c0b376aa7..782cf199c9b 100644 --- a/src/content/docs/network-interconnect/get-started.mdx +++ b/src/content/docs/network-interconnect/get-started.mdx @@ -76,7 +76,7 @@ Consider the following service levels when planning your deployment: - **No Formal SLA**: - CNI is currently offered at no charge and without a formal [Service Level Agreement (SLA)](https://www.cloudflare.com/service-specific-terms-network-services/#cf-network-interconnect-terms). - Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare data centers the recovery time could be several days. Therefore, we always recommend backup connectivity to a different device or via an Internet tunnel. -- **Observability**: There is no visibility of the interconnect config/status within the Cloudflare dashboard. +- **Observability**: The Cloudflare dashboard shows the status of your CNI interconnect. It does not validate end-to-end traffic failover. - **Availability**: Locations that support device-level diversity can maintain connectivity during maintenance when your connections terminate on separate devices. Single-device deployments will experience full service disruption during maintenance. - **Backup Connectivity**: You are required to maintain alternative Internet connectivity as a backup for all CNI implementations. - **Capacity planning**: You are responsible for capacity planning across your available links to Cloudflare, based on the topology and size of those links. diff --git a/src/content/docs/network-interconnect/maintenance.mdx b/src/content/docs/network-interconnect/maintenance.mdx new file mode 100644 index 00000000000..50c5c61802d --- /dev/null +++ b/src/content/docs/network-interconnect/maintenance.mdx @@ -0,0 +1,31 @@ +--- +pcx_content_type: concept +products: + - network-interconnect +title: Maintenance +description: Understand how Cloudflare coordinates maintenance across resilient CNI deployments. +sidebar: + order: 6 +--- + +Cloudflare coordinates routine CNI-disruptive maintenance across resilient Cloudflare Network Interconnect (CNI) deployments, including across CNI locations. + +## Planned maintenance + +Routine CNI-disruptive maintenance is planned work that can interrupt traffic on an affected CNI connection. Cloudflare schedules this work to preserve the remaining connections in your resilient deployment. + +| 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. Cloudflare avoids performing non-routine maintenance at multiple coordinated locations at the same time. + +Emergency maintenance can require shorter notice. 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/). diff --git a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx index e8db8842b0f..374adc34aa1 100644 --- a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx +++ b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx @@ -22,18 +22,18 @@ The Status column displays three statuses: - **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**. +## Maintenance notifications -## Alerts (v1 dataplane only) +You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. -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. +For information about planned maintenance coordination, refer to [Maintenance](/network-interconnect/maintenance/). -**CNI Connection Maintenance Alert:** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Cloudflare Virtual Network only. -- You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections. -- You will be notified if the details of a scheduled maintenance change or if it is canceled. -- For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments. +**CNI Connection Maintenance Alert:** This alert is available for CNI v1 circuits used with Cloudflare Virtual Network. It identifies scheduled, changed, or canceled disruptive maintenance that directly affects your CNI circuit. + +- This alert is not available for CNI v2 connections. + +**Cloudflare Status Maintenance Notification:** This alert warns about potentially disruptive maintenance at a Cloudflare Point of Presence (PoP). It is not specific to individual CNI circuits, and it may be relevant to CNI used for peering or Cloudflare Virtual Network. -**Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location. This includes connections used only for peering without Cloudflare Virtual Network. -- You will be warned about potentially disruptive maintenance at the PoP level. - By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these. - By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits. diff --git a/src/content/docs/network-interconnect/operational-guidance.mdx b/src/content/docs/network-interconnect/operational-guidance.mdx index a94aa4bae85..f2bfcbb15c3 100644 --- a/src/content/docs/network-interconnect/operational-guidance.mdx +++ b/src/content/docs/network-interconnect/operational-guidance.mdx @@ -3,44 +3,19 @@ pcx_content_type: concept products: - network-interconnect title: Operational guidance -description: Maintenance windows and troubleshooting guidance for CNI +description: Plan a resilient CNI deployment and troubleshoot connectivity issues. sidebar: order: 7 --- -## Understanding maintenance and availability +For information about maintenance coordination 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: - Traffic failover between redundant circuits must be automatic. - If your operations require manual intervention to reroute traffic during maintenance, your configuration needs review. -- Contact your account team to validate your failover design. ## Troubleshooting @@ -52,4 +27,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). \ No newline at end of file +- **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn). diff --git a/src/content/notifications/index.yaml b/src/content/notifications/index.yaml index 7522e0cd7da..a7b92bf1e67 100644 --- a/src/content/notifications/index.yaml +++ b/src/content/notifications/index.yaml @@ -615,8 +615,8 @@ entries: otherFilters: None. - name: Connection Maintenance Alert - audience: "[Classic CNI](/network-interconnect/classic-cni/) customers who want to be alerted to maintenance events that might affect Classic CNI." - availability: Purchase of Cloudflare Network Interconnect (CNI). + audience: Customers with eligible CNI v1 circuits used with Cloudflare Virtual Network. + availability: Cloudflare Network Interconnect v1 with Cloudflare Virtual Network. associatedProducts: Network Interconnect - nextSteps: No action is needed. + nextSteps: To configure this notification, refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts/). otherFilters: None. From f97680b2831f82ac13f939fcd0f80478fd990069 Mon Sep 17 00:00:00 2001 From: Roshni Dave Date: Wed, 26 Aug 2026 09:29:58 -0700 Subject: [PATCH 2/6] docs(cni): scope maintenance guidance --- .../2025-06-20-cni-maintenance-alerts.mdx | 2 +- .../docs/network-interconnect/get-started.mdx | 2 +- .../docs/network-interconnect/maintenance.mdx | 15 +++++++++++---- .../monitoring-and-alerts.mdx | 16 ++++++++-------- .../operational-guidance.mdx | 5 +++-- src/content/notifications/index.yaml | 6 +++--- 6 files changed, 27 insertions(+), 19 deletions(-) diff --git a/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx b/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx index 64b31b33924..395d73292bb 100644 --- a/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx +++ b/src/content/changelog/network-interconnect/2025-06-20-cni-maintenance-alerts.mdx @@ -4,6 +4,6 @@ description: Subscribe to email alerts for planned maintenance on CNI v1 circuit date: 2025-06-20 --- -Customers using Cloudflare Network Interconnect v1 circuits with Cloudflare Virtual Network can subscribe to maintenance alert emails. These alerts notify you of planned maintenance windows that may affect eligible CNI circuits. +Customers using Cloudflare Network Interconnect with the v1 dataplane can now subscribe to maintenance alert emails. These alerts notify you of planned maintenance windows that may affect your CNI circuits. For more information, refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts/). diff --git a/src/content/docs/network-interconnect/get-started.mdx b/src/content/docs/network-interconnect/get-started.mdx index 782cf199c9b..16c0b376aa7 100644 --- a/src/content/docs/network-interconnect/get-started.mdx +++ b/src/content/docs/network-interconnect/get-started.mdx @@ -76,7 +76,7 @@ Consider the following service levels when planning your deployment: - **No Formal SLA**: - CNI is currently offered at no charge and without a formal [Service Level Agreement (SLA)](https://www.cloudflare.com/service-specific-terms-network-services/#cf-network-interconnect-terms). - Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare data centers the recovery time could be several days. Therefore, we always recommend backup connectivity to a different device or via an Internet tunnel. -- **Observability**: The Cloudflare dashboard shows the status of your CNI interconnect. It does not validate end-to-end traffic failover. +- **Observability**: There is no visibility of the interconnect config/status within the Cloudflare dashboard. - **Availability**: Locations that support device-level diversity can maintain connectivity during maintenance when your connections terminate on separate devices. Single-device deployments will experience full service disruption during maintenance. - **Backup Connectivity**: You are required to maintain alternative Internet connectivity as a backup for all CNI implementations. - **Capacity planning**: You are responsible for capacity planning across your available links to Cloudflare, based on the topology and size of those links. diff --git a/src/content/docs/network-interconnect/maintenance.mdx b/src/content/docs/network-interconnect/maintenance.mdx index 50c5c61802d..9a722c8dff2 100644 --- a/src/content/docs/network-interconnect/maintenance.mdx +++ b/src/content/docs/network-interconnect/maintenance.mdx @@ -8,11 +8,18 @@ sidebar: order: 6 --- -Cloudflare coordinates routine CNI-disruptive maintenance across resilient Cloudflare Network Interconnect (CNI) deployments, including across CNI locations. - ## Planned maintenance -Routine CNI-disruptive maintenance is planned work that can interrupt traffic on an affected CNI connection. Cloudflare schedules this work to preserve the remaining connections in your resilient deployment. +Routine CNI-disruptive maintenance is planned work that can interrupt traffic on an affected CNI connection. Maintenance windows average six hours. 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 two business days notice. +- **Emergency maintenance**: Best-effort notice, which may be less than two business days. +- Maintenance on redundant devices at the same location may occur on consecutive days with a minimum 16-hour gap between windows. +- Routine maintenance is generally not rescheduled to accommodate customer schedule preferences. | CNI deployment | During routine CNI-disruptive maintenance | | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | @@ -24,7 +31,7 @@ Routine CNI-disruptive maintenance is planned work that can interrupt traffic on Non-routine maintenance, such as maintenance that affects an entire PoP, can affect all CNI connections at the affected location. Cloudflare avoids performing non-routine maintenance at multiple coordinated locations at the same time. -Emergency maintenance can require shorter notice. Cloudflare coordinates emergency maintenance across locations where feasible. +Cloudflare coordinates emergency maintenance across locations where feasible. ## Receive maintenance notifications diff --git a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx index 374adc34aa1..e8db8842b0f 100644 --- a/src/content/docs/network-interconnect/monitoring-and-alerts.mdx +++ b/src/content/docs/network-interconnect/monitoring-and-alerts.mdx @@ -22,18 +22,18 @@ The Status column displays three statuses: - **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**. -## Maintenance notifications -You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. +## Alerts (v1 dataplane only) -For information about planned maintenance coordination, refer to [Maintenance](/network-interconnect/maintenance/). +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:** This alert is available for CNI v1 circuits used with Cloudflare Virtual Network. It identifies scheduled, changed, or canceled disruptive maintenance that directly affects your CNI circuit. - -- This alert is not available for CNI v2 connections. - -**Cloudflare Status Maintenance Notification:** This alert warns about potentially disruptive maintenance at a Cloudflare Point of Presence (PoP). It is not specific to individual CNI circuits, and it may be relevant to CNI used for peering or Cloudflare Virtual Network. +**CNI Connection Maintenance Alert:** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Cloudflare Virtual Network only. +- You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections. +- You will be notified if the details of a scheduled maintenance change or if it is canceled. +- For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments. +**Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location. This includes connections used only for peering without Cloudflare Virtual Network. +- You will be warned about potentially disruptive maintenance at the PoP level. - By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these. - By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits. diff --git a/src/content/docs/network-interconnect/operational-guidance.mdx b/src/content/docs/network-interconnect/operational-guidance.mdx index f2bfcbb15c3..e59c66e3ef5 100644 --- a/src/content/docs/network-interconnect/operational-guidance.mdx +++ b/src/content/docs/network-interconnect/operational-guidance.mdx @@ -3,12 +3,12 @@ pcx_content_type: concept products: - network-interconnect title: Operational guidance -description: Plan a resilient CNI deployment and troubleshoot connectivity issues. +description: Validate CNI failover and troubleshoot connectivity issues. sidebar: order: 7 --- -For information about maintenance coordination and notifications, refer to [Maintenance](/network-interconnect/maintenance/). +For maintenance expectations and notifications, refer to [Maintenance](/network-interconnect/maintenance/). ## Customer responsibility @@ -16,6 +16,7 @@ Your CNI deployment must tolerate an unplanned outage on any single circuit at a - Traffic failover between redundant circuits must be automatic. - If your operations require manual intervention to reroute traffic during maintenance, your configuration needs review. +- Contact your account team to validate your failover design. ## Troubleshooting diff --git a/src/content/notifications/index.yaml b/src/content/notifications/index.yaml index a7b92bf1e67..7522e0cd7da 100644 --- a/src/content/notifications/index.yaml +++ b/src/content/notifications/index.yaml @@ -615,8 +615,8 @@ entries: otherFilters: None. - name: Connection Maintenance Alert - audience: Customers with eligible CNI v1 circuits used with Cloudflare Virtual Network. - availability: Cloudflare Network Interconnect v1 with Cloudflare Virtual Network. + audience: "[Classic CNI](/network-interconnect/classic-cni/) customers who want to be alerted to maintenance events that might affect Classic CNI." + availability: Purchase of Cloudflare Network Interconnect (CNI). associatedProducts: Network Interconnect - nextSteps: To configure this notification, refer to [Monitoring and alerts](/network-interconnect/monitoring-and-alerts/). + nextSteps: No action is needed. otherFilters: None. From e8381634c3dc04355710f10dc2e9c7df9102e37a Mon Sep 17 00:00:00 2001 From: Roshni Dave Date: Wed, 26 Aug 2026 09:31:13 -0700 Subject: [PATCH 3/6] docs(cni): clarify non-routine capacity --- src/content/docs/network-interconnect/maintenance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/network-interconnect/maintenance.mdx b/src/content/docs/network-interconnect/maintenance.mdx index 9a722c8dff2..58bd7511afe 100644 --- a/src/content/docs/network-interconnect/maintenance.mdx +++ b/src/content/docs/network-interconnect/maintenance.mdx @@ -29,7 +29,7 @@ For Dataplane v2 connectivity in multi-homed PoPs only: ## 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. Cloudflare avoids performing non-routine maintenance at multiple coordinated locations at the same time. +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 described above, 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. From 6314beb7cc11457819caf704f0cd9e64e625882e Mon Sep 17 00:00:00 2001 From: Roshni Dave Date: Wed, 26 Aug 2026 09:35:00 -0700 Subject: [PATCH 4/6] docs(cni): clarify non-routine deployment --- src/content/docs/network-interconnect/maintenance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/network-interconnect/maintenance.mdx b/src/content/docs/network-interconnect/maintenance.mdx index 58bd7511afe..e546ce4c061 100644 --- a/src/content/docs/network-interconnect/maintenance.mdx +++ b/src/content/docs/network-interconnect/maintenance.mdx @@ -29,7 +29,7 @@ For Dataplane v2 connectivity in multi-homed PoPs only: ## 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 described above, 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. +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. From b51a3ea66585ae1334d87832a5ff729fd716afe8 Mon Sep 17 00:00:00 2001 From: Roshni Dave Date: Wed, 26 Aug 2026 23:27:34 -0700 Subject: [PATCH 5/6] docs(cni): align maintenance notice guidance --- src/content/docs/network-interconnect/maintenance.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/network-interconnect/maintenance.mdx b/src/content/docs/network-interconnect/maintenance.mdx index e546ce4c061..68d78d09fdb 100644 --- a/src/content/docs/network-interconnect/maintenance.mdx +++ b/src/content/docs/network-interconnect/maintenance.mdx @@ -10,16 +10,16 @@ sidebar: ## Planned maintenance -Routine CNI-disruptive maintenance is planned work that can interrupt traffic on an affected CNI connection. Maintenance windows average six hours. Cloudflare coordinates this work across resilient Cloudflare Network Interconnect (CNI) deployments, including across CNI locations. +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 two business days notice. -- **Emergency maintenance**: Best-effort notice, which may be less than two business days. -- Maintenance on redundant devices at the same location may occur on consecutive days with a minimum 16-hour gap between windows. -- Routine maintenance is generally not rescheduled to accommodate customer schedule preferences. +- **Routine maintenance**: Minimum one week notice. +- **Emergency maintenance**: Best-effort notice, which may be less than one week. +- Maintenance on redundant devices at the same location may occur on different days. +- Routine maintenance is not rescheduled to accommodate customer schedule preferences. | CNI deployment | During routine CNI-disruptive maintenance | | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | From a684107793df296d24010e3611660d408adab7ab Mon Sep 17 00:00:00 2001 From: Roshni Dave Date: Fri, 28 Aug 2026 11:10:19 -0700 Subject: [PATCH 6/6] docs(cni): clarify redundant maintenance timing --- src/content/docs/network-interconnect/maintenance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/network-interconnect/maintenance.mdx b/src/content/docs/network-interconnect/maintenance.mdx index 68d78d09fdb..31c3259fa68 100644 --- a/src/content/docs/network-interconnect/maintenance.mdx +++ b/src/content/docs/network-interconnect/maintenance.mdx @@ -18,7 +18,7 @@ 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. -- Maintenance on redundant devices at the same location may occur on different days. +- 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 |