FDA Records Class I Recall of D'Dioses Limón Ice Pops Over Undeclared Milk, Nuts and Dyes
An FDA enforcement report dated July 22, 2026 lists 170 cases of the 4 oz lemon-lime paletas recalled across four Northeastern states, with the action ongoing.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22H-1169-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://www.fda.gov/food/food-allergensgluten-free-guidance-documents-regulatory-information/food-allergies
- https://en.wikipedia.org/wiki/Ice_pop
- https://en.wikipedia.org/wiki/Paleta
- https://www.wikidata.org/wiki/Q855373
- https://barrypopik.com/blog/paleta_mexican_popsicle
Revision history
- Version 67 Aug 2026, 15:20current
No new facts in this update; headline and dek added and reference-source URLs listed in citations.
- Version 57 Aug 2026, 13:14
Replaced the unsupported product paragraph (Paterson, N.J. producer and retail-distribution claims attributed to an FDA product notice) with the sourced background description of paleta-style ice pops, and added those reference URLs to sources.
- Version 47 Aug 2026, 07:30
Replaced the generic paleta description with the FDA product notice's own account of the line (Paterson, N.J. producer; retail grocery distribution) and dropped the unsourced water-ices regulatory aside.
- Version 37 Aug 2026, 03:46
Added source links for the FDA enforcement record, recall-class and allergen definitions and product reference material; gave the report date in full and corrected the product description to the registry-sourced paleta/water-ices wording.
- Version 26 Aug 2026, 23:29
Removed the unsourced claim tracing paletas to Tocumbo, Michoacán, and rewrote the product description to match the supplied reference material; added the reference URLs to sources.
- Version 16 Aug 2026, 17:41
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.