- We fixed multiple UI alignment issues, including overflowing dates in the Takedown and other tabs, text squishing in date fields when resizing windows, and incorrect font usage in the ‘Exact match search’ label. Additionally, zooming the screen no longer causes the customer’s logo to disappear.
- We fixed several filtering issues on the Takedowns tab of the Client Panel, including adding the ability to reset filters, correctly displaying ‘3rd Party Unresponsive’ takedowns when using the ‘Ongoing’ filter, and clarifying filter options related to process phases.
Additionally, we resolved an issue with the custom date range not applying correctly; filters now update accurately and reflect properly in the date picker text.
- We fixed an issue causing takedowns detected over 30 days ago to incorrectly display an “Ongoing” status. Users can now accurately filter these cases with two new status options: “Unresponsive” (equivalent to status #7, 3rd_party_unresponsive) and “Pending” (equivalent to status #1, pending), both clearly marked in orange.
- We fixed an issue where the Custom Date Range filter on the Client Panel wasn’t updating correctly. Users can now successfully select custom date ranges, and the displayed data accurately reflects the chosen timeframe.
- We fixed the inconsistent time lapse calculations on the main dashboard and disrupted attacks page. Now, the displayed time lapse correctly aligns with the threat confirmation timestamp. This resolves misleading scenarios such as threats resurfacing after extended periods (e.g., previously showing “Detection Time 364 days ago,” now accurately displayed as “Last Update 2 days ago”).
