昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情9 h% O% b8 ]8 V# K! V2 |' E
7 V' {+ z0 i& c" M
事件整整影响了27 分钟5 E* q8 {9 z; s. w; }- o
- }5 b) t! q# U3 Q1 q& T这种全球性的502 应该不是ddos 引起的 1 m q1 _+ `$ z* k" a7 n {0 J0 b; u: ~- z* u# ~$ z2 k后来看cloudflare 的email,应该是内部程序的问题; {1 V' c( R9 n% E7 z
/ O/ {: N. t5 N Y' mDear Cloudflare Customer, ) g! E3 x- A( n$ a5 @4 y
$ y2 s- `1 P- Y! k: I$ h' R" EToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. p+ Y! p5 f& w% O! m( S $ l# w2 F& A6 Y! x9 vThe 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. 5 E$ ~. |8 c% R1 s2 D- `
1 m- m) E* k+ q# V7 eWe’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. 5 T; H5 L3 z8 m9 U- g
' I$ _; l2 w% b! @6 p) O* p
~The Cloudflare Team " G9 A) a, }7 [1 l: \