昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情3 ?# r) m, c' G M
; F" i: |, Q& M2 T* D" E& K事件整整影响了27 分钟
8 M$ Z1 [: E8 w
4 ~* Y b( l* S2 j这种全球性的502 应该不是ddos 引起的
8 h7 \& a6 q) }& N% Y. y- k$ _6 y9 I9 d' r$ p- e. m4 l8 X
后来看cloudflare 的email,应该是内部程序的问题. `5 E, g$ E) ]4 C+ } @* G% K5 v% ]
: S# P, K* b6 B# X' kDear Cloudflare Customer,
2 T$ m# v$ o" G5 v/ Z8 B3 i2 b. M* Z3 }0 s
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. , w6 G: n5 @, t$ t
. v8 |: K3 z; b; Z, K9 XThe 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.
7 Z0 h3 g. _1 p) Q3 {$ X q; M6 g# A
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. * F) g* H- E9 Y3 R/ b6 w) }. s
) N, h4 B6 \" @
~The Cloudflare Team
6 r: }$ t3 a! @$ T: f
3 @% y( x; s/ p0 ?& O- K9 ^+ u6 S) W3 Z: p: n0 b4 i
|