Rollovers, Blank Sailings, and Port Omissions: What Disrupts Ocean Transit and How to See It Coming

Your container tracking shows “In Transit” — and has for two weeks. No updates, no new events, no position data. Is something wrong, or is this normal?

Some of that silence is the normal absence of events during ocean transit. The harder cases are the ones where silence signals an actual disruption — a rollover at origin, a blanked sailing that you weren’t notified about, a transshipment dwell that’s stretched into a missed feeder, or a port omission that diverts your container without warning.

This guide walks through the five tracking events that define the ocean transit leg — In Transit, Transshipment, Rolled, Blank Sailing, and Port Omission — with carrier-specific behavior for each.

In Transit

In Transit is a tracking status indicating that a container is currently on the water between ports, aboard a vessel that is underway.

“In Transit” is not a physical milestone — it is a status that persists from departure until the vessel reaches the next port. It tells you the container is on the water but provides no information about the vessel’s current position, speed, or expected arrival. On a transpacific voyage of 14-18 days, “In Transit” may be the only status you see for the entire ocean leg.

Not all carriers use this label. MSC shows “In Transit” as an explicit status. Others simply show a gap between the departure and arrival events with no intermediate update. The absence of an “In Transit” label does not mean anything is wrong — it just means the carrier does not publish a mid-voyage status.

An MSC container departed Ningbo on March 5. The portal shows “In Transit” from March 5 onward. No new events appear until “Arrived at Transshipment Port” on March 18 in Singapore. The 13 days of silence with only the “In Transit” status are completely normal.

The key operational insight about “In Transit” is knowing when it is normal and when it signals a problem. Two weeks of “In Transit” on a transpacific route is expected. Two weeks of “In Transit” on a 5-day intra-Asia route is not. If the status persists longer than the expected voyage time, check the vessel’s position on an AIS service.

In Transit vs tracking failure: Teams new to ocean tracking often mistake the long silence of “In Transit” for a tracking outage. It is not. Ocean containers do not transmit position data mid-voyage (unless the carrier has IoT-equipped containers). The tracking system simply has no new event to report.

Transshipment

Definition

Transshipment is the process of transferring a container from one vessel to another at an intermediate port (hub) on its way to the final destination.

Explanation

Most ocean freight does not travel on a single vessel from origin to destination. Carriers operate hub-and-spoke networks where large mainline vessels serve major ports, and smaller feeder vessels connect the hubs to regional destinations. Transshipment is the transfer between these vessels. A container booked from Vietnam to a mid-size European port, for example, might sail on a mainline vessel to Singapore, get discharged at Singapore, wait in the hub yard, get loaded onto a feeder vessel, and sail onward to the final destination.

Transshipment is where tracking most commonly goes silent. The container is off the first vessel and in the hub terminal, but it has not yet been loaded onto the connecting vessel. During this dwell period — which can range from 2 days to 3+ weeks — many carriers provide little or no tracking data. The container is physically in the terminal, but no new events fire because no milestone (load, discharge, departure) has occurred.

Carrier granularity varies significantly. Hapag-Lloyd, Evergreen, COSCO, and ZIM publish separate discharge and reload events at the transshipment port, giving you visibility into whether the container is sitting at the hub or has been loaded onto the feeder. CMA CGM and ONE compress transshipment into a single label. MSC’s transshipment visibility is notoriously poor — containers at hubs like Singapore, Busan, and Tanger Med can go silent for weeks.

ZIM and Wan Hai have been documented as providing better transshipment event granularity than average. ZIM’s API includes “additional milestones that allow you to track transshipments through intermediary ports.” Wan Hai provides transshipment events but has documented “transshipment blind zones” where tracking pauses.

Example

An MSC container sails from Ho Chi Minh City to Marsaxlokk, Malta (transshipment hub). It is discharged at Marsaxlokk on March 15. MSC’s tracking shows “Discharged (Transshipment).” For the next 18 days, the portal shows no new events. The container is in the Marsaxlokk yard waiting for a feeder to Piraeus. On April 2, “Loaded (feeder)” finally posts. The ETA for Piraeus changes three times during the wait.

Why It Matters Operationally

Transshipment is the single biggest source of tracking frustration in ocean shipping. The combination of silent dwell periods, potential rolls onto later feeders, and repeatedly changing ETAs makes transshipment legs the hardest part of the shipment to plan around. For supply chains that route through major hubs, building buffer time at the transshipment point is essential. Do not commit to downstream logistics based on the first ETA shown after a transshipment discharge — wait for the “Loaded” event at the hub to confirm the container is on the next vessel.

