昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 @; M5 Q+ N. {1 L1 _% R4 k1 a $ \; |( g/ F$ m+ N, y9 t- _" _事件整整影响了27 分钟 $ l$ |- @& I4 {0 B* Q, Y& f9 w7 b. f: g1 n
这种全球性的502 应该不是ddos 引起的0 J+ R+ m, \, M8 `8 R7 n3 M. b
% D5 F- Z( F3 `* n) }7 r, l- P
后来看cloudflare 的email,应该是内部程序的问题 : Q8 |( | b i0 G7 r5 [ - V# i: J+ O- u% MDear Cloudflare Customer, ' V8 f# H' D' b, p5 I! w' H2 k
6 b; f0 h: e+ H7 A: W1 @* `2 x; T1 k- K
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. $ J- W- |' O; `& `( ]# f 7 m4 x0 q* f' J( OThe 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. " ~# R% s% H2 [$ R* o( z h2 s" j2 }' N
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. 7 {/ ?; C7 j% \+ F* ?& d; C: }1 M+ n& f6 N
~The Cloudflare Team / ?5 r6 |) k2 E5 e