昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 - k, a. W# _5 C- I9 {& h7 ]" G. M8 \5 ^" \' N" E8 a1 m6 g# I
事件整整影响了27 分钟 3 G! H7 S* m& r* B) Q 7 o, s& a+ t: N" ` ?- V这种全球性的502 应该不是ddos 引起的 0 ~/ _0 i5 h3 w; t1 ]5 N( K5 t! [9 P- u/ U+ h* p/ L. i3 Z
后来看cloudflare 的email,应该是内部程序的问题 ; c1 { p$ k9 u, w 8 @7 C6 J% t c0 FDear Cloudflare Customer, & M% A6 k# @: H' u" N9 L 8 G$ r+ u: |5 m+ PToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 2 M5 c& y0 ]; n2 x5 @, z ~4 s# c( I r: S# R( j- e0 Y: v
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. l& V+ e1 F T1 o7 ]! u# v2 l) m0 @. w: D& R8 ]5 r
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. - ^3 x1 u0 V% i e" R R1 s
3 Q+ u* j' s# Y4 o~The Cloudflare Team * `, [9 ^( ~# E+ |% r- O' T8 G* @8 m+ Z1 e1 r
7 P- M2 |* T) u7 |: B- _$ T