8 u8 M0 U3 d$ q6 ?8 Z5 o3 ~9 JDear Cloudflare Customer, 9 y: o9 h! U3 l* n7 o0 `4 E : l2 q$ j; n. l aToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 2 [9 u p( b# |. z4 @& r9 G
/ P" _5 ?5 [+ v9 t* Y6 M: `! d: wThe 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. 0 W& @ L1 b) r: B# c4 P) N+ |/ ?9 t2 M! J* D
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. ! g5 m3 Q0 N* n2 ?2 l; S6 F* A$ A* @7 }2 A4 |
~The Cloudflare Team 4 ]$ N+ P! c& I* O5 h" O