Fresh Hormuz Attack Reports Are Now Clogging Jeddah, Creating a New Middle East Freight Risk Beyond the Gulf

A reported projectile strike on a cargo ship near the Strait of Hormuz on August 4 is colliding with a second, more operationally immediate problem for freight buyers: overflow congestion at Saudi Arabia’s Red Sea gateway of Jeddah. The result is a new phase of Middle East-linked disruption in which cargo owners are exposed not only to direct security risk near Oman and the Gulf, but also to rerouting costs, booking limits, and weaker schedule reliability at substitute gateways.

According to the Associated Press, citing the United Kingdom Maritime Trade Operations center, a cargo ship reported being “hit by an unknown projectile” at about 2 a.m. local time on August 4 while transiting the Strait of Hormuz area roughly 37 kilometers, or 23 miles, northeast of Al Khasab, Oman. As of August 4, UKMTO had not publicly identified the vessel, its flag, or its cargo in the notice cited by AP, underscoring that key incident details were still emerging.

The freight story is no longer only about Hormuz transits

For logistics planners, the more important commercial development may be what is happening outside the immediate attack zone. Journal of Commerce reported on August 4 that heavy diverted volumes into Jeddah have triggered surcharges and booking curbs, turning the Saudi port into a visible pressure point for cargo that is trying to avoid Persian Gulf exposure.

That changes the risk profile. In the spring, the central question was whether ships could move through or out of the Gulf at all. In early August, the picture is more layered: some cargo is still moving, but the operational strain is being displaced into alternate Red Sea routings, transshipment plans, and cross-border Saudi landbridge solutions.

What happened off Oman on August 4

The August 4 incident fits a pattern of recurring merchant-vessel attacks and security warnings in and around the Strait of Hormuz during 2026. AP said the strike report came from UKMTO and placed the event near Al Khasab on Oman’s Musandam Peninsula, one of the most sensitive stretches of the waterway for merchant shipping. AP also reported that no further identifying information on the ship had been released at the time of publication.

That lack of detail matters. Without a named vessel, operators and cargo interests cannot yet tell whether the ship was a liner vessel, bulker, tanker, feeder ship, or a ship serving a particular industrial lane. But the operational takeaway is clear enough: even without a full closure scenario, fresh attacks or attempted attacks can still force carriers to revise acceptance policies, alter routings, and tighten network controls with very little notice.

UKMTO continues to describe itself as a primary maritime security reporting point for the region and asks vessels in its reporting area to maintain contact and report incidents through its voluntary reporting framework, making its notices one of the most important primary sources for real-time merchant-shipping risk in the area. See UKMTO’s operations portal.

Why Jeddah has become the next pressure point

Jeddah matters because it is not just a Saudi import gateway. It is also a practical workaround node when cargo that would normally move deeper into the Gulf must be re-sequenced through the Red Sea, then forwarded by feeder, transshipment, truck, or some combination of those modes.

That substitute role is visible in carrier advisories. On July 13, Maersk said it would add a Jeddah call to its AE15 Gemini service in August as part of its trans-Suez structure, while stressing that further network changes would remain dependent on Red Sea security conditions. In other words, carriers were already leaning harder on Jeddah before the August 4 incident.

At the same time, carriers have been progressively restricting how Jeddah can be used for onward cargo. A June 23 CMA CGM customer advisory cited Saudi Ports Authority circular 25 for 2026 and said the line could no longer accept shipments booked to Jeddah for merchant haulage to countries other than Saudi Arabia because of measures aimed at preventing congestion from idling in-transit containers.

Hapag-Lloyd has gone further in successive notices. In a July 9 update, the carrier said merchant-haulage cross-border cargo movements via Jeddah were no longer accepted for consignees outside Saudi Arabia. In a later advisory, Hapag-Lloyd said merchant-haulage cross-border cargo movements via Jeddah were not accepted until further notice, and laid out alternative routings with added charges.

The new costs are not theoretical

Hapag-Lloyd’s latest Jeddah contingency pricing shows how quickly a security event can become a landed-cost problem.

For non-FMC-regulated shipments, the carrier said the charges apply immediately; for FMC-regulated shipments, they apply from August 10, 2026. The published alternatives included:

