昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
6 I. U' e7 o; ^+ l1 t9 o7 \/ u
事件整整影响了27 分钟8 ~, T8 e5 \; T% c3 y, q
/ @( t; H+ U7 r- k" F3 ^1 J
这种全球性的502 应该不是ddos 引起的( c1 o! P% X) t% U/ m) |. c
( F7 r; l/ |' l! N
后来看cloudflare 的email,应该是内部程序的问题
! ]1 K2 Y# j8 @8 `. O/ H) ?/ b9 E- a/ _0 h0 R
Dear Cloudflare Customer, ) ] g$ S0 K' x, i/ k$ e8 z
2 ^* x6 k5 t3 a: Z* v5 I% J$ t0 X5 |Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
+ t, u2 s. ~2 z$ @6 B Z* G) u4 C- I) \1 M+ U& [8 q% F0 r
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.
# z5 q* l& a0 y6 o8 v6 |
. A/ l- {( A* {) t# O4 K) VWe’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. : A8 Y% d' @4 v, B
( `( {- y: S: ?" U; s5 | p
~The Cloudflare Team
) O/ u7 J8 v" C9 G% u# u9 ~
. F* O4 J* s. b+ n0 L7 @, ?: I' y8 R+ f |$ f
|