昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 ; r$ t$ V+ f1 ] 0 A( w/ H9 s2 |- q, w* ~事件整整影响了27 分钟5 L6 ]5 O" V# V
& M# `1 O$ |0 W2 N这种全球性的502 应该不是ddos 引起的$ ~: U: f: z! R0 x) Z5 b* S
' v* L: v+ Y( ^% x' a9 u% h$ C5 u
后来看cloudflare 的email,应该是内部程序的问题 ( j1 K7 L5 N; Z8 s! f, t' ] , J8 y$ ]: {/ Z, e/ J) [9 @Dear Cloudflare Customer, 7 A+ v6 ?- O! x6 p
3 }7 H. f& F% O/ `* p5 f; H
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 8 I0 h1 ]7 c$ d7 V
2 S. m' |: [4 @. hThe 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. 8 u' z4 s7 Y. j! a; ~
; B/ E9 B1 K2 \8 [0 }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. & \; r# M- b6 I6 i, R* w# C8 \% ?- ~% b) P3 w! }. M* D7 H
~The Cloudflare Team : F) N$ g3 {1 }! ^0 O8 m ?4 J. J. f8 Y+ k s( }- y3 u, x. s! D" s' k3 {