昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
4 e( g% u5 v6 H4 y% E6 K/ l& ?9 O, N. U+ J
事件整整影响了27 分钟
9 H4 Q- C5 S/ A2 {( ~
% `8 ^) d% R2 X; \6 v6 [这种全球性的502 应该不是ddos 引起的
0 ~) M! O% s7 _2 Y# \! h1 B, P, c9 n% ^9 ]: t$ G4 i# O: l
后来看cloudflare 的email,应该是内部程序的问题" U) i: `) p7 ~6 r' l, ]
! h" C8 Q8 l' E; R) U7 [# x) D
Dear Cloudflare Customer,
% ^2 D9 A* P# o% `2 R' l4 J. w. O' c
# Z. u* @6 z- T5 Q" vToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 2 \" Y0 L+ G5 y$ `
* F w' B6 P% m6 ^8 D# m5 W
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.
1 W. Z2 o1 ^$ R
; o& `8 F1 n: j2 [* `. b4 u3 A9 E9 |* GWe’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. % ?) r* g& }# w, G$ q% c
5 j. G2 ^ R# a3 h2 P5 }~The Cloudflare Team
, B. @3 u. k& X( J6 q& V" [3 Y
4 J! b2 Q% _7 j; e* @: w2 B# e
. D% G3 L& Y$ _! G9 m |