昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
& O% Q, e% r9 K; z$ }" O1 f7 M) ? R ]
事件整整影响了27 分钟
# Z0 G: C$ O& c: A' M9 k- _& K
) e- |3 G- W" {% o这种全球性的502 应该不是ddos 引起的
8 a( t$ q9 X! T) V- o
! N5 R: z& N6 c5 G1 b7 f后来看cloudflare 的email,应该是内部程序的问题
# Y6 ~. Q- c' t5 s; S+ v+ L- I0 ?& _6 P& f
Dear Cloudflare Customer,
- O1 R! q, W! F% q" m( J4 i
& t5 ?! u: f* D& c5 z' q7 J/ W2 Z7 LToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. " |) b" S$ h+ B& ~ T
0 _, s4 M1 j- v1 ]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. 3 r& t4 M- j: j. l
& B' Z9 s0 X" |* i, K, iWe’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 p J y3 w3 N, L: |
7 }4 v* R3 t+ j* C7 v0 ^' J1 ^
~The Cloudflare Team 4 A3 B8 \' u4 W A9 z
: \' V9 \, @( S: t2 v
5 k! N+ J; I8 U; Q2 \9 _
|