昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情* V, g9 v' e6 _" C& q) ~: r
+ y" S. w3 x/ k. P$ Z
事件整整影响了27 分钟- m, W# n; n1 X2 B1 D6 {
; P' G! t. O k5 s* ?
这种全球性的502 应该不是ddos 引起的
6 C7 R$ b( f" K k' f T$ k5 x" x% j* v1 u& ^
后来看cloudflare 的email,应该是内部程序的问题/ N( v4 c, Y, Q% l6 A, I
+ M# i& x8 u% r4 cDear Cloudflare Customer,
# h" ^+ @6 C1 f+ s- u2 n
9 L/ o5 V( k3 s% jToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
9 R( r" m; K9 G2 U! T! N3 D$ G' H1 g) }& B
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.
2 o: r8 d v" L' H( ]( q* C2 p( k5 {. A+ g2 k+ l+ p3 ~/ Y2 @
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 t- [! ]7 Q; j
" Y' a* L* a) \. E& X
~The Cloudflare Team
6 d U* x7 C8 m3 S0 H8 ]6 ^7 a) ]( ]4 K
, e1 A8 P% `% |$ p, M- U' R8 h |