昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情; i, |, X: T3 Q/ `5 F/ ^' W5 @
% Y9 R' a5 s2 }" F事件整整影响了27 分钟
( j5 ]7 I8 c( B& V0 g2 k) z$ [6 A( Q6 Q7 P# Q* V, v( Y" g
这种全球性的502 应该不是ddos 引起的
8 z6 {3 d$ c! l9 X. c2 n$ g' v" {) _
后来看cloudflare 的email,应该是内部程序的问题
" v$ t2 d6 u6 k0 }! L6 ~) I6 L9 b
) Z* q& P1 H" M) n) t: j# U% ?Dear Cloudflare Customer,
- ~* b+ t/ V, a2 q5 U1 R- w) w$ e5 W: ^2 ]5 a/ R, e
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
; q* _5 ~3 `$ Y
, O2 h8 F, u! A% |. uThe 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. 2 Y. d$ D, j# F3 t
1 z+ C4 |7 B6 _: ? M
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.
7 `5 Z6 r/ y+ h) V- B# J0 ~0 E
# ]4 y8 k. N& B6 R( X( g~The Cloudflare Team
9 [/ N1 u( k% [# d# _! F
! o! D9 A7 z9 x; _6 }7 k V4 A8 X; ]0 R" K/ j
|