Pentair Perchlorate Filter

Buy Now

View full details

If your lab report shows 'not detected' or numerical perchlorate levels

When you receive a water quality report referencing perchlorate, the readings often include terms like 'not detected,' a median, or a range of values. These terms reflect results from measurements—'not detected' means perchlorate was below the reporting threshold used during testing. The median provides the middle value in a set of results, and the range indicates the lowest to highest measured perchlorate values found in tested samples.

For the Waterloo Water Works public water system in Black Hawk County, EPA sampling from 2001 to 2005 showed no perchlorate detected above the reporting level of 4.0 micrograms per liter (µg/L) in 18 samples. These measurements were part of a federal occurrence survey, which means they identify what the water system contained at those times, not individual household water quality.

If the perchlorate range you see compares to federal standards or guidelines

Currently, there is no enforceable federal maximum contaminant level (MCL) for perchlorate. The EPA’s sampling results show no perchlorate above the detection threshold, but this does not represent a safety violation or a guaranteed absence in your specific household water. It only reflects the public system's samples and does not imply any health risk or regulatory noncompliance.

Because perchlorate can affect the thyroid’s ability to use iodine, understanding whether perchlorate is present in your home's water and at what level requires a specific test of your water supply. The public system data is a helpful indication but not definitive for your water.

If your household is larger, seasonal, or a secondary residence

Households with higher water use or properties used seasonally or intermittently may experience different water quality dynamics than those in the EPA’s sampling. Water stagnation during unused periods or variation in supply sources can influence perchlorate concentrations. Testing your water, especially when occupancy or usage patterns change, is important to assess your perchlorate exposure accurately.

If perchlorate levels appear to vary over time in public water records

The Waterloo Water Works record between 2001 and 2005 shows consistent nondetection above 4.0 µg/L for perchlorate, demonstrating stability during that period. However, water quality can vary due to source water changes, environmental factors, and treatment adjustments. Continuous monitoring by the water system complements individual testing for a comprehensive understanding.

If you want to compare perchlorate presence here with a neighboring county

Comparing perchlorate data between Black Hawk County and neighboring counties requires understanding that sampling dates, laboratory methods, and reporting limits may differ. Variations in groundwater sources and local environmental factors also influence perchlorate levels. Using neighboring county data as a reference can be informative but should not replace direct testing of your well or connection.

What you should not assume from area perchlorate data alone

The public water system's perchlorate data is not a substitute for testing your specific water source. No perchlorate result listed here is a violation or a confirmation of safety for your household water. Only laboratory analysis of your home's water will establish the perchlorate concentration you actually receive. If perchlorate is detected at levels of concern or if you choose to reduce perchlorate exposure from your water, the Pentair Perchlorate Filter system ships ready to configure and addresses perchlorate reduction for residential use.

Where this information comes from

Source: EPA SDWIS public water system record. Sampled 2001-07-11. These figures describe the public water system's record, not the plumbing inside any individual building.

On record: EPA UCMR1 monitoring (2001-2005) for WATERLOO WATER WORKS (IA0790074), IA: 18 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level