This map shows live cargo-and-tanker traffic against 96 whale shark hotspots: the 74 IUCN-recognised Important Shark and Ray Areas (ISRAs) where whale sharks (Rhincodon typus) aggregate, feed, give birth, or transit, plus 22 additional Womersley aggregation sites that fall outside the ISRA network (the ISRA programme has not yet workshopped the North American Atlantic, African Atlantic, or North American Pacific regions). Sharks and ships sharing the same patch of ocean is the dominant unrecognised driver of whale shark mortality worldwide; this map exists to make that overlap visible in real time.
Polygons are sourced from the IUCN Shark Specialist Group's Important Shark and Ray Areas portal. Coverage spans nine published regions (Western Indian Ocean, Asia, Central & South American Pacific, Australia/Oceania, European Atlantic, South American Atlantic, plus zero-whale-shark regions for completeness). The North American Atlantic, African Atlantic, and North American Pacific regions are not yet workshopped by the ISRA programme. Each polygon's popup links to its full IUCN factsheet — click any hotspot to see it.
Live AIS positions arrive from aisstream.io via a same-origin Cloudflare proxy. Only AIS Class A vessels are shown — that's cargo, tankers, passenger ferries, fishing vessels above ~300 GT, towing, HSC, and large pleasure craft. Smaller Class B traffic (recreational, small fishing) is not transmitted with enough fidelity to be useful. Vessels at port or anchor (speed below 1 knot) are filtered out. Coverage is global. Vessel-day accumulation (the 30 d / 365 d counts in each hotspot card) is narrowed to the ISRA buffer bboxes server-side to stay within the Durable Object request budget; the live map shows every vessel aisstream reports anywhere on Earth.
Each hotspot is rendered with a 10 km dashed buffer ring. A vessel inside the polygon is an immediate strike risk; a vessel inside the buffer ring is a near-zone risk. The 10 km value is MMF's working choice and is more conservative than Womersley et al. (2022)'s 100 km radius used in the original collision-risk modelling.
The 30 d and 365 d counts in each hotspot card are unique vessel-days — one row per ship per UTC day per hotspot. A ship sitting inside a polygon for 8 hours counts as one vessel-day; a ship visiting the same hotspot on two consecutive days counts as two. Accumulated server-side by a Cloudflare Durable Object holding a persistent connection to aisstream. The sidebar list re-ranks by 30-day vessel-day pressure once data is available, falling back to the live snapshot in the meantime.
Bootstrap period: the 30 d window fills in over the first 30 days from launch; the 365 d window over the first year. Hotspot cards show "X days of data so far" until the windows are complete.