昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情) h: d" a' X* R9 V
, P i7 d3 L+ v+ O5 \
事件整整影响了27 分钟- `1 V. x5 c# u9 s) D9 k
1 [1 ^" [( w1 l. `& e8 g6 l
这种全球性的502 应该不是ddos 引起的1 C0 I5 U7 m4 P
# d8 c3 Q3 J# \9 e. s) ]! _后来看cloudflare 的email,应该是内部程序的问题
' W! i) g0 }# e6 ~# d& L
: O' e' f d- sDear Cloudflare Customer, : W9 p, e1 r# T
0 }( A/ k, [$ M4 E( K* U8 sToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
7 x: @3 @- n* |* k: T
: _* P& d4 g- 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.
9 ^' |. G' u/ l! H% F
S& B% R! b, W* e2 ^4 XWe’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. Y* x1 _# i! i8 G0 E" m6 N, ? h8 `
/ X7 c) \- U7 i: q! a- o
~The Cloudflare Team
4 S% h5 f( j, G/ e5 S+ k5 m5 @. I: L
& \6 K: s" c8 o) D
( u. {# ], f; i+ a! w3 `3 p |