history.rss
Dropzone AI Status - Incident History
Some investigations delayed on subset of environments
Date: Jun 23, 15:38 PDT
Status: Resolved
The fix has been rolled out to all environments, delayed alerts are being processed, and all systems are now operating normally.
Date: Jun 23, 14:55 PDT
Status: Identified
Dropzone has identified a drop in alert processing across 5% of customer environments. For those affected, alerts which were ingested during daily system updates were stuck in a pending state and were not investigated. A fix is in progress, and will automatically start those delayed investigations.
Drop in alert ingestion
Date: Mar 28, 10:45 PDT
Status: Resolved
This issue has been resolved, all delayed alerts have been backfilled and new alerts are being received and processed.
Date: Mar 28, 10:32 PDT
Status: Update
We have identified the cause of the alert ingestion delay and a fix is rolling out to all environments. No data loss is expected, and delayed alerts are being processed now.
Date: Mar 28, 09:34 PDT
Status: Update
We have identified the cause of the alert ingestion delay and a fix is rolling out to all environments. No data loss is expected, and delayed alerts are being processed now.
Date: Mar 28, 09:05 PDT
Status: Investigating
Dropzone has identified a drop in alert ingestion across multiple customer environments. A fix is in progress.
LiteLLM supply chain attack
Date: Mar 24, 14:23 PDT
Status: Resolved
On March 24, 2026, a malicious version of the open-source LiteLLM package (litellm versions 1.82.7 / 1.82.8) was publicly reported. Dropzone AI immediately investigated potential impact across our environments.
We can confirm that Dropzone AI was not affected. The vulnerable package was not present in our systems, and no indicators of compromise, unauthorized access, or data exposure were identified.
As a precaution, we performed additional validation across our infrastructure and initiated credential rotation for sensitive systems. There is no impact to customer data or services, and no action is required.
We will continue monitoring for any related developments.
Date: Mar 24, 09:12 PDT
Status: Investigating
Dropzone is aware of a supply chain attack in recent versions of the python LiteLLM package. Dropzone does incorporate LiteLLM as part of its toolset.
Our initial investigation shows that we have exclusively been on non-vulnerable versions of this package. We will continue to monitor the situation and take any actions necessary to maintain system security and protect the data of our customers.
We anticipate final analysis by end of day and will update this incident accordingly.
Dropzone UI impaired
Date: Jan 30, 15:20 PST
Status: Resolved
This incident has been resolved.
Date: Jan 30, 15:20 PST
Status: Update
Today's push was slated to include in-product support. Due to an edge condition, the integration with the support sidebar caused the UI to fail to load for some customers.
We have reverted the new functionality and will deploy it after more robust testing. UI downtime was between 10 and 45 minutes for those customers affected. Throughout the UI downtime, all other services, notably including investigations, were functioning normally.
Date: Jan 30, 14:54 PST
Status: Investigating
Dropzone environments which have been upgraded today may fail to load the user interface, and you may receive a 500 error.
We are investigating currently and expect remediation within 30 minutes. Investigations are being ingested and processed, and API access is unaffected.