昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情! V( U3 N. Y) t
5 V+ M L* {4 s1 ^) j* C: }" p
事件整整影响了27 分钟0 b4 d# Z1 K( T& \- I7 _
9 ?; E6 d1 r: W" q1 }
这种全球性的502 应该不是ddos 引起的 ! |- ]" V" ?# y) E$ a; h; s . K( O: v% d/ `: W后来看cloudflare 的email,应该是内部程序的问题' w0 b* s& B3 I" L% H( l" Q; b
+ _3 W" y) q0 K5 I- b
Dear Cloudflare Customer, ! K. G+ N+ a) A m1 y" O9 _: @0 W
' R( Y9 U& \) H. _: E7 K, tToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 2 a6 [7 e$ p1 i6 S% t* h% \" B
4 U& l1 f, g, [# m& BThe 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. $ d2 s I8 m' ]7 m
6 W7 m" [* U3 X0 Y' G& q! B
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. - ]$ [4 F N% E3 H
X. R Z; L; s$ p. o/ z1 |
~The Cloudflare Team - K5 u3 B4 g! { f3 U. T
) @% ^ J6 p1 A8 U3 q6 A) ~ 3 r% E7 G' N/ F# k- b# Y