CNI Maintenance Completed Ahead of Communicated Schedule

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.

Cloudflare Network Interconnect (CNI) edge devices at multiple locations underwent scheduled maintenance ahead of the times communicated to affected customers. On March 30, 2026, between 12:00 UTC and 17:00 UTC, a total of 8 devices across 7 locations were rebooted between 2 hours and 2 days prior to their notified maintenance windows. This was caused by an internal scheduling error where an outdated version of the maintenance schedule was used for execution, while the current version was used for customer notifications. All affected devices successfully completed maintenance and are operating normally. We are contacting affected customers directly to discuss the impact on their specific configurations.