The river's logbook for cruise travellers Waterlogged River Cruise Watch

Evidence register

Reported disruptions

Where a source names a ship, operator or departure, this page says exactly which one and where the event was reported. Waterlogged does not turn a low gauge or a navigation notice into a claim that your cruise is cancelled.

Register checked through Saturday 1 August 2026. Reports can arrive late or change; confirm your own sailing directly with its operator.

Named cruise reports

These records name an operator, ship or departure in the linked source. They are not a prediction about another sailing on the same river.

Danube · low water

Viking Ullur

primary-source record
When
Tuesday 28 July 2026
Where reported
Opposite Gomotartsi, about 25 km upstream from VidinLocation reported as Danube river-km 817.
What was reported
grounding, passenger evacuation
Status
All 186 passengers reported evacuated; complete cruise outcome not established

The Bulgarian News Agency, citing Border Police, reported that Viking Ullur grounded during low water and that 186 passengers were evacuated. The source does not establish that the complete cruise was cancelled.

Evidence limit: The official-message reporting names the vessel, location, event and evacuation count.

Danube · low water

Avalon Waterways

primary-source record
When
Wednesday 22 July 2026 –Monday 27 July 2026
Where reported
Danube — specific reach not stated in the advisoryDo not infer the blocked location from the itinerary or a nearby gauge.
What was reported
departure cancellation
Status
Operator advisory reported the listed departures cancelled
Named departures
WBD/WBDE 0722 · WBD/WBDE 0723 · WBD/WBDE 0727

Avalon reported cancelling the named Danube Dreams departures because of low water. The advisory did not identify a specific blocked reach, so Waterlogged does not assign one.

Evidence limit: The operator's own advisory identifies the sailing codes and cancellation.

  • Travel update · Avalon Waterways · operator advisory · checked Saturday 1 August 2026

Not cruise-cancellation reports. These authority notices identify affected waterway locations and operational restrictions. Operator, ship and passenger-outcome fields are deliberately blank unless a separate source names them.

Danube · low water

Official navigation notice

primary-source record
When
Wednesday 29 July 2026 –Wednesday 30 September 2026
Where reported
Hungarian DanubeReview the linked notice for its authoritative scope and instructions.
What was reported
navigation notice
Status
Notice listed for 29 July through 30 September 2026; not described here as a closure

PannonRIS listed low-water notice 070/Du/2026. A navigation notice is a waterway condition, not evidence that any particular cruise changed or was cancelled.

Evidence limit: Confirmed for the notice identity and listed validity; no cruise outcome is inferred.

Danube · low water

Official navigation notice

primary-source record
When
Tuesday 28 July 2026 –Monday 17 August 2026
Where reported
Austrian Danube, notice 107/00No-wash section as listed by viadonau.
Austrian Danube, notice 108/00No-wash section as listed by viadonau.
What was reported
no-wash restriction
Status
Restrictions listed through 17 August 2026; navigation closure not reported

viadonau listed no-wash restrictions in two Austrian Danube sections. These operational restrictions do not establish a cruise cancellation, ship swap or missed port.

Evidence limit: Confirmed for the listed restrictions, locations and validity; passenger impact remains unknown.

Historical evidence

Useful context for what operators have reported or what court records allege—not a base rate for the next sailing.

Rhine · low water

Viking

primary-source record
When
Saturday 1 January 2022 –Saturday 31 December 2022
Where reported
Rhine — individual low-water reaches not identified in the filingAggregate operator disclosure only.
What was reported
ship swap
Status
Historical aggregate operator disclosure

Viking disclosed that identical Longships were positioned on opposite sides of low-water areas and that 14% of its 2022 Rhine sailings involved ship swaps. The aggregate does not identify individual sailings and does not establish a fleetwide cancellation rate.

Evidence limit: The percentage and mitigation description are the operator's own aggregate regulatory disclosure.

Rhine · Moselle · Main · Danube · low water

Scenic / Evergreen / Emerald

primary-source record
When
Friday 1 June 2018 –Monday 31 December 2018
Where reported
Rhine, Moselle, Main and Danube river systemsThe court notice lists affected sailings; this record does not infer narrower locations.
What was reported
alleged itinerary disruption, litigation record
Status
Historical allegations; no judgment or settlement located in the reviewed record

A NSW Supreme Court notice identifies 21 Scenic, Evergreen or Emerald-branded sailings alleged to have been disrupted by 2018 drought conditions. Scenic denies the allegations. Waterlogged does not describe the litigation as resolved.

Evidence limit: Primary court record confirms the proceeding, dates, brands, named sailings, allegations and denial; it does not prove the allegations or a resolved outcome.

How a report gets onto this page