←back to thread

Details of the Cloudflare outage on July 2, 2019

(blog.cloudflare.com)
698 points jgrahamc | 3 comments | 12 Jul 19 15:46 UTC | HN request time: 0.514s | source
Show context
woliveirajr ◴[12 Jul 19 15:50 UTC] No.20421577[source]▶
> 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.

replies(2): >>20422273 #>>20426938 #
1. toomuchtodo ◴[12 Jul 19 17:05 UTC] No.20422273[source]▶
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

replies(2): >>20422798 #>>20425008 #
2. citruspi ◴[12 Jul 19 17:55 UTC] No.20422798[source]▶
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

3. ◴[12 Jul 19 22:15 UTC] No.20425008[source]▶