What the LBCT rail backlog says about buffer, and why the equipment failure is the least interesting part of the story.

Sometime in June, the ship-to-shore cranes at Long Beach Container Terminal started giving trouble. The terminal has described the problems only as "technical," and has not said much more. Six weeks later, containers leaving that terminal by rail are still catching up.

That is a long tail for a maintenance issue. It is worth understanding why.
‍

What happened

LBCT is the busiest container terminal at the Port of Long Beach by through put. When its cranes ran into repeated technical problems through June, rail containers piled up in the yard.

LBCT president Anthony Otto told the Journal of Commerce at the end of July that dwell times for rail containers had come down from ahigh of seven days, against a terminal target of about 3.5 days. He expects to be back at target later in August. Until then, the backlog persists. The terminal has been running late-night "hoot" shifts for longshoremen specifically to work rail boxes, which is nota routine measure.

The size of the pile was never disclosed. It moves daily with vessel arrivals and discharges.
‍

The failure was random. The pressure was not.

Here is the part the headline skips.

Los Angeles-Long Beach handled 881,159 TEUs of imports in June, the gateway's heaviest month of 2026 so far, according to PIERS. The reason is well documented: retailers pulled fall and holiday merchandise forward to get it into the country before the US tariff reset in late July.

Front-loading ahead of a policy deadline is one of the most legible patterns in trans-Pacific trade. The deadline is announced. Everyone books against it. The surge arrives in a compressed window and then stops.

So the terminal was running its heaviest volume of the year at exactly the moment its equipment failed. That coincidence is what turned a maintenance problem into a six-week one. A crane outage in as lack month is a scheduling nuisance. The same outage at peak inbound volume becomes a yard problem, then a rail problem, then somebody's missed floor date at retail.
‍

It did not stay inside one terminal

Rail container dwell across all 12 container facilities in theLA-LB complex averaged 5.43 days in June, the second-highest figurein 14 months, behind the 6.14 days recorded in January, per thePacific Merchant Shipping Association.

One terminal's equipment problem is visible in a complex-wide average. Congestion rarely stays where it starts. Chassis, drayage capacity, rail slots and labour are shared across the gateway, so pressure at the busiest terminal redistributes to its neighbours.
‍

Where the delay actually lands

The ports of Long Beach and Los Angeles generally cite a benchmark that about one-third of imports move directly from vessel to inland port intermodal rail. Otto says LBCT has been handling very high levels of IPI cargo.

For that third of the cargo, the port is a waypoint, not a destination. The vessel can berth on schedule, discharge on schedule, and the box can still be late to Chicago or Dallas because it sat in the yard waiting for a train.

This is where a lot of shippers are looking at the wrong number. Vessel ETA and berth productivity are easy to obtain and widely reported. Post-discharge dwell is harder to see and often the number that actually decides the delivery date. If your visibility stops at the quay, you will not know you have a problem until the arrival notice does not arrive.
‍

The wider pattern: buffer goes first

Step back from Long Beach and the disruptions of the past several years share a shape. A specific trigger meets a network with no spare capacity. The trigger is never the same twice: a pandemic, a canal, a labour negotiation, a crane. What decides whether it becomes a two-day story or a two-month one is how much slack the system had that particular week.

That should change what you try to forecast.

Nobody can predict when a ship-to-shore crane will fail. But the conditions that make a failure expensive are largely on a calendar. Policy deadlines. Holiday booking peaks. Lunar New Year. Announced capacity withdrawals. These are knowable weeks or months ahead, andthey tell you when your network is least able to absorb a surprise.

What to check now

If you have August intermodal bookings routed through Long Beach:

• Confirm what your ETA covers. Ask your forwarder whether the date you have been given is to the port or to the inland ramp. The difference is where the delay lives.
• Plan against current dwell, not the target. The 3.5-day figure is where LBCT expects to be later in August. It is not where the terminal is today.
• Know your IPI exposure by lane. If a third of your volume moves vessel-to-rail, a third of your volume carries this risk and the rest does not.
• Price the transload alternative before you need it. Moving the box by truck to a nearby facility and reloading is more expensive per container. When rail dwell is running well above target, it can still be the cheaper answer once you count the missed delivery window.
• Watch the calendar, not the news feed. By the time congestion is reported, your booking decisions have already been made.

How we look at this

Worldtop & Meta moves Asia-North America cargo through thisgateway, so we watch it closely. We could not have forecast thecranes. Nobody could.

Resilience is not usually about predicting the accident. It isabout knowing when you cannot afford one.

Shipping into North America this quarter and want a view ofwhere your lane is exposed? Talkto us.

Exceed Expectations, Every Time.

Source: Journal of Commerce, Bill Mongelluzzo, 31 July 2026 —https://www.joc.com/article/lbct-working-around-the-clock-to-thin-backlog-of-intermodal-containers-6262518