Back to Resources

Where the Gulf's Ports Stand After Hormuz: Imports Recovering, Exports Stalled

July 2, 2026

When the Strait of Hormuz was confirmed closed on March 2, 2026, Vizion's booking data registered the shock in the same week, in both directions. Bookings into the Gulf's container ports and bookings out of them both fell off together. What has happened since is the more useful story: the two sides have moved to completely different places, and the split is visible port by port.

A note on the data. These are container bookings, not vessel transits, which is why they move early. Origin bookings are exports leaving a port; destination bookings are imports arriving at it. This piece reads both. It is the port-level companion to our country-level view of the same disruption.

The split: imports are climbing back, exports are not

The Gulf’s imports are recovering. Its exports are not.

Weekly bookings at Jebel Ali, Khalifa and Dammam, indexed to the early-February average (=100). Hover any week. Jubail excluded (import data unavailable).

Imports (bookings into the port)Exports (bookings out of the port)
0255075100125Strait closed · Mar 2 ImportsExportsW02W04W06W08W10W12W14W16W18W20W22W24W26
W02 · Imports 129 · Exports 99 (base=100)
W03 · Imports 113 · Exports 116 (base=100)
W04 · Imports 122 · Exports 113 (base=100)
W05 · Imports 116 · Exports 95 (base=100)
W06 · Imports 108 · Exports 98 (base=100)
W07 · Imports 103 · Exports 120 (base=100)
W08 · Imports 77 · Exports 93 (base=100)
W09 · Imports 112 · Exports 89 (base=100)
W10 · Imports 25 · Exports 22 (base=100)
W11 · Imports 10 · Exports 10 (base=100)
W12 · Imports 10 · Exports 5 (base=100)
W13 · Imports 36 · Exports 62 (base=100)
W14 · Imports 21 · Exports 29 (base=100)
W15 · Imports 22 · Exports 27 (base=100)
W16 · Imports 22 · Exports 9 (base=100)
W17 · Imports 25 · Exports 14 (base=100)
W18 · Imports 25 · Exports 9 (base=100)
W19 · Imports 28 · Exports 10 (base=100)
W20 · Imports 27 · Exports 12 (base=100)
W21 · Imports 30 · Exports 15 (base=100)
W22 · Imports 29 · Exports 14 (base=100)
W23 · Imports 33 · Exports 7 (base=100)
W24 · Imports 42 · Exports 12 (base=100)
W25 · Imports 31 · Exports 16 (base=100)
W26 · Imports 32 · Exports 23 (base=100)

Source: Vizion booking data, weekly, 2026 W02–W26. Strait of Hormuz closure confirmed 2 March 2026.

Indexed to their early-February average, imports and exports at the three Gulf ports with clean data on both sides, Jebel Ali, Khalifa, and Dammam, told the same story until March, then diverged. Both collapsed to roughly a tenth of normal in the first weeks after the closure. Imports then began climbing and now sit near 35% of their pre-closure level. Exports never moved off the floor and sit near 11%.

Jebel Ali is the clearest case. Its import bookings fell from about 24,700 per week to a low of 3,084 in week 11, then recovered to roughly 11,400 per week by June, close to half of normal. Its export bookings fell from about 10,900 per week to roughly 1,200 and have stayed there. Same port, same closure, opposite trajectories.

Where each port stands now

Where the ports stand: exports vs imports

Change in weekly bookings, early February to June 2026. Negative is below the pre-closure baseline. Hover a port.

Exports vs early FebImports vs early Feb
-100%-50%+0%+50%+100%-89%-54%Jebel AliUAE-85%-48%KhalifaUAE-98%-92%DammamSaudi Arabia+60%+117%JeddahSaudi Arabia (Red Sea)
Jebel Ali (UAE)
Exports -89% · Imports -54% vs early Feb
Khalifa (UAE)
Exports -85% · Imports -48% vs early Feb
Dammam (Saudi Arabia)
Exports -98% · Imports -92% vs early Feb
Jeddah (Saudi Arabia (Red Sea))
Exports +60% · Imports +117% vs early Feb

