昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 ; p2 l" `0 u7 t) j# H/ G; U# a/ l% z. w! C5 \
事件整整影响了27 分钟 6 K% f: h# H9 H0 O: G" L - U0 F( L( B3 Q, {这种全球性的502 应该不是ddos 引起的 + a; {; e8 ^2 P. R2 G 9 ?' m5 c$ s. _- S8 S后来看cloudflare 的email,应该是内部程序的问题 ' g5 b! {# _) a& g4 h- E, r. R% ?% H. w" \0 R) f) \
Dear Cloudflare Customer, : z5 `/ S2 m2 j- ~5 v2 k9 ]- B# Q( D3 x+ p* r/ |& M7 f8 M) r
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. % H5 l) J. k0 \; G) a( Q
! M" f' p6 T! p$ F1 i2 l& xThe 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. 2 x( x3 A* \6 u
! g; g' S# S. q* A6 wWe’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. 6 _2 C+ i& ^8 P. I# j
: R) K, O3 o) W9 p$ d2 Z6 k
~The Cloudflare Team / F+ {; B7 r2 x# c- @' }
; m9 {# F1 Q% n1 [. G7 s2 n
& e1 k. l) ?! [' H; @