Incidents | Sift Incidents reported on status page for Sift https://status.sift.li/ https://d1lppblt9t2x15.cloudfront.net/logos/8ec4b390e35ba6ba2c18742aee5af142.png Incidents | Sift https://status.sift.li/ en Recovering from a resource exhaustion attack https://status.sift.li/incident/915027 Fri, 05 Jun 2026 22:31:00 -0000 https://status.sift.li/incident/915027#7a8775ac55ba0e1d5ea67a09963dc0be56dd9876b6332aaae482e842519e4635 Earlier today, Sift experienced a database storage incident caused by a deliberately abusive user behaviour. We identified and suspended the abusive account, stopped the runaway import impact, and began removing the incident-related data. The system is now recovering while we implement hardening. Degraded queue performance https://status.sift.li/incident/898886 Mon, 18 May 2026 17:01:00 -0000 https://status.sift.li/incident/898886#c9e8e7b333b705ead4024d2e14259d7cdc451d6d77d439623cc17b4f8500d8da We identified overlapping feed refresh workers as the cause of the backlog and have deployed safeguards to clear the queue and reprocess feeds gradually while protecting database capacity. This should be resolved by 20:00 BST.