昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
* g9 l8 u- O# i) ^6 q6 W
% r* o/ _+ v) @5 C/ O事件整整影响了27 分钟
0 {# X$ p2 m3 O& v" }* k7 ^9 \- g7 t% U1 o6 u. h) o9 @% f
这种全球性的502 应该不是ddos 引起的4 @$ S% z5 H+ E0 l2 ^
G. v) @1 w% t5 ?: y0 d, F2 \9 ?0 y
后来看cloudflare 的email,应该是内部程序的问题) O% d7 M# {& W
( l2 }: a1 j( D3 b. v, }
Dear Cloudflare Customer,
, _+ B1 z# G7 t/ }7 H& |) U6 z9 S, l( I
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. I1 x: O8 L* ^, ~; S+ X
\' X: [0 [; @- j$ X, yThe 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 d- {+ Z& N4 ^+ f# I, b! Y; D, D1 m& V% C
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. , F' f# ~4 _2 M, y" g8 G( }$ S6 q
0 ]/ }! T8 Z9 q
~The Cloudflare Team
1 x$ ?1 G. X+ l! [) c2 z2 h
# i) @/ R" Z$ B8 x* E
$ b! r( B, l2 {) _3 X |