Details of the Cloudflare outage on July 2, 2019

(blog.cloudflare.com)

698 points jgrahamc | 2 comments | 12 Jul 19 15:46 UTC | HN request time: 0.401s | source

Show context

kevinherron ◴[12 Jul 19 19:28 UTC] No.20423632[source]▶

>>20421538 (OP) #

Sometimes I wish Cloudflare failed more often so I could read more of these postmortems...

replies(2): >>20423799 #>>20424214 #

1. bostik ◴[12 Jul 19 20:30 UTC] No.20424214[source]▶

>>20423632 #

Please no.

The last time they had a global problem, everyone scrambled for more than a week. (Cloudbleed)

This 30-minute global outage was pretty nasty, but not anywhere near as awful. Timing helped, as nothing truly critical was affected. (There are some extremely high-volume sporting events which, if affected even just for few minutes, can have a direct impact on the bottom line.)

I do not wish to see more of these. Cloudbleed gave me two weeks of headache and an indigestion problem. This one did basically nothing. If there is a happy middle ground between the two, I am not exactly thrilled at finding out what it is.

replies(1): >>20425102 #

2. eastdakota ◴[12 Jul 19 22:29 UTC] No.20425102[source]▶

>>20424214 (TP) #

Agree. Cloudbleed was really, really awful. We should write up all the things we learned from that and all the changes we've made since. Just looking at the number of engineers who are Rust experts since then, for instance.

↑