昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
- G, n; K; [: G3 R6 m( f( d3 B# E& z% i! |" K
事件整整影响了27 分钟
1 B, n. O. p0 z: L0 d: m) b& z
) ~3 p5 b3 b9 K: Z6 d8 ~, W这种全球性的502 应该不是ddos 引起的/ Y% ~6 D1 M& _. [5 t1 a2 ?
2 S1 a8 \! K1 ^, o& ^# `( {后来看cloudflare 的email,应该是内部程序的问题0 o3 W6 F: i. D) [# H& w: `4 R
5 X' b/ v0 H4 pDear Cloudflare Customer, 5 j j& r) v. c3 L& [+ A6 w/ c' ~
* \" F- E0 I( m$ I }, m
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 2 S! r7 t/ b( w% Q
, }% B2 m. n) H) F3 B/ {$ i2 b# v
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. ) ?* U" m% W' S4 n% u( T
, j8 X9 L" `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. + A! z: U% I- ~- A( f7 `/ C# P, s
; y- t* _3 X/ E0 I9 b, s~The Cloudflare Team ! V7 g" A) ]: a7 {# A& l7 q
; ^& h6 [" l; ]; u! w1 [
! _8 h7 I8 B2 S8 B7 q. v |