If Your Water Comes from Surface Sources Like Asheville's Public Supply
The City of Asheville in Buncombe County draws its water from surface sources. Surface water can be susceptible to algal toxins, known scientifically as cyanotoxins, which sometimes arise from algal blooms. These toxins include microcystins, cylindrospermopsin, and anatoxin-a, all monitored by federal surveys but without established maximum contaminant levels (MCLs) in drinking water. For the Asheville system, monitoring between 2018 and 2020 did not detect these algal toxins above their respective reporting thresholds, illustrating conditions in this wide municipal supply—not individual household water.
If You Have a Certified Laboratory Test for Algal Toxins
Testing your home's water for algal toxins is the only way to know your specific levels. Such tests typically report concentrations for microcystins, cylindrospermopsin, and anatoxin-a in micrograms per liter (µg/L), and compare them to health advisories established for short-term exposure. Understanding these results depends on recognizing that a non-detection means toxin levels are below the laboratory's reporting threshold, not necessarily zero. Knowing your home's values helps determine if advanced water treatment is necessary.
If You Compare Asheville’s Water Records with Neighboring Counties
When looking at Buncombe County’s water system record, keep in mind these figures reflect a large-scale municipal system, not private wells. Other nearby counties might have different sources or less comprehensive monitoring. Comparing these records should not lead to assumptions about household water quality but can indicate regional trends in algal toxin presence. Asheville’s water record shows no detections above reporting levels during the last federal survey, a useful baseline for comparison.
If You Use the C-Series Algal Toxins Filter at Your Tap
The documented C-Series System is designed specifically for residential removal of cyanotoxins like microcystins, cylindrospermopsin, and anatoxin-a. Once in place, treated water delivers reduced algal toxin levels, addressing concerns identified through testing or precautionary considerations. The system ships ready to configure with your household water line, providing a focused approach to managing algal toxins where they may be detected or suspected.
If You Operate a Commercial or Industrial Water System
Commercial or industrial users face distinct concerns including volume, regulatory compliance, and detailed monitoring. They may require additional or different treatment classes, and more frequent testing protocols. This page focuses on residential residential needs, which differ considerably from commercial assessments, including regulatory frameworks and water use scale.
If You Consider the Federal Range for Algal Toxins and What It Does Not Imply
The federal occurrence data indicate that Asheville’s public water system had no measured concentrations above reporting levels for the key algal toxins monitored. This absence of detection does not guarantee zero presence in all household taps. Moreover, there are no enforceable MCLs for these toxins; only EPA health advisories guide risk management. Thus, monitoring results are tools to inform treatment decisions, not definitive safety or risk verdicts.
In summary, your decision about household treatment for algal toxins in Asheville’s water supply should consider the municipal source type, your own certified water test results, and how local records compare with the region. The C-Series Algal Toxins Filter provides a targeted solution for residences seeking to reduce cyanotoxin levels once monitoring or testing indicates their presence or risk.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2019-11-18. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR4 monitoring (2018-2020) for City of Asheville (NC0111010), NC: 72 results across 3 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level