If your shipments consistently route through transshipment hubs, understanding which carriers have better hub visibility (ZIM, Hapag-Lloyd, Evergreen) versus worse (MSC, CMA CGM, ONE) can inform carrier selection decisions — especially for time-sensitive cargo.

If your shipments span multiple carriers and you’re trying to normalize event taxonomy across them — so an MSC “Discharged (Transshipment)” and a Hapag-Lloyd separate discharge/reload sequence are visible in one consistent view — walk through how ops teams set this up across 100+ carriers in a 30-minute call.

Common Confusion

Transshipment vs direct service: Direct services sail from origin to destination without changing vessels. Transshipment services change vessels at one or more hubs. Direct services have simpler tracking timelines; transshipment services have more events and more silence gaps.

Transshipment discharge vs final discharge: “Discharged” at a transshipment port means the container was offloaded at the hub, not at your destination. Check the port name to distinguish the two.

Rolled

Definition

Rolled means a container was not loaded onto the planned vessel and has been moved to a later sailing, either on the same service or a different one.

Explanation

A rollover (or “roll”) happens when a carrier cannot or does not load a specific container onto the vessel it was booked for. The container remains in the terminal yard and is rebooked onto a later sailing. Rolls can happen for several reasons: the vessel is overbooked and there is not enough space, the container arrived at the terminal after the cut-off time, weight restrictions prevent additional loading, the container is flagged for inspection, or the carrier is prioritizing higher-revenue cargo.

Rolls are one of the most operationally disruptive events in container shipping because they introduce unpredictable delays. A roll adds at minimum one week to the schedule (the frequency of most services), and on routes with less frequent sailings, it can add two weeks or more. The container sits in the origin terminal during this period, and the shipper may or may not be informed proactively.

Most carriers do not publish a “Rolled” event in their tracking. The roll becomes apparent when the expected “Loaded on Vessel” event does not fire, or when the vessel name in the tracking changes from the original booking. On MSC, rolls at transshipment hubs are especially common and frustrating — the container shows “Discharged (Transshipment)” and then nothing for days or weeks while it waits for a feeder with available space.

It is important to distinguish a roll from a blank sailing. A roll affects a specific container — the vessel sails, but your container was not on it. A blank sailing affects the entire voyage — the carrier cancels the sailing altogether, and all booked containers on that vessel are rebooked.

Example

A shipper books a container on an MSC vessel departing Shanghai on March 10. The container gates in on March 8. On March 10, the “Loaded on Vessel” event does not fire. On March 11, MSC’s tracking still shows “Gate In” as the last event. The shipper contacts MSC and learns the container was rolled due to space constraints. It will load on the next sailing on March 17 — a one-week delay.

Why It Matters Operationally

Rolls cascade through the supply chain. A one-week roll at origin pushes back the arrival date by one week, which may mean missed delivery windows, production delays, or stockouts at the destination. For time-sensitive cargo, a roll can be more costly than the freight itself. The lack of proactive notification from most carriers makes it worse — you discover the roll only when the expected event fails to appear.

For teams managing multiple shipments, monitoring for rolls means watching for the absence of events — a “Loaded on Vessel” that should have fired but did not. This negative-event monitoring is one of the hardest things to do with carrier tracking alone and is a common reason teams turn to visibility platforms.

Common Confusion

Rolled vs Blank Sailing: A roll affects specific containers — the vessel sails without your box. A blank sailing cancels the entire voyage — no vessel sails at all. Both result in delays, but blank sailings affect all cargo on that service, while rolls affect only the bumped containers.

Rolled vs delayed: A roll means the container was left behind and rebooked. A delay means the vessel itself is running behind schedule but the container is aboard. The tracking looks different: a rolled container shows no “Loaded” event; a delayed container shows “Loaded” but a later-than-expected departure.

Blank Sailing

Blank Sailing is a scheduled vessel departure that the carrier has cancelled entirely — the ship does not sail on that date, and all booked containers on the service are rebooked to alternative sailings.

Carriers blank sailings to manage capacity against demand. When cargo volumes drop, carriers cancel (blank) voyages to prevent vessels from sailing partially full, which is economically unviable. Blank sailings are a capacity management tool, not an operational failure. They are typically announced 2-6 weeks in advance, though shorter-notice blanking does occur.

A blank sailing affects every container booked on that voyage. All shippers must be rebooked — either to the next sailing on the same service or to an alternative service. This can add 1-2 weeks of delay depending on the service frequency and available capacity on the next sailing.

Blank sailings are distinct from rolls, which affect individual containers. If the vessel sails but your container was not loaded, that is a roll. If the vessel does not sail at all, that is a blank sailing.

