Overwatch now applies a three-tier downsampling strategy to AIS position data so you get the right resolution at every time horizon. Data from the last 7 days is stored at full resolution, positions between 7 and 30 days old are thinned to one ping per vessel per minute, and data between 30 and 90 days is reduced to 5-minute intervals. Full-resolution archives are preserved separately for rehydration on demand. This keeps queries fast on recent data while retaining deep history for investigations and trend analysis.
The in-app support chat now verifies your identity when you’re signed in, so support conversations are automatically linked to your account. This means faster resolution — the support team sees your workspace and plan context without asking you to identify yourself. Unauthenticated visitors on the marketing site still have access to anonymous chat.
A comprehensive security audit resulted in tighter access controls across the platform. Key improvements include enforced tier-based access checks on data export and event endpoints, so free-tier API keys can no longer access paid datasets. Audit log CSV exports are now sanitized against formula injection. Row-level security policies have been extended to additional tables that were previously unprotected. No action is required on your part — these changes apply automatically.
Fixed an issue where concurrent AIS events could create duplicate open vessel visits at the same port, leading to phantom “in port” records that departure events couldn’t close. A uniqueness constraint now prevents duplicate visits at the database level, and departures correctly close all matching records. If you noticed vessels stuck in an “in port” state, this should resolve it.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
