How MSC Container Tracking Actually Works: What the Portal Shows, What It Doesn't, and What the Events Mean

Key Takeaways

Physical-to-digital lag runs 2-12 hours. Events are synced 2-4 times daily, so what you see is never truly real-time.
Transshipment visibility is MSC’s biggest weakness. Containers moving through hubs like Singapore, Busan, and Tanger Med can go silent for days or weeks, with ETAs changing repeatedly.
Track by Master B/L instead of container number for a fuller picture during transshipment legs. Container-level tracking often drops updates between feeder vessel connections.
The myMSC portal adds bulk tracking, Last Free Date visibility, and document access — features the public tracker does not offer.
MSC’s API is gated behind a sales rep and hosted at developerportal.msc.com. It supports DCSA Track and Trace v1.2 and v2.2, but fees may apply.
Schedule reliability sits at 61-70% monthly, ranking MSC third among the top 13 global carriers in the second half of 2025.

Schedule reliability figures, update cadence estimates, and carrier performance data referenced in this guide are based on third-party industry reports and may reflect specific monthly snapshots rather than sustained averages. Carrier systems and capabilities are subject to change.

What the Portal Shows You

MSC offers two tracking interfaces, and the difference between them matters more than most teams realize.

The public tracker at msc.com/en/track-a-shipment is open to anyone. No account required. You can search by container number, bill of lading number, or booking reference. The results page returns a timeline of milestone events with dates, port names, and vessel names. It works fine for checking on a single box, but there is no way to track multiple containers at once, no Last Free Date information, and no access to shipping documents.

The myMSC portal is the registered-user platform. It adds bulk tracking (paste a list of container numbers), Last Free Date visibility, document downloads (B/Ls, arrival notices, invoices), and email notifications. If you ship on MSC with any regularity, myMSC is the minimum you should be using. As of July 2025, MSC also launched email notifications for non-myMSC users — triggered when key milestones fire — though the detail level is thinner than what the portal itself shows.

Identifier coverage is broad. MSC’s primary container prefix is MSCU, but you will also encounter MEDU, MSBU, MSDU, and MSGU containers in their fleet. All are trackable through the same portal. If you are unsure which identifier to use, our guide on container numbers, B/Ls, and booking references covers when each one gives you the best results.

Event Names and What They Mean

MSC uses its own set of tracking event labels. If you also track on Maersk, CMA CGM, or ONE, you will notice that the same physical event often has a different name. The table below maps MSC’s labels to plain-English descriptions and the corresponding DCSA standard event codes where applicable.

MSC Event Label	What Actually Happened	DCSA Code
Booking Confirmed	MSC accepted the booking request and allocated space	—
Gate In	Laden container entered the origin terminal	GTIN
Loaded (at POL)	Container was lifted onto the vessel at the port of loading	LOAD
Vessel Departed	Ship left the port of loading	DEPA
In Transit	Container is on the water between ports	—
Arrived at Transshipment Port	Vessel reached the intermediate hub port	ARRI
Discharged (Transshipment)	Container was unloaded at the transshipment hub	DISC
Loaded (feeder)	Container was loaded onto a connecting feeder vessel	LOAD
Vessel Arrival (at POD)	Ship arrived at the final destination port	ARRI
Discharged (at POD)	Container was unloaded from the vessel at destination	DISC
Gate Out	Container left the destination terminal (picked up by trucker)	GTOT

A few things to flag in this table. The “In Transit” event is not a physical milestone — it is a status that persists between departure and arrival. It tells you the container is on the water, but nothing about where on the water. If you see “In Transit” for two weeks on a five-week voyage, that is normal behavior, not a tracking failure.

“Discharged” appears twice in any transshipment routing — once at the hub port and once at the final destination. If you are reading the tracking timeline and see “Discharged” before the container has reached its destination, check the port name. It is likely a transshipment discharge, not the final unload.

MSC does not surface an “Available for Pickup” event in its public tracking. After “Discharged (at POD),” the next event is typically “Gate Out.” The gap between those two events — which might be days — is where customs holds, freight holds, and terminal availability all happen, and MSC’s portal will not tell you about them. You will need to check with the terminal or your customs broker independently.

Update Cadence: How Fresh Is the Data?

MSC’s tracking updates are event-driven, meaning the system writes a new entry when a milestone fires rather than polling on a fixed schedule. However, the backend synchronization runs 2-4 times per day. The physical-to-digital lag — the time between when something actually happens at the terminal and when it appears on your screen — ranges from 2 to 12 hours.

What this means in practice: if a container was loaded onto a vessel at 06:00, you might not see the “Loaded” event until anywhere from 08:00 to 18:00 the same day. For most planning purposes this delay is manageable. Where it becomes a problem is at the destination end — if you are dispatching a trucker based on a “Discharged” event, a 12-hour lag can mean your driver arrives at a terminal before the container is actually available.

Silence does not always mean a problem. On a transpacific voyage of 14-18 days, the only event you will see between “Vessel Departed” and “Arrived at Transshipment Port” (or “Vessel Arrival” for direct services) is “In Transit.” That is normal. Our guide on why tracking stops updating covers the common scenarios where silence is expected versus where it signals something has gone wrong.

Known Gaps and Quirks

Transshipment visibility is the single biggest pain point with MSC tracking. MSC operates the world’s largest fleet and routes a high proportion of its cargo through major hub ports — Singapore, Busan, Marsaxlokk (Malta), Tanger Med (Morocco), and Port Said (Egypt). When a container arrives at one of these hubs and needs to be transferred to a feeder vessel, the tracking timeline often stalls.

