昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情
& ?, h) Y1 g: U( A6 a; Q% @( E
H" k {5 m% j2 J: L2 C, n1 p事件整整影响了27 分钟8 q- H9 P9 u% ]& f9 h5 H
9 E' }# \$ T- A6 u+ k这种全球性的502 应该不是ddos 引起的0 y, h9 U! Q' y1 f1 {: G. `
7 p/ o, @* n8 R+ j- z
后来看cloudflare 的email,应该是内部程序的问题' H' G! Y5 J; M! Z& T, ^# r* U5 H
/ }3 h v: o, i0 m
Dear Cloudflare Customer,
$ ?4 B8 @$ n* d2 F
9 z# y( b r( N0 t, r" J+ GToday at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes.
e! ?0 e7 k: z
' a8 q* K6 r+ G; X! {% GThe 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.
2 D& y+ B4 A5 {1 I5 e
* l. N/ D- T, N# I- R* ]# QWe’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.
& ~$ G5 m6 _: C) a5 f
' J8 r9 G7 q: c U/ W~The Cloudflare Team ; a; S7 [2 A- P% s9 N% R Q
. Y% W' k' }& P" D2 u% D' `
; W% ~) f, r* N |