昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 ! D% Q4 Y; {" r2 l! J : Q- x9 q$ }" x. Y( e1 S( [事件整整影响了27 分钟' K# g* E0 d7 A i6 w
+ U' e1 U$ U1 ?0 D9 _2 j8 w2 i
这种全球性的502 应该不是ddos 引起的 : |. [6 J. D3 j! }2 _& y6 B+ ^3 a " F% Z" e8 v6 L( f8 M后来看cloudflare 的email,应该是内部程序的问题 : B8 D+ y+ P0 _5 c2 m1 ~# d; x 4 n- ]7 m3 t+ U. W& U/ ZDear Cloudflare Customer, ! r6 T& x) h7 h) d7 N 1 |, C/ H0 L2 P$ BToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. ( X9 \6 |& g# ]! L. z$ p/ W, Y
7 K9 @5 V. w$ C$ Y5 r3 j& ]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. % C" ?, o p$ V' l7 F* {7 b
. e3 c! l! D/ `5 W5 @ _& x
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. : }1 z" u) j2 I+ }- O
4 |& J$ [& K3 p' l- h~The Cloudflare Team ! A* I1 S/ q& ?1 z9 }5 C
! r& Z# N7 a: ~5 ^5 E$ d* D, @