India → USA Shipment Tracker

Missed transshipment connection: your feeder arrived after the mainline vessel cut off (or the mainline was full), and the next service with space was days out. It's the lane's most common invisible delay — the bill of lading shows one journey but two vessels. Track the transshipment hub as an explicit milestone and ask your forwarder for the ACTUAL connection vessel, not just the mother-vessel ETA.

Published schedules say 24–35 days East Coast via Suez; West Coast routings vary via transshipment. Reality adds origin dwell, destination clearance and the lane's specific friction (most india–us cargo transships (colombo, salalah, jebel ali)). Your own log is the honest answer: after 15–20 shipments the actual door-to-door distribution — including the tail — is sitting in your CSV export.

Pre-Diwali factory pushes and Q4 US retail stack onto the same sailings. Peak behaviour to expect: space sells out earlier, rollover risk rises, rates firm, and the lane's chokepoints run hotter. Rows you add in those windows should carry earlier bookings and more conservative ETAs than the same route in the slack months.

Because lanes have personalities — different chokepoints, peaks and failure modes — and mixing them averages the signal away. A dedicated board per major lane keeps the dataset clean: this lane's transit distribution, this lane's exception causes, this lane's carrier ranking. That's the granularity rate negotiations and buffer-stock math actually need.