昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情& m' [& Y- X0 j$ v. b5 M* S% B( K6 F
' R3 o8 A1 B/ a, s% Y$ G8 P事件整整影响了27 分钟 ; L2 f; U9 h& p. g$ U7 L1 u& ~7 f( S3 Z
这种全球性的502 应该不是ddos 引起的 j, q$ i) F E# n* c
. j+ E R& u p x6 B; r后来看cloudflare 的email,应该是内部程序的问题 # g2 B8 N" @8 f; R/ a; }& z 0 y6 u p( F2 R2 `8 k& Y/ VDear Cloudflare Customer, " E) l% E9 A, E/ m1 o7 l) R' X' ~/ L7 L' W+ n4 T! V" i# E2 i
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. / h1 `; X3 B; d" j0 s4 O. }: \' r) h0 @ n5 X
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. + ~1 O* A9 \6 e5 }# w
* C0 X( P6 ]2 ^+ k
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. 6 V. h8 |% t1 R' t& @4 @
: N; K+ G, Y6 [* A
~The Cloudflare Team 4 O! n7 G8 t: e) i' |' h2 S! }