昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情7 ?& v1 R1 B& s0 I) a0 O1 c% A
5 T* e1 ?- I/ p8 g
事件整整影响了27 分钟
# p7 I' C( C1 _$ j. b; l
; ?* r+ Y$ j. J5 o; s3 H这种全球性的502 应该不是ddos 引起的1 R2 q! g; r, L1 J3 U M$ C
/ S' [7 w, X0 V. K% X后来看cloudflare 的email,应该是内部程序的问题
1 R$ `* l8 Z0 P @& Y; e( g1 Y7 I8 b5 E" f8 W: s9 ]; d
Dear Cloudflare Customer, % Y0 o4 I# r e4 [: _
+ t9 { h8 e6 K8 E3 m8 C7 ~
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. % G h) D; P2 B1 _# u
B/ C ^5 z7 u8 E& h! D
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.
) S! M, @* g ], z, O. R
6 c+ m- M4 q$ {3 t1 z0 y2 \# 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.
5 r8 R% r8 S6 K: [* R. P
$ X5 }! }; u9 _* d9 Z; {~The Cloudflare Team
% ^: X; M5 f& k) r+ x- g1 X7 _& n/ B6 N, r% Y! f; _
4 n6 j: v; W9 D/ g3 k |