Mystery illness affects 134 passengers on Caribbean cruise ship
Summarised from 2 outlets · Updated 19 Nov, 03:38 · Archive
A gastrointestinal illness of unknown cause has sickened 134 passengers and 14 crew members aboard the Caribbean Princess.
An unknown gastrointestinal illness has sickened 134 of the 2,936 passengers and 14 of the 1,132 crew members aboard the Caribbean Princess, a luxury cruise ship sailing through the Caribbean, Colombia and the Panama Canal. The outbreak was first reported to the CDC's Vessel Sanitation Program on Saturday, four days into the 12-night voyage that departed Fort Lauderdale on 11 November.
The CDC said the cause remains unclear, though the symptoms reported include vomiting and diarrhea. Princess Cruises described it as a 'mild gastrointestinal illness' and said most guests remained unaffected. A spokesperson told NBC South Florida: 'While most guests remain unaffected, we are continuing to closely monitor the situation.'
The crew has increased cleaning and disinfecting procedures, collected stool specimens for testing and isolated the sick passengers and crew members. The ship is to return to Florida on 23 November. This is the fourth outbreak aboard a Princess cruise ship in 2026, more than any other cruise line, according to NBC.

How it is being reported
- Mystery sickness bug rips through luxury cruise sailing through CaribbeanThe Caribbean Princess first reported the outbreak to the Center for Disease Control and Prevention's (CDC's) Vessel Sanitation Program on Saturday.Daily Mail · 19 Nov, 03:15
- Mystery gastrointestinal illness sickens more than 100 cruise passengersThe CDC said the cause of the outbreak was not yet known, but the symptoms included diarrhea and vomiting.New York Post · 18 Nov, 21:20
In this story: Caribbean Princess · Princess Cruises · CDC · Fort Lauderdale · Caribbean · Panama Canal · Florida
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)