昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情4 w8 K; ?1 e B
; r- r. \4 f: Z* l
事件整整影响了27 分钟 * {3 d$ l8 k" O, x% r- `8 o4 w. z' l9 _0 N( b: X7 ]
这种全球性的502 应该不是ddos 引起的! t" A3 |0 d! A% Y! @4 i
. i4 \# @& C" `! a% E
后来看cloudflare 的email,应该是内部程序的问题2 `0 k4 l8 P3 v G) e/ V* \
3 j' g( y9 |: u: g" X3 {" t' DDear Cloudflare Customer, , T. o; s: M- o; L
0 R6 I2 P; n/ U+ d# ^* ZToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 6 N+ J7 u% J& ^0 n0 @! `! N - B u: G6 [, GThe 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. & S) `8 Q0 r, b4 n* w y/ V j u9 G+ N0 d) 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. $ a( I7 n8 e: a& {" z. T# s2 [& g' u' w/ t' F9 P$ U6 n. h
~The Cloudflare Team 1 s1 I: f3 z- R% ` j4 \0 K
2 s( V' Y1 t, n Z# `- F
1 e% Y, O- X( E. o4 E, c