Autotrol 1,4-Dioxane Filter

Buy Now

View full details

Understanding What Public Water Data Can and Cannot Tell You

Data from the City of Bismarck's public water system in Burleigh County provides a snapshot of water quality for over 72,000 residents. Government sampling between 2013 and 2015 found no detections of 1,4-dioxane above 0.07 micrograms per liter (µg/L), equivalent to 0.07 parts per billion (ppb). However, these figures represent system-wide measurements and do not reflect individual household water characteristics. To determine your home's exact level of the cyclic ether commonly known as the solvent stabiliser, a specific water test is necessary.

Why 1,4-Dioxane Advances Beyond the Solvent Plume It Stabilised

Unlike many other pollutants, 1,4-dioxane moves ahead of the primary solvent contamination plume because of its high mobility in groundwater and surface water. This means the solvent stabiliser can travel further and faster in the water supply, potentially reaching household taps even when the main solvent source appears distant. Understanding this behavior is critical for assessing potential exposure risks beyond the immediate vicinity of contamination.

Why Carbon Filters and Boiling Are Ineffective Against This Cyclic Ether

Traditional treatments like activated carbon filtration and boiling water have limited impact on the solvent stabiliser. 1,4-dioxane's chemical structure resists adsorption on carbon media, and boiling does not significantly reduce its concentration. Instead, documented technologies capable of addressing this compound focus on specialized filtration methods designed to target its unique properties.

Interpreting the Public Record’s Median and Range for Homeowners

The absence of 1,4-dioxane detections above 0.07 µg/L in Bismarck’s public system suggests very low concentrations at the community level. The EPA’s cancer risk reference concentration for 1,4-dioxane is 0.35 µg/L, which provides a benchmark for evaluating potential long-term health concerns. Still, this does not guarantee zero presence at any tap. Homeowners should consider these figures as background data and seek individual water testing to clarify their specific situation before choosing treatment options.

The Impact of Plumbing Materials and Age Separate from Source Water Quality

Water quality at the tap can be influenced by plumbing materials and the age of the household system, distinct from the original source water quality. Older pipes or certain materials might cause chemical interactions or leaching unrelated to the solvent stabiliser itself. These factors warrant inspection alongside source water testing to understand all potential contributors to water chemistry at home.

What to Record Before Seeking Treatment Guidance

Before requesting expert advice, note the following details:

• Results of any recent water testing for 1,4-dioxane or related contaminants
• Age and materials of your plumbing system
• Local water source type (public surface water is the supply in Bismarck)
• Any noticeable water quality issues, such as taste or odor changes

This information helps clarify treatment needs and identify appropriate solutions.

Considering Treatment: The Autotrol 1,4-Dioxane Filter

For households in Burleigh County assessing options to address the solvent stabiliser, the Autotrol 1,4-Dioxane Filter ships ready to configure for direct purchase. It is a documented technology specifically designed to target and reduce 1,4-dioxane concentrations in residential water. Utilizing this system aligns treatment capability with measured demand figures obtained through your testing, helping ensure an effective household water solution for this persistent cyclic ether.

Where this information comes from

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

On record: EPA UCMR3 monitoring (2013-2015) for City of Bismarck (ND0800080), ND: 4 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level