昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情 7 f. U5 W- z! t: R+ x' `, [$ g7 }. ?: I9 [) G. J7 `0 J
事件整整影响了27 分钟0 d3 o, L5 e: L6 Z t" J
$ c& G3 v' `" G
这种全球性的502 应该不是ddos 引起的 6 y9 z( j5 E$ ` A& N / n( T) d2 {9 P" [0 M后来看cloudflare 的email,应该是内部程序的问题 % k9 f. H# h6 W: ^6 B! O; Z z$ G5 A1 i7 p7 s4 F
Dear Cloudflare Customer, 5 n/ T7 S7 d3 B( ^
6 {$ \ D, T7 l3 y& l# _9 @) k
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. ! s7 N3 G9 k) B) _- I6 l9 F
. Z( s( ] o% q! G, _* i
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. ) z; E' t8 y/ t# J7 i( C ( _! ^# N8 i* ]# SWe’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. 9 o6 S6 n$ O- j& q! j, \# U0 o& R. ~- A
~The Cloudflare Team 2 |5 v7 i5 {+ q6 k2 A) Q) t d- S* Q; Y% T4 {# N
* `$ e2 J' ]/ g6 o, N