|
|
昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
& p0 o4 ?) M9 s0 P2 l5 K
* D5 o! X0 f: }# k1 ?/ @, O事件整整影响了27 分钟
% q6 {7 ]! \! O7 I6 |* {; g! a/ g9 P% X' Z, m' n
这种全球性的502 应该不是ddos 引起的
2 X6 L" Z0 H/ l3 m: {! W' X$ J) D3 h
7 h i9 ]. C8 k% A" z" _. y3 g后来看cloudflare 的email,应该是内部程序的问题# v( z, f5 h' }8 B7 w3 m3 b
" Y' r" W4 j% x, r+ t; i \Dear Cloudflare Customer,
" Q1 p% j/ p9 f$ l! [# D, Q1 }( B4 N: e4 P k @ s/ ^& r3 x: v
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. ( x+ t/ v3 }! h3 \: _4 S
( D: j! D( J9 |6 Y! p% y
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. & q y3 u( ]. P
5 F) o' o- [. N2 x( h } w
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.
# F ~# q& Y4 N4 m- H( |; M" e4 s0 [: e& v4 O: Y
~The Cloudflare Team
& B) ?) v4 l2 h y& y% i$ D x
2 \! G+ B! i: o. T1 e
6 ^, b, L" N4 V, _ }& S |
|