昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情, _# m# G0 D4 U/ S' M2 d+ D
3 ]; s8 ]0 w& e4 ?
事件整整影响了27 分钟& N: q ]8 |& H. ]% _; {* {
* t! r& M+ l4 s( x
这种全球性的502 应该不是ddos 引起的" z0 \' b: a; G( W6 U
4 M5 V2 A, F! ?- {, B v, ` S/ n后来看cloudflare 的email,应该是内部程序的问题 2 F! y# C2 O. p5 {, x# H1 t( S 7 l5 h8 @: |! t6 |9 XDear Cloudflare Customer, ( O: A6 x/ R/ B9 o& d4 ]
5 H) p0 {/ ?( L0 w0 {# R: S! d% k
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. + B. f( W: O5 U# ~+ ?/ y* P 0 }7 k" m2 x8 @* S; g- a7 PThe 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. 8 t/ |7 d# w) B. Y2 w
: m( x h: z9 j% R- _
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. ' N# A+ Y. n5 [/ }( J 0 d+ c1 n3 z/ ?; w9 Q5 o~The Cloudflare Team ' O- V) J% W2 E3 e7 F3 M* [
+ ^+ x4 ~3 i+ c/ B$ |' {7 N" S. ]2 H, K j! T w4 m/ `- h' U