Running Mortality Syndrome in Vannamei: Causes, Diagnosis & Prevention

What Is Running Mortality Syndrome in Vannamei?

Running mortality syndrome (RMS) in vannamei is a condition where Penaeus vannamei shrimp die continuously in small numbers — often 0.5–2% of the pond population per day — for weeks at a stretch, instead of dying all at once in a single crash. You will not see hundreds of shrimp floating on one morning. Instead, you find a handful of dead shrimp at the pond edge or in the check tray every single day, and the count barely slows down no matter what you correct in the water.

This slow bleed is exactly what makes RMS so damaging to a season's economics. A single mass-mortality event is obvious and forces an immediate decision — treat, harvest early, or write off the pond. Running mortality syndrome instead erodes the standing crop day after day while the pond otherwise looks manageable, so many farmers keep feeding a shrinking population for weeks before realising how much biomass has actually been lost by the time of harvest.

RMS has been widely reported across vannamei culture in Andhra Pradesh and other Indian shrimp belts since the mid-2010s, usually appearing 45–70 days into the culture cycle. It does not have a single cause. Almost every documented case is a combination of an underlying pathogen — most commonly Enterocytozoon hepatopenaei (EHP) or opportunistic Vibrio species — and a pond environment that is stressing the shrimp enough to let that pathogen take hold.

How Running Mortality Syndrome Differs From a Mass Mortality Event

It helps to separate RMS from the other way shrimp ponds fail. Diseases like White Spot Syndrome Virus (WSSV) or Acute Hepatopancreatic Necrosis Disease (AHPND) typically cause mortality that spikes hard within a few days of onset — you can often lose 50%+ of the pond within a week. An oxygen crash or an ammonia spike kills within hours, tied to a single measurable event.

RMS looks different on every axis. Daily mortality stays in the low single-digit percentage range, cumulative losses build up gradually rather than in a spike, and affected shrimp often show reduced feed intake and visible size variation within the same pond well before the die-off becomes obvious. Survivors frequently show a pale or atrophied hepatopancreas and slower growth, which is one of the clearest tells that EHP is involved rather than a purely bacterial or water-quality event.

What Causes Running Mortality Syndrome in Vannamei?

There is no single organism responsible for every RMS case, which is part of what makes it hard to diagnose from symptoms alone. The pattern that shows up repeatedly in Indian ponds is a base pathogen combined with one or more stress factors that weaken the shrimp's ability to fight it off.

• Enterocytozoon hepatopenaei (EHP): a microsporidian parasite that infects the hepatopancreas, reducing nutrient absorption and growth even when it does not directly kill the shrimp — it is one of the most frequently detected pathogens in RMS-affected ponds
• Opportunistic Vibrio species: bacteria that are present in almost every pond at low levels but multiply rapidly when organic load, temperature, or stress rises, contributing to secondary infections in already-weakened shrimp
• Poor pond bottom condition: accumulated organic sludge from uneaten feed and faecal matter creates localised low-oxygen, high-ammonia pockets at the pond floor where shrimp spend most of their time
• Chronic low-grade stress: repeated swings in dissolved oxygen, ammonia, or pH — even swings that never cross an acutely lethal threshold — keep shrimp in a weakened immune state over weeks
• Poor post-larvae (PL) quality: PL sourced without EHP/AHPND screening can introduce the pathogen into an otherwise well-managed pond from day one
• High stocking density: more biomass per litre of pond water means more competition for oxygen and more organic waste generation, both of which raise baseline stress

The Water-Quality and Stress Connection

A shrimp fighting EHP or a Vibrio load is not fighting it in isolation — it is fighting it while also managing whatever stress the pond environment is putting on it. This is the connection that explains why two ponds stocked with PL from the same hatchery can have very different outcomes: one with stable water quality tolerates a low-level EHP infection with minimal losses, while the other, cycling through daily ammonia and oxygen swings, tips into full running mortality syndrome.

The stress triggers worth tracking are rarely the dramatic ones. It is not usually a single oxygen crash that causes RMS — it is the cumulative effect of repeated, moderate swings that never quite reach an emergency threshold but never let the shrimp fully recover either.

