At its narrowest point — the Phillips Channel, south of Singapore — the Malacca Strait is 1.5 nautical miles wide. About 94,000 vessels transit it every year. That's roughly 260 vessels a day, single-file through a passage that's narrower than some rivers.
Right now, our chokepoint monitor shows the Malacca Strait at disruption 50. That's higher than the Strait of Hormuz (30), Bab el-Mandeb (30), and the Bosphorus (30). Of the chokepoints ArcNautical monitors in real time, Malacca is the most stressed.
A Jakarta-to-Tokyo voyage (IDJKT → JPTYO) currently scores risk 35 in our system. That's moderate. But a Jakarta-to-San Diego run (IDJKT → USSDO) scores 43 — tipping toward elevated. The difference is distance and exposure time. This post is about what drives those numbers through one of the world's most congested waterways.
What disruption 50 actually means
ArcNautical's chokepoint disruption score is a composite of several real-time signals specific to the strait: active navigational warnings in the area, piracy and armed robbery incidents within 80nm, AIS anomalies (signal gaps, potential jamming), weather conditions, and conflict events near the coastal states.
Here's how the Malacca Strait compares to the other chokepoints we monitor right now:
| Chokepoint | Disruption | Status | Primary drivers |
|---|---|---|---|
| Malacca Strait | 50 | DISRUPTED | Piracy incidents, congestion, NAVWARNs |
| Strait of Hormuz | 30 | ELEVATED | Geopolitical tension, sanctions proximity |
| Bab el-Mandeb | 30 | ELEVATED | JWC listed area, conflict events |
| Bosphorus | 30 | ELEVATED | Traffic congestion, weather delays |
| Suez Canal | 20 | MODERATE | Operational, routine traffic |
Hormuz gets the headlines. Bab el-Mandeb gets the war risk premiums. But right now, by the numbers, Malacca is where the most signals are firing simultaneously.
The geography problem
Most chokepoints are chokepoints because of geopolitics. Hormuz is tense because of Iran. Bab el-Mandeb because of Yemen. Malacca is different. It's a chokepoint because of geometry.
The numbers
The strait runs about 550 nautical miles from its northwest entrance (between Sumatra and the Malay Peninsula) to the Singapore Strait at the southeast end. Width varies from 200nm down to 1.5nm. Depth at the southern end drops to 25 meters in places — too shallow for fully laden ULCCs.
Traffic separation is mandatory. Vessels over 300 gross tonnage must report to STRAITREP (the strait reporting system run by the three coastal states: Indonesia, Malaysia, Singapore). At peak hours, the separation scheme handles vessels in both directions through a channel that, at its tightest, barely fits two Suezmax tankers abreast.
What transits here
About 25-28% of global seaborne trade passes through Malacca. That includes roughly a third of the world's LNG shipments, a quarter of all crude oil trade, and most of the container traffic between East Asia and Europe or the Middle East. China, Japan, and South Korea depend on it for energy imports. Southeast Asian economies depend on it for exports.
When we score a route like Jakarta to Tokyo, the Malacca transit is the dominant risk segment — not because of war, but because of the concentration of vessels, the narrow channel, and the persistent low-level piracy threat in the adjacent waters.
Piracy in the strait: not Somali-style, but persistent
Malacca Strait piracy doesn't look like Gulf of Aden piracy. There are no motherships, no ransom negotiations, no armed militia boarding from skiffs at 20 knots. What happens in and around Malacca is mostly petty theft and armed robbery at anchor — gangs boarding vessels at night in anchorages, stealing cash, electronics, ship stores. Sometimes engine spares. Occasionally crew valuables.
ReCAAP (the Regional Cooperation Agreement on Combating Piracy and Armed Robbery against Ships in Asia) tracks these incidents in detail. The numbers are consistent: the Malacca and Singapore Straits region accounts for a significant share of all incidents reported in Asian waters. Most are CAT 3 or CAT 4 (the lower severity categories), but they don't stop.
A P&I club pricing hull cover for a vessel regularly transiting Malacca isn't worried about a total loss from piracy — that risk is vanishingly small here. They're worried about the cumulative cost of petty theft incidents (each one generating a claim), the risk of crew injury during a boarding, and the operational delays when a vessel has to cooperate with investigations by three different coastal state authorities. It's a frequency problem, not a severity problem. The scoring reflects that.
Two voyages through the strait, two different scores
Our ticker currently shows two routes that transit Malacca:
Jakarta to Tokyo. Jakarta to San Diego. Both exit through the Malacca Strait. Both hit the same chokepoint disruption. But they score differently because the routes diverge after Singapore.
The Tokyo run heads northeast through the South China Sea, past the Spratly Islands (contested waters, occasional NAVWARN clusters, but no JWC listing), up past Taiwan, and into Japanese waters. Total distance is roughly 3,300nm. The Malacca transit is the high-risk segment; the rest is relatively benign.
The San Diego run is longer — about 9,800nm. After exiting Malacca, it crosses the South China Sea, enters the Pacific, and runs a long exposed ocean crossing. More distance means more weather exposure, more fuel uncertainty, and a wider ETA distribution from the Monte Carlo simulation. The 8-point difference between 35 and 43 is mostly weather and distance, not threat.
The alternative: Lombok and Makassar
When Malacca disruption is high enough, some operators reroute. The alternative is the Lombok Strait (between Bali and Lombok) into the Makassar Strait (between Borneo and Sulawesi), then north to the Pacific. It adds roughly 1,000–1,500nm depending on origin and destination.
| Factor | Via Malacca | Via Lombok/Makassar |
|---|---|---|
| Distance (Jakarta → Tokyo) | ~3,300 nm | ~4,600 nm |
| Transit time (14kt) | ~10 days | ~14 days |
| Draft restriction | 25m (Phillips Channel) | None significant |
| Piracy frequency | Regular (CAT 3-4) | Very low |
| Fuel cost delta | — | +35-40% |
| Congestion risk | High | Minimal |
For a laden VLCC drawing 20+ meters, the Lombok option isn't optional — it's the only option. Malacca is too shallow. But for most vessel classes, the choice is economic: pay 4 extra days of fuel and charter costs, or accept the disruption risk and transit through 550nm of congested, piracy-prone waterway.
This is exactly the kind of decision our Route Advisory feature quantifies. It scores up to five alternative routes and presents the risk-cost tradeoff side by side: risk score, fuel consumption, CO2 emissions, CII impact, ETA distribution.
The question isn't whether Malacca is risky. It's whether the risk justifies 4 extra days and 40% more fuel.
What 369 NAVWARNs look like from the bridge
The global NAVWARN count — 369 active as of right now — is a number that means nothing in isolation. Most navigational warnings are routine: temporary buoy relocations, cable-laying operations, military exercises with coordinates nobody will actually sail through. But some are material.
In the Malacca corridor, NAVWARNs tend to cluster around three things: submarine cable operations (the strait is laced with telecom cables), military exercises by the coastal states, and — increasingly — drifting containers or debris from the sheer volume of traffic. Each active warning contributes to the disruption score because each one represents a potential routing constraint for vessels in the Traffic Separation Scheme.
Why Malacca won't stop being a problem
Hormuz can theoretically be bypassed. Saudi Arabia has pipeline capacity to the Red Sea. UAE has Fujairah on the Gulf of Oman side. Bab el-Mandeb already has vessels rerouting around the Cape of Good Hope when Houthi activity spikes.
Malacca has no real bypass at scale. The Lombok/Makassar alternative works for individual vessels making individual cost decisions. But the global container network — the alliance schedules, the port rotations, the transshipment hub at Singapore — is built around Malacca transit. You can't move Singapore.
Roughly $3.5 trillion in cargo value passes through the Malacca Strait annually. A 48-hour closure — from a grounding, a collision, or a security incident — would create cascading port congestion from Colombo to Shanghai. The last time the maritime industry had to think about this kind of systemic disruption at a chokepoint, the Ever Given was stuck in Suez for six days. Malacca handles more traffic than Suez.
For reinsurers modeling PML (Probable Maximum Loss) exposure, the Malacca Strait is arguably the single highest concentration of insured value transiting one geographic point on Earth. If you're aggregating hull and cargo policies across your portfolio, knowing how many of your insured voyages transit Malacca — and when — is a question worth answering with data, not estimates.
What we track, and what we don't
Honest limitations for the Malacca corridor:
- Our piracy data comes from IMB and ReCAAP. Both rely on voluntary reporting. The actual incident rate in Southeast Asian waters is almost certainly higher than what's reported — ReCAAP themselves acknowledge this.
- We don't model vessel-to-vessel collision risk, which is arguably the primary physical hazard in Malacca. That requires real-time AIS density analysis at a resolution we don't yet do.
- STRAITREP compliance data (which vessels reported, which didn't) isn't publicly available. It would be a valuable signal for disruption scoring if it were.
- Weather in the strait is typically benign — equatorial, low swell, light winds. Our weather signal rarely contributes much to Malacca routing scores. The disruption here is about traffic and security, not sea state.
The disruption score of 50 reflects what the available data sources report. Like any composite, it's a lossy compression of a complex situation. But it's a compression that lets you compare Malacca to Hormuz to Bab el-Mandeb at a glance and allocate attention accordingly.
If you operate vessels that transit the Malacca Strait regularly, or you're underwriting policies for routes through Southeast Asia, I'm curious: at what disruption level would you actually consider the Lombok alternative? Is it a risk threshold, a cost threshold, or something else entirely? The economics of that decision are something I'd like to understand better.
Monitor your chokepoints
Real-time disruption scoring for Malacca, Hormuz, Suez, Bab el-Mandeb, and more. See what's happening right now.
Open the Dashboard