昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
5 ]' b* E! p- U U/ |- Q* G. |* t* Q3 L; n
事件整整影响了27 分钟4 y$ ]) C f( f, I* t# @% k6 X, O$ w
& g, V/ G) ^" w' ^这种全球性的502 应该不是ddos 引起的
5 H* k, S5 r* e$ i( p6 D. t
! C* o& C5 I0 X后来看cloudflare 的email,应该是内部程序的问题
0 |2 ~9 i7 N# H" ~5 }/ }9 w, `/ _4 O& V* Z
Dear Cloudflare Customer,
( j5 @8 C' c8 z. n a. j
9 K# P7 z' A1 l; n: [, IToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. , f+ n, ~; p% k \9 q3 A/ p1 t
1 z5 w% [9 Y, X6 I- g3 d4 aThe 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.
( a* F( c- M& A2 F' k+ I( c) r
5 \" f, C& s6 _% Y, B A6 ]+ LWe’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.
0 q! }1 g; F4 o$ O' z2 S1 {2 r9 r
~The Cloudflare Team
: s3 r$ I8 \* n( s9 b1 g
% g2 t' ]4 o z9 F* l7 o
" c e* }6 i }( y- S! E; n4 V |