The pattern looks like this: you see “Discharged (Transshipment)” at the hub port, and then nothing for days or even weeks. ETAs for the onward leg change repeatedly. The container might sit in the transshipment yard for three weeks before being loaded onto a feeder, and during that entire period the portal shows no new events. Trustpilot reviews from MSC customers consistently cite this as the most frustrating tracking experience across all major carriers.

The underlying issue is operational, not technical. MSC’s hub-and-spoke network means feeder connections are fluid — containers get bumped, reprioritized, and rebooked based on vessel space availability. The tracking system reflects the result of these decisions, not the decisions themselves. You will never see a “Rolled at Transshipment” event because MSC does not publish one.

No “Available for Pickup” status. As noted in the event table, MSC does not publish a combined availability event. Between “Discharged” and “Gate Out,” you are blind to whether the container is held by customs, held for unpaid freight, or sitting ready in the yard. This forces operations teams to make phone calls or check terminal websites independently.

Empty return is invisible. MSC’s public tracking typically ends at “Gate Out.” Whether the empty container was returned to the depot — and whether it was returned within the free time window — does not appear on the timeline. If you need to prove timely empty return for demurrage disputes, you will need the Equipment Interchange Receipt (EIR) from the depot, not MSC’s portal.

ETA accuracy is variable. MSC’s schedule reliability sits at roughly 61-70% on a monthly basis, ranking them third among the top 13 global carriers in the second half of 2025. That means roughly 3 out of 10 arrivals are late. The portal shows estimated arrival dates, but these can shift multiple times during a voyage — especially on routes with transshipment connections. Treat portal ETAs as directional, not precise.

The February 2025 network restructuring matters here. After the dissolution of the 2M Alliance with Maersk, MSC launched its own standalone East/West network. This means vessel schedules, port rotations, and transshipment patterns have all changed since early 2025. If you had built internal benchmarks based on the 2M-era routing patterns, those benchmarks need to be recalibrated.

What to Do When Tracking Breaks

Scenario 1: Tracking stuck on “In Transit” for longer than expected. First, check the vessel schedule. MSC’s portal shows vessel name and voyage number — search for the vessel on MarineTraffic or VesselFinder to confirm its actual position. If the vessel is still underway, the tracking is accurate; the voyage is just taking longer than the original ETA. If the vessel has already arrived at port but your container still shows “In Transit,” the port discharge event has not yet synced. Give it 12-24 hours.

Scenario 2: Container stuck at transshipment hub. This is the most common MSC tracking complaint. If your container shows “Discharged (Transshipment)” for more than 5-7 days with no subsequent “Loaded (feeder)” event, the container has likely been rolled to a later feeder vessel. Contact your MSC booking agent or local office and ask for the confirmed feeder vessel and revised ETA. The portal will not give you this information proactively.

Scenario 3: Different results when searching by container number vs B/L. MSC sometimes returns a more complete event timeline when you search by Master B/L rather than container number. If you are seeing gaps — especially in the transshipment portion — try re-searching with the B/L. This is particularly useful for shipments routed through multiple hubs.

Scenario 4: Portal shows “Vessel Arrival” but terminal says container is not yet available. “Vessel Arrival” means the ship reached the port, not that your container has been unloaded. Discharge can take 24-72 hours depending on the vessel’s stowage plan and the terminal’s crane schedule. Wait for the “Discharged” event before dispatching your trucker.

Scenario 5: You need Last Free Date information. The public tracker does not show Last Free Date. Switch to myMSC (requires a registered account), where Last Free Date is displayed for containers at destination. Alternatively, contact the terminal or your carrier’s local office directly.

API and Integration Options

MSC’s API is not self-service. Unlike Maersk or CMA CGM, which offer developer portals with direct API key registration, MSC gates API access behind a sales representative. You can browse the documentation at developerportal.msc.com, but to get credentials, you need to go through MSC’s commercial team. Fees may apply depending on your volume and the scope of access.

The API supports DCSA Track and Trace versions 1.2 and 2.2. MSC is a founding member of the Digital Container Shipping Association (DCSA), and the API follows the DCSA event structure. This is good news if you are building integrations that need to normalize data across multiple carriers — the event types and codes map to the same standard used by Maersk, CMA CGM, and Hapag-Lloyd.

What the API adds over the portal: programmatic access to milestone events, vessel schedules, and container status for bulk volumes. If you are tracking hundreds of MSC containers, the API is the only scalable path. Polling the portal manually is not feasible at that scale, and screen-scraping MSC’s website is unreliable due to their JavaScript-rendered frontend.

Smart Containers (IoT) launched in 2025. MSC has begun rolling out IoT-enabled containers that report location and condition data directly, bypassing the traditional milestone-based tracking model. This is still early-stage and not available across the full fleet, but it signals MSC’s direction: moving from port-event-based tracking toward continuous GPS-level visibility.

Operational Note: MSC’s transshipment blind spots are the carrier’s most operationally significant tracking limitation. If your supply chain depends on MSC’s hub-and-spoke routing — and most Asia-to-Europe or Asia-to-Latin America lanes do — build in buffer time at every transshipment point. Do not dispatch inland logistics based on the first ETA the portal shows after a transshipment discharge. Wait for the “Loaded (feeder)” event to confirm the container is actually on the next vessel. For teams that need shipment-level visibility across the full transshipment chain, combining MSC’s data with terminal and AIS feeds fills the gaps that the carrier portal leaves open.