Web, Payments, Bytes & Ventures

WPBV Radio

Tune into tech and money.

Cloudflare outage, 20 February 2026

The Cloudflare outage of 20 February 2026: what failed, why, and what Cloudflare changed, from its own incident report.

Provider
Cloudflare
Date
Duration, hours
6.1
Cause
Software bug
Regions
Global (~1,100 BYOIP prefixes)

Cloudflare BYOIP prefix withdrawal outage (20 February 2026). The disruption lasted about 6 hours 7 minutes, according to Cloudflare’s own timeline.

What happened. A change to how Cloudflare manages BYOIP addresses ran a cleanup sub-task whose API query passed ‘pending_delete’ with no value. The API server treated that as a request for all BYOIP prefixes, so about 1,100 prefixes were withdrawn via BGP and some service bindings were deleted.

What changes. Cloudflare will standardize its API schema, separate operational from configured state with easier rollback, and detect overly fast/broad BGP prefix withdrawals.

Questions

What caused the Cloudflare outage in February 2026?

A change to how Cloudflare manages BYOIP addresses ran a cleanup sub-task whose API query passed ‘pending_delete’ with no value.

Which services were affected?

Cloudflare BYOIP customer services; one.one.one.one (1.1.1.1 website).

Read how shared dependencies spread a failure in why one cloud outage can break unrelated apps, or browse the outage archive.

Started (UTC)
2026-02-20 17:48 UTC
Services affected
Cloudflare BYOIP customer services; one.one.one.one (1.1.1.1 website)
Incident report
blog.cloudflare.com
Sources
SourceLink
Cloudflare incident reporthttps://blog.cloudflare.com/cloudflare-outage-february-20-2026/
WPBV Radio

What are you looking for?

Search by headline, topic or keyword.