Data and feeds

Every machine-readable output the site publishes, gathered in one place. All of it is generated at build time from the same records the pages read; nothing here is a separate database. Data through 2026-11-08 (8 November 2026). Licence: CC BY 4.0 for World Freight Monitor's own records; upstream sources keep their own terms, listed on Sources and terms.

Events and effects

/data/revisions/How many already-published PortWatch values were rewritten in each of our weekly pulls
status.jsonWhat this build contains: data date, newest news day, event and edition counts, build time
events.jsonEvery published event, with its full measured effect history
events.csvThe same events as one flat table: type, dates, severity, places, lead measured effect and recovery time
events.rssOne item per published event
editions.rssOne item per approved weekly edition

Ongoing disruptions

situations.rssOne item per event currently marked ongoing
/situations/The page itself, day counters and latest levels against the pre-event baseline

Series and comparisons

compare.jsonLast 120 days of daily transits or port calls, one array per chokepoint and top-100 port, feeding the compare tool
watch.jsonA descriptive summary (last 28 vs prior 28 days) and recent events for every port, chokepoint and lane, feeding the browser-only watchlist
map-chokepoints.json / map-lanes.jsonGeoJSON for the interactive map
/exposure/Oil and LNG carried through each chokepoint, from one public EIA table
compare-events.jsonEvery event's lead measured effect and recovery time, feeding the event comparison tool

Full-history daily series (beyond the 120 days above) are not offered as a bulk download. IMF PortWatch's terms allow publication with attribution but ask for permission for commercial reuse and automated bulk download, and the IMF has not yet answered; see Sources and terms. A single event's own window and baseline are in that event's row in events.json.

Facts and context

facts.jsonEvery sourced fact computed from the data and the archive, the same pool the daily fact draws from
/recovery/Recovery time for every ended event with a measured fall, as a table
/measures/Sanctions, customs and capacity-withdrawal events, in force or ended
/events/compare/Compare any two events' severity, measured effect and recovery time
/confidence/Every record's stated confidence level

Feeds for one place

Every port, chokepoint, lane and country with at least one published event has its own RSS feed of those events, newest first, at most 50 items. The address is the entity's page address plus events.rss:

/ports/<slug>/events.rssExample: Los Angeles and Long Beach
/chokepoints/<slug>/events.rssExample: Suez Canal
/lanes/<slug>/events.rssExample: Asia to North Europe
/countries/<slug>/events.rssEach place's page links to its own feed ("Follow this place")

Embeds

Embed the ongoing disruptions status board on your site

Copy the code below. It updates when this site does, and carries its own source line and a link back. Preview the embed.

<iframe src="https://worldfreightmonitor.com/embed/status/" title="Ongoing disruptions on World Freight Monitor" width="100%" height="480" style="border:0" loading="lazy"></iframe>

Text for language models

llms.txtA short, linked index of the site
llms-full.txtThe full text of every page, concatenated

Sitemaps

sitemap-index.xmlEvery page, sectioned by type

Embeddable charts for a single chokepoint, port, ongoing disruption or recovered event are on each entity's own page, not listed here individually.