Issues with Cloudflare One Appliance, Cloudflare Tunnel, and Cloudflare Mesh connections on 2026-04-21

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 1h 8m it lasted.

  Anything that failed between 2026-04-21 03:00 UTC and 2026-04-21 04:08 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. resolvedApr 21, 2026, 4:08 AM UTC

   An issue prevented Cloudflare One Appliance as well as a subset of new connections for Cloudflare Tunnel and Cloudflare Mesh from being successfully established between 04:08 and 06:45 AM UTC on Tuesday, April 21st. This issue has been fully resolved, and all services are operating normally. During this timeframe, customers may have experienced connectivity errors when attempting to register new devices, nodes, or tunnels. The impact was most significant for the Cloudflare One Appliance, with data plane issues impacting the majority of devices. For Cloudflare Tunnel and Cloudflare Mesh, the issue was strictly limited to the registration or re-initiation of connections during the impact window. For these products, existing tunnels, devices, and connections that were already active prior to the incident remained unaffected and continued to function as usual. Our engineering team identified a bug that caused certain connection updates to be lost silently. We have since addressed the root cause and are monitoring the environment to ensure continued stability. We apologize for any disruption this may have caused.

   provider

Corrections

None so far.

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