Live tracking · 320 vessels · 277 ports Data refreshed 60d ago

Contact

Get in touch.

PortWatch is maintained by a small team of maritime data enthusiasts. We welcome corrections, partnership enquiries, and feedback from researchers and journalists.

Corrections and data quality

If you have spotted incorrect port metadata (wrong country, wrong UN/LOCODE, wrong coordinates), incorrect vessel particulars, or a vessel-to-port association that you can demonstrate is wrong, please get in touch with a citation to an upstream source. The fastest fixes come with a Wikidata QID, an Equasis URL, an IMO entry, or a UNECE UN/LOCODE row reference. Corrections submitted without a verifiable citation are still welcome but take longer to process.

Press and research enquiries

Journalists working on stories that use PortWatch as a source — whether for context, statistics, or a screenshot — are invited to contact us in advance so we can flag any data caveats relevant to your specific question. We do not require advance permission to quote the directory or screenshot it under fair-use conventions; reaching out is courtesy, not prerequisite.

Partnership and data licensing

If you are interested in a bulk export of the directory, an API integration, an embedded widget for your own site, or a custom data partnership, contact us with a description of your use case. Bulk exports are not available under the standard public terms of service (see terms) but can be agreed for non-commercial research and educational use.

Reporting abuse

If you believe a deployment of PortWatch is being misused — for example as part of a phishing scheme, sanctions evasion exercise, or platform abuse complaint — contact us with a description of the abuse and any supporting URLs or screenshots. We take abuse reports seriously and respond to credible reports within a few working days.

How to reach us

The maintainers can be reached via the email address published in the site footer of any commercially operated deployment of PortWatch. For deployments running on community infrastructure, please open a discussion on the public source repository linked from the about page.