昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情/ |0 g* K( R' ~/ v3 K4 X, s4 x
H7 u+ a- [+ n事件整整影响了27 分钟
3 {8 R5 R6 p7 m# P9 P6 M/ Y3 \* Q% k+ N' h
这种全球性的502 应该不是ddos 引起的
& f/ z/ h- ?0 _, R1 f; B2 f9 I4 E6 m4 V( t' k9 ]
后来看cloudflare 的email,应该是内部程序的问题
' C v/ G% n/ @. _- q$ `$ U, j4 T! {8 o# ?) |5 J! _
Dear Cloudflare Customer,
0 M, }9 y: A7 x) d1 v. X+ Y1 b, f# b
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
1 m& O7 t2 Q' ~1 b5 c' [ [
. R9 Y0 a; P' ]5 h8 _/ G: g* m: ~4 v, u; X6 kThe 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.
" }$ H7 _7 `" B3 B, g; M& R- |! g X, K* f! c8 v Z5 S
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. 2 \4 J3 G3 ~4 D0 o$ B
P3 ~/ \3 u$ h
~The Cloudflare Team
+ w: _/ R8 I( c( R7 B; q* {& a/ z4 Y7 K# ?+ W! z
. I6 l0 w; [3 P/ Z5 U3 L6 G7 e |