World Monitor — real-time global intelligence dashboard with live markets, geopolitical data, and infrastructure monitoring

Chokepoint

Strait of Gibraltar

The Strait of Gibraltar is the roughly 14-km-wide gateway between the Atlantic Ocean and the Mediterranean Sea. Every cargo moving between the Mediterranean and the wider ocean — including Suez-bound Europe–Asia traffic — passes through it.

Current status

Strait of Gibraltar disruption pulse

Published pulse

The traffic-light badge is a disruption score, not an operational closure declaration. Transit metrics appear only when the current vessel snapshot has coverage.

Disruption score15Green
Navigational warnings0 warnings
AIS disruptions1 AIS disruption
AIS congestionHigh
Today's transits24
Week-over-week movement+2.7% vs prior week
Open Strait of Gibraltar on the live map →
ConnectsAtlantic ↔ Mediterranean
Position35.9°N, 5.6°W
Energy shock modelNo

Why does every Suez–Europe loop still have to use Gibraltar?

Strait of Gibraltar sits at 35.9°N, 5.6°W and connects Atlantic ↔ Mediterranean. The reference maps 4 modelled trade-route corridors onto this waypoint.

Gibraltar is the Atlantic door of the Mediterranean. Suez delivers Asia–Europe cargo into the eastern Mediterranean; to reach the Atlantic ranges (Rotterdam, the US East Coast via Suez, West Africa) that cargo still exits here. Intra-Mediterranean trades never need it. That split is why Gibraltar appears on Gulf–Europe oil, Singapore–Mediterranean, India–Europe, and Asia–Europe (Cape Route) but not on purely Asian legs.

Four modelled routes use this waypoint: Persian Gulf → Europe (Oil), Singapore → Mediterranean, India → Europe, and Asia → Europe (Cape Route). The Cape loop still re-enters Europe’s Atlantic approaches and is therefore in this set even when it skipped Suez. There is no EIA oil-transit baseline and no energy shock model; the oil that does pass is already attributed to Hormuz/Suez/Bab el-Mandeb in that series.

World Monitor does not enable the energy shock model on this waterway. This waterway has no row in the committed 2023 EIA World Oil Transit Chokepoints series.

There is no second sea gate between the Atlantic and the Mediterranean. The overland options are pipeline and rail across Iberia or the Maghreb, which do not move the container loops. A Gibraltar closure would trap Mediterranean shipping inside the basin the way a Bosporus closure traps the Black Sea, at a much larger cargo scale.

Major trade routes through Strait of Gibraltar

Modelled trade-route corridors through Strait of Gibraltar. Volumes are World Monitor corridor figures as of .
RouteCategoryModelled volumeAs of
Persian Gulf → Europe (Oil)Energy6.5M+ bpd
Singapore → MediterraneanContainer10M+ TEU/year
India → EuropeContainer6M+ TEU/year
Asia → Europe (Cape Route)Container5M+ TEU/year

How to read this page

The crawlable Dataset is the registry-and-route snapshot under the chokepoint disruption methodology. Live pulse tiles are a separately frozen observation and are not copied into this Dataset. Modelled corridor volumes are dated .

Template revision 2026-09-03. Reference observation . This note is a methodology-revision stamp, not a live AIS clock. Published revisions that affect this page are in the corrections log.

Questions about Strait of Gibraltar

Do Cape of Good Hope sailings still use Gibraltar?

Europe-bound Cape loops that discharge in the Mediterranean or transit to Mediterranean hubs still use Gibraltar. Pure Atlantic European discharge can avoid it.

Is Gibraltar shock-modelled?

No. World Monitor does not enable the energy shock model here and does not assign an EIA 2023 oil-transit baseline to Gibraltar.

Which modelled trade routes use Strait of Gibraltar?

Strait of Gibraltar is a waypoint on Persian Gulf → Europe (Oil) (6.5M+ bpd); Singapore → Mediterranean (10M+ TEU/year); India → Europe (6M+ TEU/year); Asia → Europe (Cape Route) (5M+ TEU/year). Those corridor volumes are World Monitor modelled figures dated March 14, 2026 in src/config/trade-routes.ts.

Related

Download: reference.json. Source: src/config/chokepoint-registry.ts and src/config/trade-routes.ts. Captured 2026-04-09. Methodology: how chokepoint disruption is scored.