昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情3 T. G: L0 v; d7 W; t* V
6 V1 V9 y( m ?事件整整影响了27 分钟6 u8 t& ?" N. V9 I; n- {
* J* f. F" u, \4 c这种全球性的502 应该不是ddos 引起的 2 s$ h9 y/ C8 d9 r) G . T/ A ~7 P) a: {7 j后来看cloudflare 的email,应该是内部程序的问题 $ H# _1 i2 n. C9 x( \2 t# C; S/ W4 J
Dear Cloudflare Customer, 8 |' m& s: D6 i M0 i5 l- P7 w) j 3 G6 z- {9 l7 \5 k3 m k8 b2 JToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. " w6 I6 N2 u$ R7 ~; f' i; w/ m* o% I% U
The 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. $ M) x& Y4 V I$ b& h # Z: C" s7 l3 eWe’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. 2 \2 f6 Y+ Q5 j: ]- z' d7 l
9 n. b9 R) I0 J6 G! r5 m~The Cloudflare Team 9 M2 f4 O9 {2 d+ o: x% ~; U, p2 D0 z; p7 _ s( R S2 v
3 m! H A) W B6 c* V+ H