On the morning of 18 November 2026 the Hapag-Lloyd box TCKU3381848 had shown no new carrier event for 46 days. The last one was a departure from Ningbo on 2 October at 14:25 UTC. The ship carrying it, OSAKA EXPRESS, sent an AIS position at 05:00 UTC that day: 9.84 N, 78.82 W, in the Caribbean, making 10.4 knots. The ship was moving normally.
Container tracking not updating for days looks like a fault. Mostly it is not. I pulled that record from a Navo tracking account with 210 containers in it. Sixty-nine were at sea, in transshipment or about to arrive. Thirty-six of those 69 had gone 14 days or more without a carrier event. Thirty of the 36 still had an ETA in the future. A silent status is the normal state of a loaded box. Telling it from the other kind of silence is the job.
Why container tracking not updating is normal on the ocean leg
Carrier tracking runs on events. A status moves when the line or a terminal records a gate move, a load, a discharge or a departure. Between two ports there is usually nothing to record. Kpler’s guide to container tracking says the same: carrier updates are largely event-driven, so there may be few between departure and arrival.
The DCSA event definitions tag every event as Planned, Estimated or Actual. They set no reporting interval. No document I opened names a number of quiet days that is safe or unsafe.
TCKU3381848 shows the split on one screen. Its last actual line is the Ningbo departure. After that the record holds only planned lines: gate-out at Norfolk on 28 November, arrival on 29 November. A planned line is a schedule entry. Not a move. The TCKU page covers the prefix owner. The Hapag-Lloyd page covers the line that reports the events.
What to check, in this order
Run these steps first.
- Read the last event and its classifier. Actual means it happened. Estimated and planned are forecasts. For TCKU3381848 the last actual is DEPA at Ningbo on 2 October.
- Find the ship named in that event and see where it is. OSAKA EXPRESS was under way at 10.4 knots, crossing the Caribbean. The position comes from AIS, a separate feed from the line, so the two can disagree. The piece on AIS explains why.
- Compare the ETA with today’s date. The carrier ETA for this box was 29 November, 11 days ahead. The published-schedule ETA in the same record said 1 December. Ship moving, ETA ahead: wait.
- Check whether the ETA has already passed. If it has, the silence is no longer the sea’s doing. The article on an ETA that passed without an arrival covers what the tracker is waiting for.
- Open the carrier’s own tracking page. If the line shows newer events than your tracker, the gap sits in the feed. If both show the same last line, take the container number, the date and the last event to the line.
- No events at all? Then the quiet may be a rejected reference, not a ship. The container not found guide sorts those cases.
Most of the quiet boxes in the account stopped at step 3. Twenty-six of the 36 had a vessel position fix from the last 24 hours. The ship was reporting. The line was not. You can run the same check on the track page, and compare the ETA with the sailing schedules. The tracking API returns the event list and the vessel position as JSON.
When a stale status is a real problem
The same account has one. LYGU0034810 is another Hapag-Lloyd box, a 40-foot high cube from Ho Chi Minh City. Its ETA was 10 October, 22:00 UTC, marked estimated. The record shows arrival at Charleston on 14 October and a discharge there at 08:36 UTC. Then a departure line on 15 October at 18:02. The record’s last poll answer from the line is dated 3 November, with no new events in it.
On 18 November the status still read in_transit. That was 33 days after the last event. The ETA was 38 days overdue.
The ship, ANTWERPEN EXPRESS, was at 6.24 N, 92.68 E that morning, in the Indian Ocean at 16.3 knots. The discharge line says the box came off at Charleston. The departure line belongs to the ship. The status still says in transit. Where the box sits now, the record does not say. This is the case where you write to the line, with the number, the discharge timestamp and a request to confirm the location. If you cannot get an answer from the line, contact us with the number.
The API had already marked this one dormant. It suggested archiving it. It did the same for 4 other boxes. Of the 36 quiet ones, only 6 had an ETA in the past, and 5 of those carried that flag.
Frequently asked questions
How many days can a container tracking status stay the same?
There is no fixed number. In a Navo tracking account on 18 November 2026, 36 of 69 moving boxes had gone 14 days or more without a carrier event, and TCKU3381848 had gone 46 days while its ship was under way.
Why does my container show in transit but the ETA has passed?
An ETA that has passed with no new event is the case to take to the line. LYGU0034810 had an ETA of 10 October and a last carrier event on 15 October, so on 18 November its ETA was 38 days overdue.
Is a planned event in tracking the same as a completed one?
No. DCSA event definitions tag events as Planned, Estimated or Actual. The planned gate-out at Norfolk on TCKU3381848 for 28 November was a schedule entry, not a move.
