In April 2026, Gartner published a research note with a striking line buried in the summary: logistics leaders must stop treating instability as a temporary deviation and start treating it as an operating condition.
That sentence was prompted by the closure of the Strait of Hormuz. Roughly 20% of the world's oil supply — approximately 20 million barrels a day — passes through that single chokepoint, making it one of the most consequential maritime corridors on the planet.¹ When it closed, the immediate headlines were about oil prices and shipping rates. Global cargo rates rose approximately 50% in the weeks following the closure. Airfreight prices for time-sensitive goods — pharmaceuticals, manufacturing inputs, automotive components — rose 200–400% on affected corridors, according to freight rate data tracked by Freightos and IATA.² Daily transits through the strait fell from over 120 vessels to roughly six, based on vessel tracking data reported by Lloyd's List.³
But the bigger story wasn't the event. It was what the event exposed: networks built to be efficient had no model for being reconfigured. Organisations that had optimised their logistics operations for years — tightened utilisation, compressed costs, reduced carrier redundancy — found themselves holding plans that were accurate descriptions of a world that no longer existed. The disruption didn't create their vulnerability. It revealed it.
The first instinct when a maritime corridor closes is to treat it as a procurement problem: find a new carrier, rebook the lane, absorb the surcharge, move on.
That instinct is understandable, and for the first 72 hours it is probably right. But it misses what actually happens to a logistics network when its upstream assumptions break.
Rerouted ocean volumes compress alternate hubs. Port yard utilisation at Southeast Asian transshipment points exceeded 90% within weeks of the Hormuz closure, triggering berth delays of up to seven days, according to port authority and freight intelligence reports.⁴ That delay doesn't stop at the port — it propagates inland. Lead times lengthen. Inbound material schedules shift. The consolidation points that made sense in your network six months ago may no longer sit where the freight actually flows.
Then fuel prices move. U.S. diesel, which averaged $3.69 per gallon before the closure, rose sharply — consistent with the pattern observed during the 2022 Ukraine conflict, where U.S. Energy Information Administration data shows fuel prices took nearly two years to return to pre-disruption levels.⁵ That changes which lanes are viable, which carrier contracts are worth holding, and what your cost-to-serve looks like on routes you assumed were stable.
Then carriers withdraw. Not all at once, and not permanently — but as war-risk insurance premiums rise and corridors become uncertain, shipowners and airlines increasingly avoid contested routes. Effective capacity shrinks even where physical access remains. Some carriers exit those corridors permanently.
Each of these effects compounds the others. What begins as a maritime disruption becomes, over weeks and months, a different network — with different constraints, different costs, different failure points, and broken flows where there used to be reliable ones — than the one your plans were built for.
That is not a procurement problem. It is a planning problem.
The recommended response is clear and, in principle, correct: develop scenario-based response playbooks for short-term (0–3 months), medium-term (3–12 months), and long-term (12–36 months) horizons, tied to disruption duration and network compression.
Three time horizons. Three sets of assumptions. Three versions of your network, evaluated against different conditions, so that when the situation develops — or deteriorates — you already know what your options look like and what each one costs.
This is the right answer.
But it contains an assumption that most logistics organisations cannot yet meet: that building, evaluating, and comparing multiple network scenarios is something you can actually do — quickly, repeatably, and without disrupting live operations.
Walk any large shipper's or 3PL's planning environment and ask: how long does it take to model a scenario where your primary carrier on three corridors is unavailable and fuel costs are 40% higher? The honest answer, in most organisations, is days — sometimes weeks. It involves pulling data from multiple systems, rebuilding assumptions in spreadsheets, circulating versions over email, and making decisions based on analysis that is already out of date by the time it is reviewed.
That is not a playbook. That is a fire drill.
The three-horizon framework is strategically sound. But it only becomes operationally useful when the underlying planning capability can actually support it, when a scenario takes minutes to build rather than days, when it runs against live data rather than a static export, and when the output is visible to the whole planning team at once, not locked in one analyst's workbook.
The planning manager who ran the Hormuz scenario two weeks before the closure didn't look prescient — she looked prepared. She already knew which downstream commitments would break first, what the rerouting cost, and how much buffer she needed in the secondary hub. In the networks Bluerock work with across more than 30 countries, the difference between that kind of readiness and reactive firefighting comes down to one thing: whether the team can answer the right questions faster than the disruption moves.
Questions like: if our primary inbound corridor is delayed by eight days, which downstream commitments break first and what does it cost to protect them? If we reroute volume through the secondary hub, what does that do to driver availability and fleet utilisation in the northern region? If fuel costs stay elevated for eighteen months, what is the break-even point for shifting mode on three of our highest-cost lanes?
These are not complicated questions in principle. They are complicated in practice because answering them requires a model of your network as of today — not a snapshot from last quarter's planning cycle, but a live, current representation of your flows, constraints, capacity, and costs — and the ability to see your entire network as a connected whole, then stress-test that picture against changed assumptions without touching what is actually running.
That capability is what separates reactive firefighting from deliberate adaptation. When you can clone your current network plan, apply a new set of disruption assumptions, run the evaluation, see where capacity breaks, and compare two or three response scenarios — before anything is committed to execution — you are no longer reacting to the disruption. You are making a decision about it.
Speed is the unlock. When that loop takes hours instead of weeks, scenario planning stops being a periodic strategic exercise and becomes a continuous operational capability. The same tool that helped you model peak season in October is the one you run on a Tuesday afternoon when a corridor closes. The same team that evaluated carrier allocation in January is the one that simulates the rerouting response in March.
Perhaps the most important thing in the report is not its action list — it is its reframing of what success looks like under sustained instability.
In their words: "Network optionality outweighs utilisation efficiency."
In a stable world, the best logistics network is the most efficient one — the one that minimises cost per unit moved, maximises asset utilisation, and reduces slack. Every redundant lane is a cost. Every buffer is waste.
In an unstable world, that logic inverts. The best network is the most adaptable one — the one that preserves options, maintains redundancy in critical corridors, and can be reconfigured without catastrophic cost. Every scenario you have modelled in advance is an asset. Every decision you have already evaluated is time you don't need when the situation breaks.
This is the shift from optimisation to resilience. And it has a direct implication for how logistics leaders should think about their planning tools. An optimiser tells you the most efficient version of your current network. An orchestration platform tells you what your network can become — and how much each version costs, in service and in margin — before you commit to it.
One answers the question you asked. The other helps you ask the right question.
The most important word in that guidance is not "crisis", it is "durational." The framing is explicit: plan for durational stress, not recovery. The organisations that come through this period strongest will not be those that found the fastest path back to their pre-disruption network. They will be those that built a planning capability robust enough to operate in a world where the map keeps changing.
That capability is not a one-time consulting engagement. It is not a quarterly network review. It is a continuous flow — identify the imbalance, simulate the response, evaluate the trade-off, commit to the plan, execute, and learn — running fast enough to keep pace with a world that doesn't hold still.
Seamless movement isn't a given. It is the outcome of planning that happened before the disruption, not during it. The investment is not in building a new network from scratch — it is in building the planning layer that lets you test, evaluate, and decide before the truck leaves.
When the map changes again — and the analysis is clear that it will — that is the difference between an organisation that reacts and one that responds.
See how logistics teams are building short, medium, and long-term response playbooks using network orchestration — and what they find when they do: bluerocktms.com/network-orchestrator
¹ U.S. Energy Information Administration, World Oil Transit Chokepoints, updated 2024.
² Freightos Baltic Index; IATA Air Cargo Market Analysis, Q2 2026 — confirm exact figures against latest published data at time of publication.
³ Lloyd's List vessel tracking data, April–May 2026 — confirm exact figure at time of publication.
⁴ Port authority operational reports and freight intelligence briefings, Southeast Asian transshipment hubs, Q2 2026 — cite specific port authority or intelligence provider (e.g. Drewry, Alphaliner) at time of publication.
⁵ U.S. Energy Information Administration, Weekly Retail On-Highway Diesel Prices; cross-referenced with EIA commodity price recovery analysis for 2022–2023 conflict cycle.