昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
3 a" V6 ~4 I, F# L# Z% ^9 j' o) M: q3 I q5 R K9 x. C
事件整整影响了27 分钟2 j o" C% ^2 U" `! ~5 X
. M! ]9 I, J) _! R7 R& c这种全球性的502 应该不是ddos 引起的6 v) K; n! ]1 I/ J, f9 l* b ?" M
6 i' A9 E5 i+ u+ [
后来看cloudflare 的email,应该是内部程序的问题
) H& D s6 }0 c9 g2 o0 u1 f$ h1 A9 D$ F0 g. ]2 K5 j
Dear Cloudflare Customer, $ a- V( r3 D, Y- H$ g2 Q- C
4 l( w0 X3 x# \Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
* V- C) m8 X0 d. e
% I1 Y5 f* I- cThe 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.
5 t: s# J& g% Z; a/ f8 X& ?2 W9 x& F. z5 Z% Q8 V3 R2 Q
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 O' ]& y- M4 `+ X( b8 D) O3 ?1 V# ^ E
~The Cloudflare Team + i* A! @% ?+ S+ W( i
- J( W3 q4 T' R" V+ K, }3 l( b4 S" Y4 g
|