昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情! i8 Z. o0 l% [$ v
. x+ t5 s2 R: N3 v0 U+ I) C
事件整整影响了27 分钟9 \8 q( f. J* M+ T" r& x9 S* L
/ h W# o; T0 ?$ ^' x
这种全球性的502 应该不是ddos 引起的" @# [5 z- k( l' h& b/ m1 S: k7 f
) c( V9 v ]3 E- \
后来看cloudflare 的email,应该是内部程序的问题' i+ T6 C/ d- s) M; C+ r$ p
4 ^: p9 Z" `6 y6 r9 \/ tDear Cloudflare Customer, 0 i, w, b2 E+ D! X 1 R& N* s5 c3 H8 y$ iToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. % H1 T6 K7 j+ ^/ \$ ?# {2 I$ f+ _; A2 D- ^
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. . T ~3 y( Y: o! z6 f/ A8 A' s& R8 Z8 C
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. + ^, t% d: y2 e L
3 |6 h E- L, O4 [+ l4 {1 D5 S~The Cloudflare Team ( I4 `( E! e/ G a, p; h
+ M4 W' c1 [5 a" z: C5 x- n
! r8 l3 V9 i; c0 `' C% E