Inconsistency in AIS filters leads to events without tracks
- Release:
- Tags: API, Map, Marine Manager, Open Issue, Vessel Viewer
We have noted some inconsistencies that may occur between vessel track data and other associated information in our platform, whereby events and vessel detections show but tracks are missing or vice versa.
Automatic identification system (AIS) data inherently contains a degree of “noise.” To ensure the highest possible accuracy and utility of this information, our data pipeline has advanced filtering mechanisms.
While these filters are crucial for refining the data, certain conditions can, at times, lead to specific display anomalies like the examples below:
- Events like loitering or port visits may appear without a corresponding vessel track (example).

- Sentinel-1 detections matched with AIS, yet lack an associated vessel track.
- In the below example, the vessel Golden Grains has a matched Sentinel-1 detection but it doesn’t have a track for this time range because the matched track segment is currently filtered out due to data “noise.”

Update: September 26, 2025
- We’ve deployed an initial fix to resolve inconsistencies you may have seen in the track history on our APIs and map. To ensure track history is accurate, we’ve adjusted its update schedule: we will reimport all track data for the current year every month to ensure it’s comprehensive.
- As a reminder: this doesn’t impact the 72-to-96-hours delay in our daily data processing. The update has been on the historical data.
We are aware of these intermittent issues and our team is working to enhance our data processing capabilities to mitigate their occurrence.
If you see any of these issues and require further clarification, please contact our support team at [email protected].