昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情) B, \ w& N8 e0 |7 r
% Y& i$ P: U4 I, ?5 u事件整整影响了27 分钟
! ?2 q8 D% i, K. c( V: C' ?( p$ u% s5 t0 Y& g, E
这种全球性的502 应该不是ddos 引起的
4 _# k* ~) c! ~7 l7 r0 Q" B$ k4 p7 C" T* G
后来看cloudflare 的email,应该是内部程序的问题0 K6 f. v, P. F1 M) l5 p
5 F9 _+ q( O$ K/ d7 J! l2 r
Dear Cloudflare Customer, - d3 \8 u& z U- p2 B; K! k9 V4 Z
- d# }. X9 k; _
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. - \% S, C8 Z5 c
$ X) U; _8 s1 t9 Y. t4 R p6 l6 k
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.
$ {' s0 R! {4 c7 u$ y9 \
. O4 R$ b, g6 [1 _! eWe’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. ; r7 `& M. [* z- j+ Q5 b$ F* U
5 @9 e2 n$ ~* v, }1 r7 b* N
~The Cloudflare Team
5 Z! I: @* U7 S' b* Q3 e; b$ G9 u; _8 L" d4 D8 L) I- A/ S
8 A" g+ D6 Z% h9 q
|