昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情8 m% U* d9 b/ n1 M6 x6 T0 x- k
5 d6 h! ]' E' w/ y) f. u
事件整整影响了27 分钟( U, g8 C8 h8 O* r7 J: |) b8 h
# |5 N8 v. F; Q# V0 H这种全球性的502 应该不是ddos 引起的
/ O. Y, b! m9 d M5 e1 a4 \3 t3 _+ F5 W, R9 C, {3 {; g
后来看cloudflare 的email,应该是内部程序的问题
& d. X* j, W: J7 n( v+ q8 s3 E+ E7 F6 ?/ W }( T' I, X, W
Dear Cloudflare Customer,
6 y2 ^. R7 h( [1 [, \7 f% g' p# o3 b# P
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
. _ r! t- w5 i* c* e5 m' c
~* K7 ?' H" [8 p1 M1 P; ZThe 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.
; e! A* o/ E9 d* f! G# F4 q4 @; z6 n4 h6 n7 D% O" f% {
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.
- y3 S) ?9 `8 U, L( Y- A0 C( m" L' J. F
~The Cloudflare Team
7 N, P8 K) X. i8 u T2 E
0 v/ u8 {! L5 \% c' N# y+ R) R3 x3 x! e# n1 d8 z
|