昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 2 G8 K1 r W1 z1 d( u6 L( d4 X( m! e0 v
事件整整影响了27 分钟 / i0 P. N1 L: d1 A' W7 f W9 ^: t6 l! F) B
这种全球性的502 应该不是ddos 引起的 * i0 c" {# ~3 h# }: G: K " o9 |2 S2 {& C& H9 `$ H) e后来看cloudflare 的email,应该是内部程序的问题 ( {, F( b! p. Y$ C% A% [3 P 2 O1 [3 [9 i' e) `. u- E8 h/ k4 t7 Y- NDear Cloudflare Customer, ' {" ]+ F6 V2 M# W; ?1 K0 m
1 l; E+ r$ q9 V# E2 [
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 0 N# b# a, Y- S, y( p- K8 T' h, q, F1 R; j. z 8 a+ f& u3 B BThe 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. # h: Y- J' |* X8 Q
+ A2 B- d9 f+ ]- h+ {* @/ ]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. ) ~/ |, P U* D / T: g" ^" z4 x~The Cloudflare Team $ P) b& l) n! O* H8 o / Z; R5 i1 g/ o) Q, ]2 t7 y& L: o' F2 N( Y3 j/ v+ \# P0 a