Home / Companies / Cloudflare / Blog / Post Details
Content Deep Dive

Details of the Cloudflare outage on July 2, 2019

Blog post from Cloudflare

Post Details
Company
Date Published
Author
John Graham-Cumming
Word Count
4,537
Company Posts That Month
12
Language
English
Hacker News Points
698
Post removed?
No
Summary

On July 2, Cloudflare experienced a global outage due to a poorly written regular expression that caused CPU exhaustion on every CPU core handling HTTP/HTTPS traffic across their network worldwide. The incident resulted in customers seeing a 502 error page when visiting any Cloudflare domain. The company has since taken measures to prevent such an occurrence from happening again, including re-introducing the excessive CPU usage protection that was mistakenly removed and introducing performance profiling for all rules to the test suite. Additionally, they are switching to either the re2 or Rust regex engine which both have run-time guarantees.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.