[ad_1]
We’re actively counting on Cloudflare caching for our web site pages to load sooner. Now we have a mechanism for caching person information based mostly on person identifiers which forestall Cloudflare to serve one person information to a different.
For some motive (we’re exploring), the Settings on Cloudflare cache guidelines have modified and all of our web site requests began to get the identical and just one person portfolio web page.
Once more, that was solely read-only to the portfolio, no person had the power to do any edit actions as a result of they’d no permission to take action.
Proper after the incident was reported, we did put our web site in upkeep mode, purged and disable all of the Cloudflare caches. All person portfolio information is protected and we’re going to give you the motion gadgets for stopping this type of incident sooner or later.
[ad_2]