CNI Maintenance Completed Ahead of Communicated Schedule

What to do

• Check whether your product depends on Cloudflare. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-03-30 12:00 UTC and 2026-03-30 12:00 UTC may need a replay.

• Subscribe to Cloudflare's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Cloudflare 1

1. resolvedMar 30, 2026, 12:00 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.