昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 / [3 ]3 O3 i5 K, c2 M/ [; R " p9 B# u, }5 T- c U7 p事件整整影响了27 分钟( N0 B1 y# u- p* |" M7 t
8 ^- `7 p1 I' [$ V. T这种全球性的502 应该不是ddos 引起的 / J( Y2 m `1 l 9 [0 i5 g" A( i, B后来看cloudflare 的email,应该是内部程序的问题. V% o- p- f+ l/ H. B, g& |& ~" Y
0 }3 W( b3 X: u5 t1 S7 P" W5 \
Dear Cloudflare Customer, . Q3 y) o/ i" u( S 1 `5 J: `+ D8 a1 _( ~5 Z7 yToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. & V! f7 ~5 u2 C
; T3 B9 A, d7 y
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. : g" ~ N" _4 f
* G& L( f* }% B& X( U- F) I7 k" z
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. * s, y) b2 X# C0 a3 k0 w2 j2 L
S! Q" g+ o8 n8 L# v~The Cloudflare Team % A$ x" r" O2 O2 ~6 W
/ D% x: A/ o3 a1 k& f0 h6 n
% _1 q; H* h- p) o3 O* E