Last updated: October 06, 2026 at 09:42 PM UTC
167 responses collected so far. This is a self-reported, crowdsourced tracker built to try to spot patterns in the current multistate cyclospora outbreak — not an official CDC or state health department investigation. There is no control group, so results below are proportional reporting among people who got sick, not proof of cause. Treat this as “worth watching,” not “confirmed.”
The form asks everyone why they believe they have cyclospora. 27 of 167 responses (16.2%) are lab confirmed. Another 124 (74.3%) are self-suspected — people who have the symptoms and think they have it, without a test.
Every number on this page is computed over all 167 responses, including the self-suspected ones. That is deliberate. Excluding them would discard most of the data and bias what remains toward whoever was able to get a stool test — which is a function of healthcare access, not of what someone ate. But it does mean the leads below describe a mostly self-diagnosed population, and that is a real limit on how far any of them should be pushed.
Free-text answers here are counted, never quoted — some mention unrelated medical conditions. “Unclassified” means an answer didn’t clearly fit any tier, not that it was discarded.
Sorted by signal ratio — how much more often cases report eating this compared to how often people eat it in an ordinary two-week period. A ratio above 1 means it’s showing up more than you’d expect from typical diets.
See Table 1 below for the full data, including confidence intervals.
This is a representation of the cases that have been self-reported in this survey. For the official case count, please refer to the CDC or your relevant state/local health department. See Table 2 below for the full state-by-state count.
See Table 3 below for the full province-by-province count.
See Table 4 below for the full date-by-date case counts.
This is a hand-compiled tally of food/restaurant mentions from Reddit threads, kept separate from the statistical analysis above since it doesn’t have the per-person structure needed for the confidence intervals or signal ratios. Read as “what’s been mentioned together,” not as a statistical finding.
See Table 5 below for the full mention tally (all restaurants/foods, not just the top 15 shown here).
CI columns are a 95% confidence interval — small sample sizes mean wide ranges. If the “Ratio CI low” column is still above 1, that’s a stronger lead than the point estimate alone.
The signal ratio divides how often cases report a food by a baseline — how commonly people eat it normally. That denominator drives every number in this table, so it’s worth being explicit about where it comes from.
Of the 27 foods below, 15 have a baseline sourced from USDA ERS and 12 rest on the author’s own estimate. Both are labeled in the “Baseline source” column.
baselines-external.json.The ERS column is shown but not yet used, and the reason is a real limitation rather than an oversight. ERS publishes pounds of food available per person per year; the baseline this ratio needs is the share of people who ate a food in a two-week window. Those measure different things and cannot be converted into one another — 19 lb of tomatoes a year could be everyone eating a little or a few people eating a lot. Substituting one for the other would change every ratio on this page for no reason but a change of units. Reconciling them properly is open work; until then both numbers are shown side by side so the gap is visible rather than hidden.
A signal ratio needs a denominator, so a food with no baseline can’t appear in the table above. That’s 34 of the 61 foods reported so far — not a rounding error, and previously they simply vanished from the page with nothing said. They are listed here instead.
Two different reasons a food is on this list, and they need different fixes:
lettuce_unspecified, onions, grapes, cherries, apples and
the like. These could be ranked; they just need a “how often
does a normal person eat this” number added to
category_vocabulary.json. Adding one moves the food
straight into the table above. lettuce_unspecified is the
largest by some way, and the most worth doing: it is lettuce whose
type the checklist recorded but whose form it didn’t,
so it is ordinary produce rather than an unrankable composite.tacos, sushi,
beef_burger or veggie_tray, and non-answers
like no_specific_item. There is no meaningful “percent of
people who ate a taco in a two-week window” to divide by, and inventing
one would manufacture a ranking rather than measure it. These stay here
permanently, which is the honest outcome, not a gap waiting to be
filled.lettuce_untyped is deliberately on this list too: it
held the obsolete flat baseline of 55 while its siblings divide by
10–20, which published a signal ratio of 0.04 for what is otherwise a
real lead. Removing the baseline was the fix.
Every food reported, whether or not it can be ranked. The last two columns show how each report arrived — a preset option someone ticked, or something they wrote in themselves.
A response can contribute to both columns — ticking “cilantro” on the checklist and also writing it in — so they can sum to more than the case count.
Cyclospora illness tends to run longer than most foodborne bugs (often weeks, sometimes relapsing). Short-duration reports are more likely something else.
How to read this page: a high signal ratio means the food is reported by sick people more than you’d expect from normal eating habits — that’s a lead worth watching, not a verdict. Small numbers (a food only 2-3 people mentioned) are noisy and easy to over-read. If something looks concerning and consistent, the right next step is reporting it to your local or state health department, who can do formal case-control interviews and trace product lots — this page can’t do that part.
Want to add your own report? Fill out the form here.
## category names 194 ok
## vocabulary integrity ok