昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 5 G+ v- F4 d" R0 ]- j2 C1 {) w( t& d
事件整整影响了27 分钟 % q& A ^2 v" i1 E : R& Z/ s# |7 D: m这种全球性的502 应该不是ddos 引起的 * S* q, k. F6 \ , k& E- G9 R* u6 a5 D) Z0 ?- P y后来看cloudflare 的email,应该是内部程序的问题" k0 H3 N$ W; y. e
4 I3 Z! ]2 p' {+ N7 u }Dear Cloudflare Customer, $ y$ o! ?+ a, |1 C
4 B* @6 d( T9 V) K0 G3 T
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. # h$ n# r V! {& a- B8 v' h7 r Y. v, M6 L- BThe 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 \/ x& v( C; L/ W4 _* a
2 f) B" o3 K3 Q9 uWe’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. 1 \7 M, Y0 O$ i* W1 u( y1 {- S7 Z2 U
8 F% Y* O0 w1 E# s' M/ c0 }, Y6 y9 j
~The Cloudflare Team q9 F6 I( b$ ~2 J
$ c' _) h' {) x* j! a: [+ Z / ?( Q5 X5 C5 ]" c$ J" g6 W* j: Z+ G