Source: Vizion booking data. Change is June (W23–W25) vs early-Feb baseline (W06–W09). Jubail import data unreliable and omitted.

Measured against the early-February baseline, this is the current standing:

Two patterns stand out. Dammam, on Saudi Arabia's Gulf coast, is near zero on both sides and has not recovered. Jeddah, on the Red Sea, grew on both sides, and its import bookings more than doubled. The Gulf ports that depend on Hormuz went quiet; the Red Sea gateway absorbed the region's trade.

Imports found the Red Sea door

The reason imports recovered is that the region's inbound trade found another way in. As inbound bookings collapsed at the Gulf ports, they climbed at the Red Sea. The Gulf ports lost roughly 25,000 inbound bookings per week against their baseline. Jeddah gained close to 16,000 per week over the same period, with smaller additions at King Abdullah and Sohar, accounting for about 69% of the lost Gulf inbound volume.

That is a regional read, not a clean port-to-port swap. Some of Jeddah's rise is Saudi restocking after the spring supply gap, and goods bound for the UAE do not simply reappear at a Saudi port. Salalah's inbound also more than tripled, but that traces to Cape-of-Good-Hope transshipment tied to Red Sea avoidance, a separate disruption, so it is left out of the count here. Even with those caveats, the shape is unambiguous: imports to the region largely kept flowing, through the Red Sea instead of Hormuz.

Exports never found one

The export side has no equivalent. Of the roughly 21,800 export bookings per week the Gulf ports lost, only about 5,500 reappear anywhere in the data, almost all of it at Jeddah as Saudi Arabia shifted export volume west across its land bridge. That is about a quarter. The remaining three-quarters does not show up at any port in this dataset.

It is worth being precise about what that means. It is a statement about visibility, not a claim that the cargo was destroyed. The missing export volume could be stranded in the Gulf, re-sourced from origins outside the region entirely, or moving through ports this dataset does not cover, including Fujairah, the UAE's only container port outside the strait. Fujairah is not in this data. It is a modest container facility built mainly around oil storage and bunkering, and it was struck directly during the March attacks on the emirates, so it is an unlikely home for the bulk of the missing volume, but the booking record cannot close that question on its own.

Why the two sides diverge

The split has a plausible logic, offered as a read rather than a proof. Imports answer demand. The region still needs goods, so importers reroute to whatever door is open and keep ordering. Exports answer supply and standing contracts. Re-establishing export flows means rebuilding carrier slot agreements, repositioning empty equipment, and restarting production decisions that were disrupted for months, which takes longer than redirecting an inbound booking. The booking data shows the demand side adapting quickly and the supply side still stalled.

The control, and the timeline

Two checks support reading this as Hormuz-specific. Israel's Mediterranean ports, Haifa and Ashdod, kept running throughout, so this is not a region-wide shipping collapse. And the timing tracks the conflict: the break lands in week 10, the week of the closure; a partial rebound appears in weeks 13 to 15 around the late-March signals and the April 8 ceasefire; and the strait re-closing on April 18 and 19 shows up as a renewed drop.

Why this shows up in bookings first

Customs records confirm what already sailed. Booking signals show what shippers are committing to now, which is why the closure registered here the same week it happened, and why the import recovery and the export stall are visible now rather than after the customs record catches up. For anyone managing Gulf exposure, that lead time is the difference between reacting to the shift and positioning for it.

TradeView tracks origin and destination booking signals across global ports in near real time. See how TradeView reads disruptions as they form.

Get the Most Advanced Visibility into the Journey of Your Ocean and Rail Containers

Talk to one of our supply chain experts to get started now.

Talk to an Expert

Thank you for your submission!

A member of the Vizion team will be in touch shortly.
Oops! Something went wrong while submitting the form.

Talk to an Expert

Thank you for your submission!

A member of the Vizion team will be in touch shortly.
Oops! Something went wrong while submitting the form.
close modal icon

