News for hackers. Stuff that matters.

A comment on Details of the Cloudflare outage on July 2, 2019.

Re:Details of the Cloudflare outage on July 2, 2019 by woliveirajr on Friday July 12, 2019 @11:50AM (#20421577)
> Unfortunately, last Tuesday’s update contained a regular expression that backtracked enormously and exhausted CPU used for HTTP/HTTPS serving.

One of those cases where they had 1 problem, used regular expression and ended up with 2 problems ?

Edit: I really like how much information is given by CloudFlare. 11 points in the "what went wrong analysis" is how every root-cause analysis should be done.

[ Parent | on HN ]
Re:Details of the Cloudflare outage on July 2, 2019 by toomuchtodo on Friday July 12, 2019 @01:05PM (#20422273)
Somewhat humorous, as someone [1] (congrats /u/fossuser!) mentioned this failure scenario in the thread about Twitter being down yesterday.

"Pushing bad regex to production, chaos monkey code causing cascading network failure, etc.", in response to a comment from someone who previously worked at Cloudflare.

[1] https://news.ycombinator.com/item?id=20415608

[ Parent | on HN ]
Re:Details of the Cloudflare outage on July 2, 2019 by citruspi on Friday July 12, 2019 @01:55PM (#20422798)
They mentioned it was a regular expression in the original post[0] on the day of the incident, that part isn't news (discussion here[1]).

[0]: https://blog.cloudflare.com/cloudflare-outage/

[1]: https://news.ycombinator.com/item?id=20336332

[ Parent | on HN ]
Re:Details of the Cloudflare outage on July 2, 2019 by anoviceuser on Saturday July 13, 2019 @03:17AM (#20426938)
I agree this is an awesome post and a really great example of how every Root Cause Analysis needs to be done. I am also impressed by their incident response.
[ Parent | on HN ]