昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
+ T; F" n4 d' f. x
* ]8 {/ Z6 m& k4 n0 i5 ]3 O7 F" w- K事件整整影响了27 分钟
' w* M7 m0 J, s" Y
* I8 X8 v3 s7 K. Z2 u这种全球性的502 应该不是ddos 引起的8 w0 x! P) A$ Z
' Q) Q5 K2 m! D" Y, b后来看cloudflare 的email,应该是内部程序的问题. J! X3 e% O1 \+ z: M4 V
' Y% N4 {* c* E2 V5 `: e: a% K
Dear Cloudflare Customer, * C* j: x* k# b; l% e
* K$ K( g% T! S) r; oToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 6 v( t6 N8 _2 n- F9 P3 J
! x/ O9 o+ ?& W( h
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.
r: P. A( S. G: [: c, p. M) `
$ @+ W. }' Y" \: z2 k4 F, [1 J, uWe’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.
# X h$ h1 S$ f n) Q
7 ]3 N" r. N9 c~The Cloudflare Team
% ]/ T$ a& U- w& y( W5 |
: t6 k8 z$ v: t3 `! ^* I N Y1 s
7 J9 _ M: b/ E F: o1 q |