CMA CGM announces that its FAL3 service sailing from Shanghai on March 20 is blanked due to low demand. All 500 containers booked on that sailing are rebooked to the March 27 departure. Shippers receive notification 3 weeks in advance.

Blank sailings create cascading delays across supply chains. If you are managing just-in-time inventory, a blanked sailing can cause stockouts. Monitoring carrier announcements for blank sailings — and having backup routing options — is part of proactive supply chain management.

Blank Sailing vs Rolled: A blank sailing cancels the entire voyage (no vessel sails). A roll leaves a specific container behind while the vessel sails with other cargo. Both cause delays, but blank sailings are announced in advance; rolls are usually discovered after the fact.

Port Omission

Port Omission occurs when a carrier skips a scheduled port call on a voyage — the vessel bypasses the port entirely and proceeds to the next port in the rotation.

Port omissions are a schedule recovery tool. When a vessel is running behind schedule, carriers may skip one or more ports on the rotation to get the vessel back on time for subsequent calls. The omitted port’s cargo is either discharged at a nearby alternative port (with onward trucking or feeder connection) or carried over to the next voyage rotation. Port omissions can also occur due to port congestion, weather, labor disputes, or geopolitical disruptions.

For shippers with cargo destined for the omitted port, this is a significant disruption. The container may be discharged at a substitute port and trucked at additional cost, or held aboard until the vessel returns to the omitted port on its next rotation — adding a full rotation’s worth of delay (typically 4-8 weeks).

A vessel on a North Europe service is running 4 days late. The carrier decides to omit the Antwerp call and proceed directly to Rotterdam. Containers originally destined for Antwerp are discharged at Rotterdam and trucked to Antwerp at the carrier’s expense, adding 1-2 days to the final delivery.

Port omissions change the delivery port without the shipper’s consent. Your container may arrive at a different port than planned, requiring revised customs entries, different trucking arrangements, and updated delivery coordination. Monitoring for port omission announcements — and having contingency plans for alternative port discharge — reduces the disruption.

Port Omission vs Blank Sailing: A blank sailing cancels the entire voyage. A port omission skips a specific port — the vessel continues sailing but does not stop at the omitted port.

Frequently Asked Questions

Q: Can I get position updates while a container is “In Transit”?
A: Not from carrier portals (with rare exceptions for IoT-equipped containers). Use AIS vessel tracking services like MarineTraffic or VesselFinder to see the vessel’s current position.

Q: My container has been “In Transit” for three weeks. Should I be concerned?
A: It depends on the route. Check the expected transit time for your origin-destination pair. If the “In Transit” duration exceeds the expected voyage time by more than a few days, contact your carrier.

Q: Why does tracking go silent during transshipment?
A: The container is in the hub terminal yard. No milestone event (load, discharge, departure) occurs during the dwell period, so there is nothing for the tracking system to report.

Q: Which carriers have the best transshipment visibility?
A: ZIM and Hapag-Lloyd provide the most granular transshipment milestones. Evergreen and COSCO also publish separate discharge and reload events at hubs. MSC has the poorest transshipment visibility among major carriers.

Q: Can my container be rolled at the transshipment port?
A: Yes. Containers are frequently rolled at transshipment hubs when feeder space is limited. This is especially common in MSC’s hub-and-spoke network.

Q: Will the carrier notify me if my container is rolled?
A: Usually not proactively. Some carriers send booking-change notifications (OOCL is one), but most require you to discover the roll by monitoring for missing events or contacting the carrier directly.

Q: Can I prevent my container from being rolled?
A: Gate in early (well before the cut-off), ensure documentation is complete, and maintain a strong shipper-carrier relationship. Contracted customers with volume commitments are less likely to be rolled than spot-market bookings.

Q: Do rolls happen at transshipment ports?
A: Yes, and they are harder to detect. At transshipment hubs (especially MSC’s network), containers waiting for feeder connections are frequently rolled when feeder space is tight. The tracking shows “Discharged (Transshipment)” and then silence.

Q: How far in advance do carriers announce blank sailings?
A: Typically 2-6 weeks, though shorter notice does occur. Monitor carrier announcements and schedule update feeds.

Q: Am I automatically rebooked if my sailing is blanked?
A: Usually yes, but the new sailing may be a week or more later. Confirm the rebooking details with your carrier or forwarder.

Q: Will the carrier notify me if my port is omitted?
A: Carriers typically announce port omissions, but notice periods vary. OOCL sends routing change notifications through My OOCL Center. Other carriers may notify via email or require you to check schedule updates.

Q: Who pays for the additional trucking if my port is omitted?
A: This depends on the carrier’s policy and your contract. In many cases, the carrier arranges and pays for trucking from the substitute port. Check with your carrier for specifics.