Book a Demo

Are you ready to experience the many benefits of container visibility? Schedule a VIZION API demo today.

Thank you for your submission!

A member of the Vizion team will be in touch shortly.
Oops! Something went wrong while submitting the form.
close modal icon

Where the Gulf's Ports Stand After Hormuz: Imports Recovering, Exports Stalled

July 2, 2026

When the Strait of Hormuz was confirmed closed on March 2, 2026, Vizion's booking data registered the shock in the same week, in both directions. Bookings into the Gulf's container ports and bookings out of them both fell off together. What has happened since is the more useful story: the two sides have moved to completely different places, and the split is visible port by port.

A note on the data. These are container bookings, not vessel transits, which is why they move early. Origin bookings are exports leaving a port; destination bookings are imports arriving at it. This piece reads both. It is the port-level companion to our country-level view of the same disruption.

The split: imports are climbing back, exports are not

The Gulf’s imports are recovering. Its exports are not.

Weekly bookings at Jebel Ali, Khalifa and Dammam, indexed to the early-February average (=100). Hover any week. Jubail excluded (import data unavailable).

Imports (bookings into the port)Exports (bookings out of the port)
0255075100125Strait closed · Mar 2 ImportsExportsW02W04W06W08W10W12W14W16W18W20W22W24W26
W02 · Imports 129 · Exports 99 (base=100)
W03 · Imports 113 · Exports 116 (base=100)
W04 · Imports 122 · Exports 113 (base=100)
W05 · Imports 116 · Exports 95 (base=100)
W06 · Imports 108 · Exports 98 (base=100)
W07 · Imports 103 · Exports 120 (base=100)
W08 · Imports 77 · Exports 93 (base=100)
W09 · Imports 112 · Exports 89 (base=100)
W10 · Imports 25 · Exports 22 (base=100)
W11 · Imports 10 · Exports 10 (base=100)
W12 · Imports 10 · Exports 5 (base=100)
W13 · Imports 36 · Exports 62 (base=100)
W14 · Imports 21 · Exports 29 (base=100)
W15 · Imports 22 · Exports 27 (base=100)
W16 · Imports 22 · Exports 9 (base=100)
W17 · Imports 25 · Exports 14 (base=100)
W18 · Imports 25 · Exports 9 (base=100)
W19 · Imports 28 · Exports 10 (base=100)
W20 · Imports 27 · Exports 12 (base=100)
W21 · Imports 30 · Exports 15 (base=100)
W22 · Imports 29 · Exports 14 (base=100)
W23 · Imports 33 · Exports 7 (base=100)
W24 · Imports 42 · Exports 12 (base=100)
W25 · Imports 31 · Exports 16 (base=100)
W26 · Imports 32 · Exports 23 (base=100)

Source: Vizion booking data, weekly, 2026 W02–W26. Strait of Hormuz closure confirmed 2 March 2026.

Indexed to their early-February average, imports and exports at the three Gulf ports with clean data on both sides, Jebel Ali, Khalifa, and Dammam, told the same story until March, then diverged. Both collapsed to roughly a tenth of normal in the first weeks after the closure. Imports then began climbing and now sit near 35% of their pre-closure level. Exports never moved off the floor and sit near 11%.

Jebel Ali is the clearest case. Its import bookings fell from about 24,700 per week to a low of 3,084 in week 11, then recovered to roughly 11,400 per week by June, close to half of normal. Its export bookings fell from about 10,900 per week to roughly 1,200 and have stayed there. Same port, same closure, opposite trajectories.

Where each port stands now

Where the ports stand: exports vs imports

Change in weekly bookings, early February to June 2026. Negative is below the pre-closure baseline. Hover a port.

