Current status: what cargo ship is stuck in the Suez Canal
As of the latest available operational reports, the vessel currently causing a blockage in the Suez Canal is the container ship Ever Given, operated by Evergreen Marine. The ship ran aground on 23 March 2021 while traveling northbound, near kilometre mark 113 (Bramble Junction), closing both travel lanes. No injuries were reported, and partial efforts to refloat the vessel began shortly after grounding through tidal assistance and tug support.
By 29 March 2021, a combination of hull inspections, dredging, and sustained tug operations had cleared the bow and stern, and the canal was fully reopened to traffic. This status clarification reflects the resolved event that drew global attention; the following sections provide enduring context on ship identification, grounding causes, and mitigation measures useful for understanding similar incidents.
Ever Given: identification and vessel profile
Ever Given is a Panamax containership built in 2018 by Imabari Shipbuilding in Japan. Operated by Evergreen Marine under the flag of Panama, it is one of the larger ships in the canal at the time of the incident, with a length of approximately 400 metres and a beam of about 59 metres. Below is a concise verified profile of the vessel and the incident metrics.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Vessel name | Ever Given | Operator and registries |
| Operator | Evergreen Marine Corp. | MarineTraffic/Operator filing |
| IMO number | 9824674 | IMO ship database |
| Build year | 2018 | Class registry |
| Length | ≈400 m | Construction specifications |
| Beam | ≈59 m | Construction specifications |
| Grounding date | 23 March 2021 | Canal Authority notices |
| Canal section affected | Northbound lane near km marker 113 (Bramble Junction) | SCA notice and AIS data |
| Canal closure duration | ≈6 days (blocked 23–29 March 2021) | SCA daily traffic bulletins |
| Refloating method | Dredging, tug assistance, hull inspection, tidal leverage | SCA incident report and news briefings |
Grounding mechanics: why did the ship get stuck?
The grounding was attributed to a combination of environmental and operational factors. Strong lateral winds, locally recorded at 30–40 knots, pushed the vessel sideways (beam reach) while it was in a high-speed transit zone. At the same time, the ship may have experienced a loss of hydrodynamic steering response, reduced effectiveness of the rudder at certain speeds, and possible misjudgment of set and drift in a critical reach near the canal bend. Although initial speculation included speculation about a cyber event or hull failure, official statements from the Suez Canal Authority (SCA) emphasized weather and handling dynamics rather than systemic infrastructure issues.
Weather and canal limits
The Suez Canal has narrow, straight reaches with limited room for corrective manoeuvring, especially for large vessels at or near canal limitations. When lateral forces exceed the vessel’s ability to maintain course using thrusters and rudder, the risk of bank contact and grounding rises. In Ever Given’s case, the canal segment near Bramble Junction offers little width margin, so a single uncommanded drift angle can quickly lead to hull contact and progressive immobilisation as the bow embeds.
Immediate response and mitigation actions
Once grounded, the Suez Canal Authority deployed a coordinated incident response aligned with standing contingency plans. Tugboats were dispatched from Suezport and nearby anchorages to provide bollard pull and lateral control. Dredgers worked to deepen and widen the channel around the hull to reduce bottom friction and allow tidal movements to assist refloating. Continuous monitoring of tides, hull stresses, and bank stability informed each incremental adjustment. The sequence below summarises key response milestones in clear, operational terms.
- Grounding detection and initial notification (23 March, within minutes of arrival)
- First tugs on scene and cautious pulling trials (same day)
- Deployment of additional tug support and dredging assets (24–25 March)
- High-tide assisted pulling and stern release (25–26 March)
- Hull inspection and bank remediation works (27 March)
- Final refloating and north–south passage clearance (28–29 March)
Operational and systemic lessons
Ever Given’s prolonged blockage exposed practical insights for canal design, traffic management, and incident command. One lesson is the value of bank configuration and realtime monitoring to detect early drift. Another is the importance of conservative speed policies in constrained segments, especially under marginal weather. The response underscored how integrated tug–dredge packages can shorten canal closure duration, and why clear communication protocols between pilots, tugs, and the control centre reduce escalation risk. These takeaways support more robust playbooks for future events rather than attributing the incident to a single cause.
Recovery and commercial implications
Following refloating, Ever Given underwent hull inspections at Great Bitter Lake, where no major structural breaches were found. The ship proceeded under its own power to Suez for further checks before returning to service. From a commercial standpoint, the incident generated substantial salvage and lost-time costs, including canal dues, tug and dredging expenses, and compensation claims from affected cargo owners. Payouts were coordinated through insurers and liability frameworks under applicable conventions, illustrating the layered risk-management structures that govern ultra-large vessel operations in critical waterways.
Everlasting relevance: why this case matters beyond the moment
Although the Suez blockage has eased, Ever Given remains a reference case for maritime risk analysts, canal authorities, and operators. Its engineering profile, incident timeline, and response metrics are used in training, contingency planning, and infrastructure assessment. The ship continues to trade globally, but the event informs broader debates around channel dimensions, escort protocols in marginal conditions, and technology aids such as realtime drift prediction. Understanding this case helps stakeholders anticipate and mitigate similar disruptions in deep-draft waterways worldwide.
Quick reference: key identifiers and incident metrics
| Metric | Estimate or Range | Context |
|---|---|---|
| Vessel type | Panamax containership | Fits above Suezmax baseline but constrained by manoeuvrability |
| LOA | ≈400 m | Longer than many older canal vessels, increasing bank proximity risk |
| Grounding date | 23 March 2021 | Peak traffic period with high schedule density |
| Blockade duration | ≈6 days | One of the longest full closures in canal history to that point |
| Tug deployment | 10–14 tugs at peak | Coordinated portfolio of pull and escort units |
| Dredging volume | ≈250,000–300,000 m3 | Material removed to lower bed around hull |
| Refloating method | Tug pull + high-tide leverage + dredging | Combined physics-based approach to reduce bottom adhesion |
| Commercial impact | Hundreds of millions USD in delays, cargo reroutes, and claims | Illustrates system-wide sensitivity to a single-node obstruction |
Conclusion: clear identification and enduring context
The cargo ship involved in the notable Suez Canal blockage is the containership Ever Given, operated by Evergreen Marine. The incident resulted from a convergence of vessel characteristics, weather, and canal geometry, and it was resolved through a structured, multi-asset response. This status clarification supplies durable facts and operational context that remain relevant for understanding large-cargo ship dynamics and canal risk management, supporting informed discussion long after the immediate event has passed.