- H5 ]2 J( A% fDear Cloudflare Customer, - F3 U3 {2 o. v0 ~, b8 O# w8 d 8 T- C' \( B; P) h3 ZToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 2 {9 K! d, _# _0 o5 {+ n+ d" n3 i
7 H$ n: v# ?; f, }4 u
The 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. ' s( a/ c) |" d0 B" ^3 p& d
9 C2 T+ g% r# uWe’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. ! i6 u9 U0 D$ ^
' l6 G' {! e4 M- N2 X: d
~The Cloudflare Team " X. r) S- l6 c3 I4 k0 t4 c/ S2 l9 n- A/ w% P" G F0 Z% g$ |( C" _# r