7 g. N5 ~2 _4 O( F" z2 xDear Cloudflare Customer, ) [& G4 Q8 I w; y0 d0 \' P0 `4 g3 `( F L
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. : N/ L/ s7 n) R. d) B2 Q 5 u( X! e" |2 [* i* cThe issue was triggered by a bug in a software deploy of the Cloudflare Web Application Firewall (WAF) which resulted in a CPU usage spike globally, and 502 errors for our customers. To restore global traffic we temporarily disabled certain WAF capabilities, removed the underlying software bug, then verified and re-enabled all WAF services. 6 ]% _- J0 W: A% m* c9 W' z' M$ d+ z( A; Y% ~
We’re deeply sorry about how this disruption has impacted your services. Our engineering teams continue to investigate this issue and we will be sharing detailed incident report(s) on the Cloudflare blog. , t3 k2 ]: A a
1 T" p: g1 Z: f~The Cloudflare Team : D N) c! E' x; x( X! g1 `. h$ ] $ L( U. T6 e& W e9 S " I4 I# s1 ^* G# a: a