Cloudflare data still in Bing caches
From the parent thread:<p><pre><code>  The caches other than Google were quick to clear and we&#x27;ve not been able to find active data on them any longer.
  ...
  I agree it&#x27;s troubling that Google is taking so long.
</code></pre>
That&#x27;s really the core issue here - the Cloudflare CEO singled out Google as almost being complicit in making their problem worse whilst that exact issue is prevalent amongst other indexes too.<p>The leaked information is hard to pinpoint in general, let alone amongst indexes containing billions of pages.<p>I can understand the frustration - this is a major issue for Cloudflare and it&#x27;s in everyone&#x27;s best interests for the cached data to disappear - but it&#x27;s not easy, and they shouldn&#x27;t say as such (or incorrectly claim that &quot;The leaked memory has been purged with the help of the search engines&quot; on their blog post).<p>This is a burden that Cloudflare has placed on the internet community.
Each of those indexes - Google, Microsoft Bing, Yahoo, DDG, Baidu, Yandex, ... - have to fix a complicated problem not of their creation.
They don&#x27;t really have a choice either given that the leak contains personally identifiable information - it really is a special sort of hell they&#x27;ve unleashed.<p>Having previously been part of Common Crawl and knowing many people at Internet Archive, I&#x27;m personally slighted. I&#x27;m sure it&#x27;s hellish for the commercial indexes above to properly handle this let alone for non-profits with limited resources.<p>Flushing everything from a domain isn&#x27;t a solution - that&#x27;d mean <i>deleting history</i>. For Common Crawl or Internet Archive, that&#x27;s directly against their fundamental purpose.