昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
- ?9 \. K8 u4 O6 e& t
' J+ {5 v- L& A- d事件整整影响了27 分钟 o: h5 B2 L. c- }# @
# d/ [; q4 q! [2 _5 `9 P( Y8 |
这种全球性的502 应该不是ddos 引起的
0 {! O' k" C `. o: [) c9 O) a& \. E8 M3 @+ x: R2 \
后来看cloudflare 的email,应该是内部程序的问题5 {; c1 M: h- \
! T$ a, h4 M. V+ ~% A, Q5 QDear Cloudflare Customer, , Y( f9 r. q0 T Z
4 |3 B$ b- j8 ?9 T, HToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
. ?# d% ~/ _2 @2 j; X; u- b6 e0 M, q6 r! s4 I5 C7 [
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. 4 Y! T2 M+ Z8 R/ y9 m
; a4 D6 X5 z9 c5 w3 YWe’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.
1 X3 e. p4 P7 f' p/ h/ E2 R! Q! ?( {, N
~The Cloudflare Team - F& a* G' }3 e: T
" u3 m! N0 D8 A( x
$ g" W; h% a2 N- j
|