• Dissolved oxygen cycling below 4 mg/L overnight, even if it recovers by morning
• Un-ionized ammonia (NH3) above 0.1 mg/L for sustained periods, especially in the second half of the culture cycle when biomass and feed load are highest
• pH swings greater than 0.5 units within a single day, which usually signal an unstable or crashing algae bloom
• Water temperature swings of more than 3–4°C between day and night, common in shallow ponds during seasonal transitions
• Sustained high organic load at the pond bottom from overfeeding, which raises oxygen demand and ammonia release exactly where shrimp are resting

How to Diagnose Running Mortality Syndrome on Your Farm

Because RMS is a pattern rather than a single test result, diagnosis is a combination of tracking the mortality trend and testing for the pathogens most commonly involved.

None of these steps require guesswork if you keep a simple daily log. The earlier the pattern is recognised, the more management options remain open — including adjusting feed, water exchange, and harvest timing before losses compound further.

• Keep a daily mortality count by pond, not just a periodic estimate — a steady 0.5–2% daily loss over a week or more is the defining signature of RMS
• Send hepatopancreas samples for PCR testing for EHP if growth has slowed or size variation is increasing within the same pond
• Culture pond water and gut samples for Vibrio load, particularly green/yellow colony counts on TCBS agar, if secondary bacterial involvement is suspected
• Check gut fullness and feed response daily — reduced feeding is often the earliest visible sign, appearing before mortality rises noticeably
• Review your water quality log for the two to three weeks before mortality started — repeated ammonia or DO swings in that window point toward a stress-driven case

Prevention and Management Steps

Because RMS is rarely caused by one factor, prevention has to work on both fronts at once: reducing pathogen load coming into the pond, and reducing the environmental stress that lets a low-level infection turn into a running mortality event.

• Source PL from hatcheries that screen broodstock and PL batches for EHP and AHPND — this is the single highest-leverage prevention step available before stocking
• Dry and prepare the pond bottom fully between crops, including removing accumulated sludge, to reduce the organic load that feeds Vibrio and lowers bottom oxygen
• Avoid overfeeding, especially past day 45 when biomass and feed rates are highest — excess feed is the largest controllable source of pond bottom organic load
• Use probiotics (Bacillus-based or nitrifying strains) proactively rather than reactively, to keep ammonia-producing bacteria in check before a spike occurs
• Stabilise water quality parameters rather than just responding to emergencies — the goal is to reduce the frequency and size of swings, not just avoid acutely lethal thresholds
• If RMS has occurred in a pond before, consider a lower stocking density on the next cycle to reduce baseline competition for oxygen and space

Why Continuous Water Quality Monitoring Helps Reduce RMS Risk

Continuous monitoring does not cure EHP or eliminate Vibrio from a pond — no sensor can do that. What it does is remove one half of the equation that turns a low-level infection into running mortality syndrome: the chronic, unmanaged stress from water quality swings that most farms only catch during a morning or evening spot check.

Our IoT monitoring system for shrimp ponds tracks dissolved oxygen, ammonia, pH, and temperature continuously and alerts you the moment a parameter drifts outside the safe range you set — so the swings described above get corrected in hours, not discovered the next morning after several nights of accumulated stress. For the specific safe ranges and sensor placement for oxygen and ammonia, see our guides on dissolved oxygen monitoring for shrimp ponds and how to reduce ammonia in a shrimp pond.

If you already suspect EHP or Vibrio involvement, pair continuous water quality monitoring with the lab testing described above — the two are complementary, not substitutes for each other. A pond with a confirmed EHP-positive result will still benefit from tighter water quality control, because it directly reduces the additional stress load on shrimp that are already fighting the parasite.

Get Ahead of Mortality Syndrome Before It Spreads

Running mortality syndrome is rarely a single-day emergency, which is exactly why it is often caught too late — by the time the cumulative losses are obvious, several weeks of standing crop are already gone. Tracking your daily mortality trend, testing early when growth slows or size variation appears, and tightening control over water quality swings are the three levers that matter most.

If you want to talk through setting up continuous water quality monitoring for your ponds, or just want a second opinion on a mortality pattern you're seeing, book a meeting with the MD. We work with shrimp farmers remotely across India.