• Jeddah -> Truck -> Dammam -> Vessel -> Jebel Ali: $2,500 per 20-foot dry container and $4,500 per 40-foot dry container.
• Jeddah -> Truck -> Dammam -> Vessel -> Jebel Ali -> Vessel -> Kuwait, Bahrain, Qatar, Iraq: $3,100 per 20-foot dry and $5,100 per 40-foot dry.
• Jeddah -> Vessel -> Salalah -> Vessel -> Khor Fakkan -> Truck -> Jebel Ali: $2,500 per 20-foot dry and $4,500 per 40-foot dry.
• Jeddah -> Vessel -> Salalah -> Vessel -> Khor Fakkan -> Truck -> Jebel Ali -> Vessel -> Kuwait, Bahrain, Qatar, Iraq: $3,000 per 20-foot dry and $5,500 per 40-foot dry.

Those are not war-risk surcharges in the old sense. They are network-workaround costs tied to rerouting and handling complexity after Jeddah has already become constrained.

How the disruption mechanism works

The current disruption is best understood as a corridor-wide network-management problem rather than a single chokepoint story.

When security risk rises near Hormuz, carriers and cargo owners do not necessarily stop moving freight. Instead, they change the shape of the move. Port calls may be omitted. Bookings may be narrowed to carrier-haulage rather than merchant-haulage options. Cargo may be diverted to Red Sea gateways, transshipped through Salalah or Khor Fakkan, or trucked across Saudi Arabia to reconnect with Gulf services.

Each one of those workarounds consumes scarce capacity somewhere else. Containers sit longer. Inland legs multiply. Vessel strings absorb extra handling and timing risk. Documentation becomes more complex when cargo changes mode or routing midstream. The practical consequence is that reliability can worsen even when cargo technically remains bookable.

Why this is different from the spring Hormuz crisis

This is not simply a rerun of the March-April 2026 Hormuz coverage cycle.

Earlier in the year, many carrier updates centered on booking suspensions, emergency contingency surcharges, war-risk pricing, and the problem of vessels trapped in or unable to enter the Gulf. By contrast, the August 4 story is about spillover: attacks remain a trigger, but the visible pain point has shifted toward overflow gateways and commercial controls.

That distinction matters for industrial freight. Project cargo, machinery, chemicals, mining inputs, power-generation equipment, and other time-sensitive shipments can be disrupted even if they never sail directly into the most dangerous part of the Gulf. If a substitute gateway is congested, the backup plan becomes its own source of delay and cost.

What remains uncertain

Several details still need confirmation beyond the initial August 4 reporting.

The attacked vessel’s identity, operator, flag, cargo type, and extent of damage were not publicly established in the AP report. It also remains unclear whether additional August 4 carrier advisories will broaden booking restrictions or add further Jeddah-related surcharges in the coming days.

Just as important, public visibility into actual dwell times, berth waiting, and vessel bunching at Jeddah remains limited. Carrier notices clearly show restrictions and workaround charges, but hard port-performance data have been harder to verify publicly than the commercial controls themselves.

What logistics teams should watch next

The immediate watchpoints are straightforward:

1. Carrier acceptance rules

The difference between merchant-haulage and carrier-haulage acceptance is now operationally decisive for some Middle East moves. Cargo that looked routable a few weeks ago may no longer be accepted under the same terms.

2. Jeddah onward-routing feasibility

A booking into Jeddah is no longer the same thing as a predictable path to Kuwait, Bahrain, Qatar, Iraq, the UAE, or eastern Saudi destinations. The inland and feeder leg now deserves the same scrutiny as the ocean leg.

3. Surcharge stacking

Emergency contingency pricing, rerouting charges, transshipment costs, trucking legs, and storage exposure can stack quickly if cargo misses a connection or falls outside the carrier’s preferred flow.

4. Exposure beyond Saudi cargo

The knock-on effects extend beyond imports for western Saudi Arabia. India-Gulf loops, Red Sea services, East Africa connections, and upper-Gulf industrial supply chains can all feel the impact if carriers keep reallocating capacity around Jeddah and other substitute nodes.

For CAP Logistics readers, the practical response is to build more routing flexibility into Middle East shipments, confirm surcharge exposure before tendering cargo, and validate the full transshipment or inland path rather than focusing only on whether the primary vessel can avoid the Strait of Hormuz.