Normal operations restored.

A fix has been implemented that we believe should resolve the incident; data volumes are rapidly returning to normal.

Processing is resuming - we are starting to see data returned to the Visualizer and API. We expect to restore normal operations soon, and will then concentrate on backfilling any missing JA3 signatures.

We are continuing to work on a fix for this issue.

Data processing is working but is taking multiple hours, resulting in no data in the Visualizer and API for queries of "last_seen:1d" (data is shown for "last_seen:2d". We're updating our platform to improve data processing.

We continue to troubleshoot with our vendor and are working to restore most data to our API and Visualizer tonight. Certain fields (like JA3) may not be populated until after a full recovery.

Our database vendor has their engineering team collecting information for additional troubleshooting while we make changes to our platform to attempt to restart data processing. We'll continue to provide updates at least every few hours as we work.

Data is processing but still has at least a few hours to catch up. We'll provide updates every few hours.

We are seeing improved health of the data subsystem but still have a substantial backlog of data to process.

Data processing is still stalled, resulting in no results for a GQNL query of "last_seen:1d". We continue to work with our data vendor to identify the root cause.

Data processing is substantially delayed, resulting in reduced data available in the Visualizer and via the API.