Cloudflare is investigating connectivity issues

lowCloudflareFeb 20, 2026 18:45Duration: 5h 6m
network
Network / Routing

Summary

This incident has been resolved.

Impact

minor

Timeline

Feb 20, 2026 18:45

[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.

via statuspage
+24m
Feb 20, 2026 19:09

[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.

via statuspage
+10m
Feb 20, 2026 19:20

[identified] Cloudflare is continuing to restore service to customers. Cloudflare has also identified a way for impacted customers to self-resolve impact by readvertising prefixes via the Cloudflare dashboard. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix for details on how to advertise a prefix.

via statuspage
+26m
Feb 20, 2026 19:45

[identified] Cloudflare is continuing to work on restoring service for impacted customers to what it was before the outage. Customers can self-mitigate by readvertising their prefixes in the dashboard. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix for details on how to advertise a prefix.

via statuspage
+49m
Feb 20, 2026 20:35

[identified] Cloudflare is continuing to restore prefixes to their previous state. Customers are still able to restore service from the dashboard by readvertising their IPs. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix Cloudflare is aware that some customers are unable to reload their IPs through the dashboard and are working on a fix.

via statuspage
+15m
Feb 20, 2026 20:50

[identified] 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.

via statuspage
+1h 26m
Feb 20, 2026 22:16

[identified] 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.

via statuspage
+48m
Feb 20, 2026 23:03

[identified] 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.

via statuspage
+35m
Feb 20, 2026 23:38

[monitoring] Cloudflare has enabled the remaining IP prefixes to their previous state. We are continuing to monitor for additional impact.

via statuspage
+12m
Feb 20, 2026 23:50

[resolved] This incident has been resolved.

via statuspage

Lessons Learned

Cloudflare has experienced 59 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to network have occurred 48 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.

💡This incident is categorized as: Network / Routing. Consider implementing preventive measures specific to this failure category.