, ]9 F9 U3 m( tDear Cloudflare Customer, ! a5 L N J* }) w
% e- p2 b D9 X, I! n6 f
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. & y- ]! W, t- A) y' L/ ?! p( m9 v6 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. 1 \$ Y( N; a0 A/ G
. J }$ a" {% _4 _0 `4 I- cWe’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. ( b& l" |6 X2 k$ b: }, l+ G* ?9 y8 d0 V$ C
~The Cloudflare Team ; _" U5 i3 a+ D7 n8 c ( Y) t3 Y+ l6 G: h3 q1 G& B# v( h; p& Z/ `& @, `" H