昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 $ x8 Q' h: A0 N- X) j T# w$ |! F% n- Z7 Q8 p: ^+ P. A g
事件整整影响了27 分钟 l7 R( i! z6 j, f. a# G ! Z& X( ~2 `0 E1 d这种全球性的502 应该不是ddos 引起的 0 g! D7 u$ Y# h( a2 }0 w t% g4 v4 C4 N+ a( k
后来看cloudflare 的email,应该是内部程序的问题 , H7 Z) P8 Y8 p7 U% G2 B0 r 2 X7 L& x. m( O" t4 z$ V* xDear Cloudflare Customer, - p8 _, v$ D8 k( j+ x* ^ 5 o/ f' |: [7 B+ v& RToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 6 q7 ]" y: d* K8 K! H+ H
' F' Q; E' @0 [7 |! }6 L0 ?. vThe 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. : u, m$ C/ I7 ~$ b/ W/ b! {/ e
' {7 ?- I8 J: C4 ZWe’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. ' P1 P2 H4 m' N/ }; i) ?% \$ L 7 s( N$ t8 \3 |~The Cloudflare Team 0 {7 O" _0 C6 K1 d6 ` k : A& N1 ?% k0 k& _! m; }% K( [9 Y 6 F4 Q6 O, M2 D6 |5 I- N* w) A$ l