ASHTON, ID · Fremont County
ASHTON CITY OF Water System
Consumer Confidence Report status
ASHTON CITY OF must publish a Consumer Confidence Report — the annual drinking water quality report covering calendar year 2026 — by July 1, 2027.
As of August 1, 2026, EPA's federal records show no open violations for ASHTON CITY OF.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed August 1, 2026. This is a record-keeping and public-information tool — it does not replace Idaho’s official records. Always confirm current status with Idaho before making decisions based on this information.
System facts
- System ID (PWSID)
- ID7220004
- System type
- Community Water System
- Population served
- 1,129
- Service connections
- 516
- Ownership
- local government
- Water source
- groundwater (wells)
ASHTON CITY OF is one of 133 community water systems in Idaho in the 501 to 3,300 people size category, serving 1,129 people from groundwater.
As of August 1, 2026, its federal record holds 3 entries between 2010 and 2020, all of which EPA lists as closed. Nothing has been added since 2020.
Of the 3, 2 are monitoring and reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset — rather than findings about the water itself. The record involves the Total Coliform Rules, the Stage 1 Disinfectants and Disinfection Byproducts Rule, and inorganic chemicals.
Violation history
Monitoring, Routine (RTCR)
—Revised Total Coliform Rule
May 1, 2020 – May 31, 2020
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2020 – June 30, 2020
ResolvedMaximum Contaminant Level Violation, Average
Health-basedNitrate
October 1, 2010 – December 31, 2010
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| May 1, 2020 – May 31, 2020 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| April 1, 2020 – June 30, 2020 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2010 – December 31, 2010 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- May 30, 2025State Compliance achieved3 linked violations
- May 8, 2025State Public Notification requested2 linked violations
- December 4, 2024State Compliance achieved4 linked violations
- November 17, 2024State Public Notification requested4 linked violations
- February 17, 2023State Compliance achieved3 linked violations
- February 17, 2023State Compliance achieved2 linked violations
- July 13, 2020State Public Notification requested3 linked violations
- May 13, 2019State Public Notification requested4 linked violations
- February 13, 2019State Violation/Reminder Notice2 linked violations
- August 6, 2013State Compliance achieved5 linked violations
- May 3, 2013State Compliance achieved4 linked violations
- February 4, 2013State Public Notification requested4 linked violations
- February 1, 2013State Violation/Reminder Notice2 linked violations
- November 4, 2012State Public Notification requested1 linked violation
- November 1, 2012State Violation/Reminder Notice1 linked violation
- May 4, 2012State Bilateral Compliance Agreement signed3 linked violations
- May 4, 2012State Public Notification requested8 linked violations
- May 1, 2012State Violation/Reminder Notice1 linked violation
- April 5, 2012State Public Notification requested1 linked violation
- April 5, 2012State Public Notification requested1 linked violation
- April 5, 2012State Public Notification requested1 linked violation
- April 2, 2012State Violation/Reminder Notice1 linked violation
- April 2, 2012State Violation/Reminder Notice2 linked violations
- March 6, 2012State Bilateral Compliance Agreement signed6 linked violations
- February 4, 2012State Public Notification requested1 linked violation
- January 6, 2012State Public Notification requested2 linked violations
- November 4, 2011State Public Notification requested1 linked violation
- November 4, 2011State Public Notification requested1 linked violation
- November 1, 2011State Violation/Reminder Notice1 linked violation
- November 1, 2011State Violation/Reminder Notice1 linked violation
- October 6, 2011State Public Notification requested1 linked violation
- October 6, 2011State Public Notification requested1 linked violation
- October 6, 2011State Public Notification requested1 linked violation
- October 6, 2011State Public Notification requested1 linked violation
- October 6, 2011State Public Notification requested1 linked violation
- October 6, 2011State Public Notification requested1 linked violation
- October 4, 2011State Compliance achieved1 linked violation
- October 3, 2011State Violation/Reminder Notice1 linked violation
- October 3, 2011State Violation/Reminder Notice1 linked violation
- October 3, 2011State Violation/Reminder Notice1 linked violation
- October 3, 2011State Violation/Reminder Notice1 linked violation
- October 3, 2011State Violation/Reminder Notice2 linked violations
- October 3, 2011State Violation/Reminder Notice1 linked violation
- August 31, 2011State Bilateral Compliance Agreement signed2 linked violations
- August 10, 2011State Compliance achieved2 linked violations
- August 10, 2011State Bilateral Compliance Agreement signed2 linked violations
- August 4, 2011State Public Notification requested1 linked violation
- August 4, 2011State Public Notification requested1 linked violation
- August 1, 2011State Violation/Reminder Notice1 linked violation
- August 1, 2011State Violation/Reminder Notice1 linked violation
- July 4, 2011State Public Notification requested1 linked violation
- July 4, 2011State Public Notification requested1 linked violation
- July 4, 2011State Public Notification requested1 linked violation
- July 4, 2011State Public Notification requested1 linked violation
- July 4, 2011State Public Notification requested1 linked violation
- July 1, 2011State Violation/Reminder Notice1 linked violation
- July 1, 2011State Violation/Reminder Notice1 linked violation
- July 1, 2011State Violation/Reminder Notice1 linked violation
- July 1, 2011State Violation/Reminder Notice1 linked violation
- July 1, 2011State Violation/Reminder Notice1 linked violation
- July 1, 2011State Bilateral Compliance Agreement signed2 linked violations
- May 5, 2011State Public Notification requested1 linked violation
- May 3, 2011State Bilateral Compliance Agreement signed1 linked violation
- May 2, 2011State Violation/Reminder Notice1 linked violation
- April 4, 2011State Public Notification requested1 linked violation
- April 4, 2011State Public Notification requested1 linked violation
- April 4, 2011State Bilateral Compliance Agreement signed1 linked violation
- April 1, 2011State Violation/Reminder Notice1 linked violation
- April 1, 2011State Violation/Reminder Notice1 linked violation
- February 23, 2011State Bilateral Compliance Agreement signed10 linked violations
- February 4, 2011State Public Notification requested1 linked violation
- February 1, 2011State Violation/Reminder Notice1 linked violation
- January 7, 2011State Public Notification requested1 linked violation
- January 7, 2011State Public Notification requested1 linked violation
- January 7, 2011State Public Notification requested1 linked violation
- January 7, 2011State Public Notification requested2 linked violations
- January 4, 2011State Violation/Reminder Notice1 linked violation
- January 4, 2011State Violation/Reminder Notice1 linked violation
- January 4, 2011State Violation/Reminder Notice2 linked violations
- January 4, 2011State Public Notification requested5 linked violations
- January 4, 2011State Violation/Reminder Notice1 linked violation
- October 1, 2010State Violation/Reminder Notice2 linked violations
- September 1, 2010State Violation/Reminder Notice2 linked violations
- August 31, 2010State Bilateral Compliance Agreement signedgeneral compliance action — not tied to a specific violation on record
- February 4, 2010State Public Notification requested4 linked violations
- February 2, 2010State Bilateral Compliance Agreement signed14 linked violations
- July 6, 2009State Compliance achieved2 linked violations
Common questions
Is ASHTON CITY OF required to publish a Consumer Confidence Report?
- Yes. ASHTON CITY OF is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.
When is ASHTON CITY OF’s next Consumer Confidence Report due?
- ASHTON CITY OF’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does ASHTON CITY OF have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for ASHTON CITY OF.
What is a Consumer Confidence Report?
- A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.
Contact
STEGELMEIER, CATHY
208-652-3987
ASHTON, ID 83420