昨晚 cloudflare 发生了全球502, 也就是说只要是使用了cloudflare 的站点全部502,是全球范围内的事情6 {% h ]$ M, p- n3 G L( g# K
5 I# }1 o& v4 C; g5 y
事件整整影响了27 分钟
! \: c8 F) J/ u: X. z! v- e$ Y
这种全球性的502 应该不是ddos 引起的9 Z# J! e- f/ `( J+ i+ x& W7 w2 L. C
& H, B* t5 Y3 }
后来看cloudflare 的email,应该是内部程序的问题
$ S8 T" m# k+ `4 n
6 g( Q- \* a2 \" e/ bDear Cloudflare Customer, 7 E# x O: R. A4 Q
/ r1 g6 k* c0 X# l R
Today at approximately 13:42 UTC we experienced a global service disruption that affected most Cloudflare traffic for 27 minutes. 8 I* m) G# {: R" y# Q4 q" J- U
4 V* e* D2 D- D
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. " d/ }2 K3 o7 P6 [
2 o( g9 R, f3 \1 {) e
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. 3 _1 [- r5 [" c( a @& @+ b4 k
2 a* p& z9 v0 i1 n
~The Cloudflare Team
2 i2 A( w% ?! Y: {! x
5 u) O( G8 s3 c. j# ?% Y, {
; d" X# v7 u9 U H; y! V |