昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情: R7 ]4 J+ b4 K
8 S6 Q0 O2 x0 e4 U% |: T+ \0 z事件整整影响了27 分钟 & m$ B4 v& U2 E! ~0 }5 E* F Z( Z# x5 k6 v" w+ H
这种全球性的502 应该不是ddos 引起的 . f7 I( o& u7 o! h# ?6 V/ i5 o, F& z3 O$ q
后来看cloudflare 的email,应该是内部程序的问题 2 S: ?- P! c$ C! C) h8 S& q5 G* P) J/ q
Dear Cloudflare Customer, * r; S' b# I. [' g; Q) s! V
7 {- g# p3 F, \" v; j8 rToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. ! r9 ~$ H2 t: J1 X
6 D7 E2 I% c" i1 O# l# X
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. 7 x0 G2 m' K. _& N; `
" Y5 I+ U: `2 n$ {& AWe’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. 2 V5 \8 f% t8 h6 u3 o3 W: Y/ g4 b / d, v! G( ^0 A$ ^6 p4 N~The Cloudflare Team 3 m. }" t: n/ M/ H# B% a& ~ 9 \4 n; \! x8 |5 {1 L Y. U8 C& r k, J) S# ]" f3 U/ s