Exports vs early FebImports vs early Feb
-100%-50%+0%+50%+100%-89%-54%Jebel AliUAE-85%-48%KhalifaUAE-98%-92%DammamSaudi Arabia+60%+117%JeddahSaudi Arabia (Red Sea)
Jebel Ali (UAE)
Exports -89% · Imports -54% vs early Feb
Khalifa (UAE)
Exports -85% · Imports -48% vs early Feb
Dammam (Saudi Arabia)
Exports -98% · Imports -92% vs early Feb
Jeddah (Saudi Arabia (Red Sea))
Exports +60% · Imports +117% vs early Feb

Source: Vizion booking data. Change is June (W23–W25) vs early-Feb baseline (W06–W09). Jubail import data unreliable and omitted.

Measured against the early-February baseline, this is the current standing:

Two patterns stand out. Dammam, on Saudi Arabia's Gulf coast, is near zero on both sides and has not recovered. Jeddah, on the Red Sea, grew on both sides, and its import bookings more than doubled. The Gulf ports that depend on Hormuz went quiet; the Red Sea gateway absorbed the region's trade.

Imports found the Red Sea door

The reason imports recovered is that the region's inbound trade found another way in. As inbound bookings collapsed at the Gulf ports, they climbed at the Red Sea. The Gulf ports lost roughly 25,000 inbound bookings per week against their baseline. Jeddah gained close to 16,000 per week over the same period, with smaller additions at King Abdullah and Sohar, accounting for about 69% of the lost Gulf inbound volume.

That is a regional read, not a clean port-to-port swap. Some of Jeddah's rise is Saudi restocking after the spring supply gap, and goods bound for the UAE do not simply reappear at a Saudi port. Salalah's inbound also more than tripled, but that traces to Cape-of-Good-Hope transshipment tied to Red Sea avoidance, a separate disruption, so it is left out of the count here. Even with those caveats, the shape is unambiguous: imports to the region largely kept flowing, through the Red Sea instead of Hormuz.

Exports never found one

The export side has no equivalent. Of the roughly 21,800 export bookings per week the Gulf ports lost, only about 5,500 reappear anywhere in the data, almost all of it at Jeddah as Saudi Arabia shifted export volume west across its land bridge. That is about a quarter. The remaining three-quarters does not show up at any port in this dataset.

It is worth being precise about what that means. It is a statement about visibility, not a claim that the cargo was destroyed. The missing export volume could be stranded in the Gulf, re-sourced from origins outside the region entirely, or moving through ports this dataset does not cover, including Fujairah, the UAE's only container port outside the strait. Fujairah is not in this data. It is a modest container facility built mainly around oil storage and bunkering, and it was struck directly during the March attacks on the emirates, so it is an unlikely home for the bulk of the missing volume, but the booking record cannot close that question on its own.

Why the two sides diverge

The split has a plausible logic, offered as a read rather than a proof. Imports answer demand. The region still needs goods, so importers reroute to whatever door is open and keep ordering. Exports answer supply and standing contracts. Re-establishing export flows means rebuilding carrier slot agreements, repositioning empty equipment, and restarting production decisions that were disrupted for months, which takes longer than redirecting an inbound booking. The booking data shows the demand side adapting quickly and the supply side still stalled.

The control, and the timeline

Two checks support reading this as Hormuz-specific. Israel's Mediterranean ports, Haifa and Ashdod, kept running throughout, so this is not a region-wide shipping collapse. And the timing tracks the conflict: the break lands in week 10, the week of the closure; a partial rebound appears in weeks 13 to 15 around the late-March signals and the April 8 ceasefire; and the strait re-closing on April 18 and 19 shows up as a renewed drop.

Why this shows up in bookings first

Customs records confirm what already sailed. Booking signals show what shippers are committing to now, which is why the closure registered here the same week it happened, and why the import recovery and the export stall are visible now rather than after the customs record catches up. For anyone managing Gulf exposure, that lead time is the difference between reacting to the shift and positioning for it.

TradeView tracks origin and destination booking signals across global ports in near real time. See how TradeView reads disruptions as they form.

Talk to an Expert

Book A Demo

Are you ready to experience the many benefits of container visibility? Schedule a VIZION API demo today.

close icon
Only valid business email addresses.
Please include country code.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.