Resolved
This incident has been resolved.
Posted Feb 20, 2026 - 23:50 UTC
Monitoring
Cloudflare has enabled the remaining IP prefixes to their previous state. We are continuing to monitor for additional impact.
Posted Feb 20, 2026 - 23:38 UTC
Update
Cloudflare continues working to mitigate impact from the last subset of prefixes which were withdrawn and were unable to be mitigated through toggling advertisement on the dashboard.
Posted Feb 20, 2026 - 23:03 UTC
Update
Cloudflare is working to mitigate impact from the last subset of prefixes which were withdrawn and were unable to be mitigated through toggling advertisement on the dashboard.
Posted Feb 20, 2026 - 22:16 UTC
Update
Cloudflare is continuing to restore prefixes to their previous state. Any customer who withdrew their IPs as a result of this incident will see their IPs withdrawn upon full impact mitigation. Customers are still able to restore service from the dashboard by readvertising their IPs. Cloudflare is aware that some customers are unable to reload their IPs through the dashboard and are working on a fix.
Posted Feb 20, 2026 - 20:50 UTC
Update
Update
Update
Identified
Cloudflare has identified impact to a subset of BYOIP prefixes. Cloudflare has identified and mitigated the underlying issue and is working to restore availability to impacted advertisements.
Posted Feb 20, 2026 - 19:09 UTC
Investigating
Cloudflare is investigating issues with our services and/or network. Users may experience errors or timeouts reaching Cloudflare’s network or services. We will update this status page to clarify the scope of impact as we continue the investigation.
Posted Feb 20, 2026 - 18:45 UTC
This incident affected: Cloudflare Sites and Services (Magic Transit, Cloudflare One Client).