昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
, s/ R3 ]3 `0 J% y0 h
1 W+ a: }$ B5 E& ]事件整整影响了27 分钟. S \1 J c- }7 n4 \
8 K( R; \! B8 k' P, N, x1 s, r这种全球性的502 应该不是ddos 引起的
& g) J, n, o! E: M
# v5 a& ^6 ?( V4 F1 I后来看cloudflare 的email,应该是内部程序的问题
! I' g: ^: W2 O8 c J; N! h$ N L4 ^( A* v7 U* ^- x
Dear Cloudflare Customer,
. ]0 m& m& y3 j/ w, F! [9 j" a! J6 i2 h9 o6 P( [# x. E
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
* _1 a2 W R3 P, ?7 c" l0 e/ n0 P/ J+ f7 e+ \7 {8 D! h
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.
, n5 K& M% j: ~ \% E+ F7 i
# j- X: p4 [+ l5 x- x/ b2 e0 C$ 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.
5 e9 p8 U* B# Q8 Y+ p/ z, v% e$ | W6 ~) M* [
~The Cloudflare Team - R2 d6 P+ D$ l% ]8 R8 R# e7 c
$ U0 y3 D& w( q
" U) P6 u0 u- ~! r0 N& ^" b |