Well, handmade developers, it's been an interesting day so far. Cloudflare issued a warning that due to a memory leak in one of their html parsers, information could end up being leaked in the responses to completely unrelated requests.
TL;DR: Cloudflare screwed up, Google noticed and told them, Cloudflare fixed it, people will be resetting passwords everywhere for days to come.
Long story short: If your site was behind Cloudflare, they may have leaked potentially sensitive information; that information may have ended up in Google's and other caches. This was regardless of whether or not your site used the vulnerable features that caused it to leak, because your traffic might have previously transited through the node in question, with some of your pages remaining in memory.
So while it looks like we weren't part of the subset of sites that triggered a leak, our traffic may


Fig. 1 - Current Kennedy HQ