昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情' d& d" F5 [5 ~8 P1 F y
0 w6 g/ J: I; C! H" i6 y事件整整影响了27 分钟 ' W+ c/ `1 q8 Y# L& m8 o7 S- z ' J, Y% J+ t! N这种全球性的502 应该不是ddos 引起的/ m2 ~* a4 F0 D' K0 Y" z
/ c5 B2 g! ]2 ?2 o8 w
后来看cloudflare 的email,应该是内部程序的问题5 g4 o4 M) I, d
# F$ s- T1 C+ d
Dear Cloudflare Customer, + {) m* f6 J$ \3 t# d- Q
1 e3 r( c, Q# D+ g' s2 G. w) CToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. , m2 [7 q0 d, t; i1 a( l . D5 f& I6 S6 h* n! e: 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. ! C: U, |/ h/ `3 K ) c7 {# [: f g8 y3 E. @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. 3 d( @" p9 S T) v8 J6 k1 v3 T; E6 O% B; f; s1 s2 P- @& n: ^! }2 J
~The Cloudflare Team d% U& J: I& F 0 Y* m4 Q" o8 _5 D1 Y" {: j% N' K& J/ C3 M. j