Operational guidance
Also refer to 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.
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.
- Maintenance on redundant devices (for example, edge router one and edge router two) 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.
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.
When facing connectivity problems, your first action should be to check for broader service disruptions. Visit Cloudflare Status ↗ to see if any scheduled maintenance or active incidents are impacting services. This helps determine if the issue originates outside your network. Refer to Monitoring and alerts.
If no system-wide problems are reported, gather the following information before submitting a support case. Providing comprehensive details facilitates a faster resolution:
- Timeline: When the issue began and ended (if applicable), including the timezone.
- 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).