Cloudflare·

Cloudflare outage: one regular expression exhausts CPUs worldwide

A new firewall rule with a regular expression that backtracked heavily maxed out CPUs handling web traffic across Cloudflare's network for 27 minutes.

ResolvedEnded Jul 2, 2019
Security:
Explicitly ruled out
Started
Jul 2, 2019, 13:42 UTC
Traffic and CPU back to normal
Jul 2, 2019, 14:09 UTC
Duration
27 min
Full recovery
Complete
Geographic scope
Global
Last verified
2 sources

What happened

Systems and services affected
Cloudflare CDN and proxy (HTTP and HTTPS traffic)Web Application Firewall
Kind of failure
Software defect
Sector
Internet infrastructure
Provider report
Published
Status and recovery
Resolved. Traffic and CPU returned to expected levels at 14:09 UTC after the WAF was switched off globally; the WAF was re-enabled at 14:52 UTC.[1]

What caused it?

Root cause: Confirmed

A change to Web Application Firewall managed rules contained a regular expression that backtracked heavily and exhausted CPUs on every core handling HTTP and HTTPS traffic. WAF rule changes could be pushed globally at once, unlike Cloudflare's staged rollouts for other software.[1]

Provider report: Published. Cloudflare published details on July 12, 2019.[1]

Was it malicious?

Explicitly ruled out

Early speculation about an attack was dismissed once the WAF change was identified as the cause, by 14:00 UTC, according to Cloudflare's report.[1]

How the failure happened

  1. 1TriggerWAF managed rule change
  2. 2FailureRegular expression backtracked
  3. 3SpreadCPUs exhausted
  4. Affected2 services and systems

Evidence for each step

  1. 1
    WAF managed rule change. Rule changes could be pushed globally at once[1]
    Starting point.
  2. 2
    Regular expression backtracked[1]
    Led from step 1: Stated in a provider report or official record.
  3. 3
    CPUs exhausted. On every core handling HTTP and HTTPS traffic[1]
    Led from step 2: Stated in a provider report or official record.

Only steps the sources state are drawn. Affected services are listed under What happened.

Explanation

Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.

Plain language: what happened and why people were affected.

On July 2, 2019, websites using Cloudflare showed errors for about 27 minutes.

Cloudflare added a new rule to the firewall that inspects web traffic. The rule contained a search pattern that, on certain inputs, made computers do enormous amounts of work. Every server running it maxed out its processors.

Firewall rules were pushed everywhere at once so Cloudflare could respond quickly to threats, so the bad rule reached the whole network immediately.

Confirmed and unknown

Confirmed

  • Confirmed
    A WAF managed rule's regular expression backtracked heavily and exhausted CPUs on every core handling HTTP and HTTPS traffic.[1]
    Said by: Cloudflare · Evidence: Official
  • Confirmed
    The standard procedure for rule changes allowed them to be pushed globally, bypassing staged rollout.[1]
    Said by: Cloudflare · Evidence: Official
  • Confirmed
    The service was down for 27 minutes.[1]
    Said by: Cloudflare · Evidence: Official

Denied

  • Denied
    It was an attack.[1]
    Said by: Cloudflare · Evidence: Official

Still unknown

No open questions: the provider has published a full account.

Timeline

Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.

  1. First observedJul 2, 2019, 13:42 UTC
  2. AcknowledgedJul 2, 2019, 13:45 UTC
  3. MitigationJul 2, 2019, 14:07 UTC
  4. RecoveryJul 2, 2019, 14:09 UTC
  5. ResolvedJul 2, 2019, 14:52 UTC
  6. Incident reportJul 12, 2019
Jul 2, 2019, 13:42 UTCJul 2, 2019, 14:52 UTC
  1. First observed
    WAF rule change begins deploying automatically.[1]
  2. Acknowledged
    First alert pages Cloudflare's team.[1]
  3. Mitigation
    Global WAF termination executed.[1]
  4. Recovery
    Traffic and CPU back to expected levels worldwide.[1]
  5. After the incident ended
    Resolved
    WAF re-enabled globally after the fix is confirmed.[1]
  6. Incident report
    Cloudflare publishes details of the outage.[1]
  7. Start to: Traffic and CPU back to normal27 min

Related incidents

Links stated by providers or officials carry their evidence label. “Similar failure” is a comparison of documented causes, not a causal link.

Evidence and sources

Grouped by type of evidence. Numbers match the citations above.

Primary: provider and official sources

Published by the provider or agency itself: incident reports, status records, advisories, statements.

  1. 1.
    Details of the Cloudflare outage on July 2, 2019 (opens in a new tab)
    Cloudflare · Provider report · Published · Accessed
  2. 2.
    Cloudflare outage on November 18, 2025 (opens in a new tab)
    Cloudflare · Provider report · Published · Accessed

Last verified against these sources on Nov 14, 2026.