Cloudflare Inc. reported a technical service disruption on April 22, 2026, characterized by significant delays in the activation of new customer sites and the provisioning of DNS zones. The issue, which was first acknowledged by the company’s engineering team during the early morning hours, primarily affected the administrative control plane rather than the global content delivery network. Consequently, while existing websites and services already configured on the Cloudflare platform continued to operate without interruption, new users and existing customers attempting to add new domains faced prolonged wait times.
Technical logs indicated that the delay originated within the zone activation pipeline, a critical component of the Cloudflare Dashboard and API. Under normal operating conditions, the transition of a site from a pending state to an active state—following the update of nameservers at the registrar level—typically occurs within minutes. However, during this incident, the propagation of these settings across Cloudflare’s edge infrastructure was stalled. The company’s status page categorized the event as a performance issue affecting the Cloudflare Dashboard and API services, specifically noting increased error rates in the Analytics Engine API.
At 08:30 UTC, Cloudflare officially confirmed it was investigating reports of delayed zone activations. By 10:00 UTC, the technical team identified the root cause within the internal systems responsible for managing zone metadata and state transitions. This bottleneck prevented the automated systems from processing the queue of new site requests, leaving many domains in a "Pending Nameserver Update" status despite correct configurations. To mitigate the impact, engineers implemented a fix designed to optimize the processing of the activation backlog.
A fix was formally deployed and moved into the monitoring phase at 13:01 UTC. Following the deployment, Cloudflare reported that the backlog of pending activations began to clear, though some users experienced residual delays as the system processed several hours of queued requests. The company emphasized that the data plane, which handles the actual delivery of web traffic and security filtering for active sites, remained unaffected throughout the duration of the event. Security features, including the Web Application Firewall and DDoS mitigation protocols, remained fully operational for all currently active zones.
The incident occurred concurrently with scheduled maintenance at Cloudflare’s Salt Lake City and Seattle data centers, though the company clarified that the activation delays were a separate, unscheduled event. No unauthorized access or data breaches were reported in connection with the delay. Cloudflare has since returned to nominal operating levels and continues to monitor platform metrics to ensure sustained stability across its global network.