Cryptosporidium: The Chlorine-Resistant Parasite — Why a Well-Run Pool Can Still Spread It
Cryptosporidium is a parasite the CDC calls chlorine-resistant: even well-maintained pools can spread it, its oocysts take a CT inactivation value of 15,300 to kill (20 ppm free chlorine for 765 minutes at pH 7.5 or less and 77 degrees or warmer, with no chlorine stabilizer), and at ordinary 1 ppm chlorination that is 15,300 minutes — about 10.6 days. This companion brief reads the CDC's hyperchlorination protocol against the two documented gym-system cases on this site: Bothell, where investigators found no fault, and Gaylord Pacific, where a county cleared a resort to reopen only after verifying the full protocol.
Education only — not medical advice. The health and protocol material below is what the CDC publishes about Cryptosporidium and hyperchlorination, attributed to the CDC, and what the public investigations of the two named facilities found, attributed to them. This page does not diagnose anyone. If you believe an exposure made you sick, see a doctor.
What it is
Cryptosporidium — Crypto, in the CDC’s shorthand — is a parasite, not a mold and not a bacterium, and it belongs on this library’s shelf because its gym habitat is the pool itself. The CDC’s hyperchlorination guidance states its defining property in its first paragraph: Cryptosporidium is a chlorine resistant parasite, so even well-maintained pools, water parks, and interactive fountains can spread Crypto among swimmers. The infectious form is the oocyst, shed in the feces of an infected person; a swimmer who swallows contaminated water can be infected. The illness, cryptosporidiosis, is a diarrheal illness — the cases on this site’s Gym Watch shelf are documented as case counts in official investigations, and this brief does not add symptom claims beyond what those investigations and the CDC publish.
That first CDC sentence does the conceptual work of this entire brief. For most pool organisms on this shelf — Pseudomonas, Legionella — a documented outbreak is evidence of a maintenance failure. For Crypto, the CDC fences that inference off in advance: resistance is the organism’s biology, not the operator’s excuse and not the operator’s fault by itself. What separates a well-run facility from a negligent one, for this organism, is not whether Crypto ever arrived — it is what the facility did next.
The number that governs everything — CT 15,300
Disinfection is measured as CT: the concentration of free chlorine in parts per million, multiplied by the time in minutes, at a stated pH and temperature. The CDC’s protocol to inactivate Crypto requires a CT inactivation value of 15,300, and works the arithmetic in its own table:
- 20 ppm × 765 minutes = 15,300 — the operator procedure: free chlorine raised to 20 ppm, held for 765 minutes (12.75 hours), at pH 7.5 or less and 77°F (25°C) or higher.
- Read the same number at ordinary operating chlorination and its meaning inverts: at 1 ppm, CT 15,300 takes 15,300 minutes — about 10.6 days. A pool can test perfectly in range, every day, and Crypto shed on Monday is still viable the following week. That is not a paradox; it is the definition of chlorine resistance, expressed as a clock.
- The stabilizer fence. The CT 15,300 protocol is the CDC’s procedure when chlorine stabilizer (cyanuric acid) is NOT in the water: the procedure specifies unstabilized chlorine (for example, sodium hypochlorite), pH 7.5 or less, and closure of the venue — all venues sharing the filtration system closed together — with no one entering until hyperchlorination is completed. Stabilized outdoor water is a different, harder problem under the CDC’s separate guidance, and no number from the unstabilized table should be borrowed for it.
The CDC also prints the prevention side: a health department might ask an operator to hyperchlorinate when an outbreak occurs in the community, and an operator might choose to hyperchlorinate regularly — for example, weekly — to keep Crypto levels low. Hyperchlorination is, in other words, both the outbreak response and a published standing practice; a facility that has never run it has not adopted the CDC’s own answer to this organism.
Found in the record — the two cases on this site, read at their own weights
Bothell, Washington — the no-fault case. At the McMenamins Anderson School / North Shore Lagoon pool in August–September 2026, King County investigated a cryptosporidiosis outbreak of 14 ill people, 4 of them lab-confirmed — and announced on September 30, 2026 that it found NO violations and considered the pool well-maintained and compliant. The investigators’ own lesson, carried on the Gym Watch page, is this brief’s thesis in an official voice: even in a very well-maintained swimming pool, Cryptosporidium is very resistant to chlorine. Full record: McMenamins Anderson School, Bothell.
Chula Vista, California — the verified-response case. San Diego County investigated 4 cryptosporidiosis cases (3 lab-confirmed, 1 family-reported) among visitors to the Gaylord Pacific Resort’s aquatic facilities between July 24 and August 15, 2026. The county did NOT establish the resort’s water as the source and did NOT find improper maintenance — both findings stand on the Gym Watch page in full. What the facility then did is the protocol above, executed and verified: it voluntarily closed its 4.25-acre aquatic complex on August 25, ran CDC hyperchlorination (CT 15,300; 20 ppm × 765 minutes) with filter inspection and cleaning, and county inspectors verified the work August 26–28 and cleared reopening on August 28. Full record: Gaylord Pacific Resort, Chula Vista.
Read together, the two cases are the combination this brief exists to make: the same organism, the same official no-fault posture, and two different kinds of proof — Bothell proves a clean record does not prevent Crypto; Gaylord proves what a documented response looks like when a facility treats CT 15,300 as a specification to be verified by the county, not a claim to be taken on trust.
Found together with
Crypto shares treated water — and the management failures that treated water forgives in other organisms but not in this one — with the wet-system bacteria of this library: Legionella, whose outbreaks do document maintenance failure and whose shelf must never be blurred into this one, and Pseudomonas aeruginosa, the hot-tub-rash organism of the same pools, hot tubs, and wet rooms. A diarrheal-illness cluster and a legionellosis cluster are different records with different organisms and different inferences, and this site keeps them fenced as such on every page that carries both.
What a member can actually check
You cannot test a pool for Crypto from the deck. What you can do is ask the questions this brief makes legible: Does the facility have a written Crypto / diarrheal-incident response? When did it last hyperchlorinate, at what concentration for how long, and who verified it? Are venues on shared filtration closed together during the protocol? A well-run facility answers those questions the way Gaylord Pacific’s county file answers them — with dates, numbers, and an inspector’s verification. A facility that answers “we keep the chlorine right” has told you it does not know the organism it is chlorinating against, because for this organism the CDC’s own arithmetic says ordinary right chlorination is a 10.6-day clock.
If this happened to you
A diarrheal illness you connect to a pool, a splash pad, or a gym’s hot tub — especially as one of several cases — is a health-department report, not just a complaint to the operator: case counts are what trigger the investigations that produced both records above. File a report here as well, with dates, the venue, and any health-department case number, so the public record holds what the private one may not.