This page explains how FleetLeaks builds and updates vessel records from official sanctions designations. The system is designed for traceability and repeatable updates.
Update schedule target: 00:00 UTC daily.
June 12, 2026, 12:00 AMSources
FleetLeaks ingests official lists from multiple jurisdictions. Names, formats, and identifiers vary across sources. The pipeline standardizes these into a single schema.
Russia-related designated vessels
Counts are compiled from official public designations (US, UK, EU, CA, AU, NZ). Updated daily.Pipeline
1) Fetch
We pull the latest official source data via automated jobs and keep raw snapshots for traceability.
2) Normalize
We standardize fields into a consistent schema: identifiers, names and aliases, flags when present, program/list tags, dates, and remarks.
3) Validate identifiers
When an IMO is present, it becomes the primary key for merging. The pipeline validates basic structure and removes obvious formatting errors.
4) Deduplicate and merge
Entries are merged primarily by IMO number. When multiple sources refer to the same IMO, FleetLeaks unions sources onto a single vessel record and preserves aliases and notes.
5) Publish and log changes
After processing, vessel pages update and the changelog highlights additions, removals, and edits.
Data quality
- Some entries omit IMO numbers.
- Transliteration and alias variation is common.
- Flags and ownership can change faster than lists update.
- Some lists focus on entities rather than vessels.
Corrections
If you spot an issue, include the vessel URL plus IMO and the specific claim to review. Add a source when available.
FleetLeaks updates records when evidence supports the change. Corrections are part of the workflow, not an exception.