CHANNAHON, IL · Will County
CHANNAHON EAST Water System
Consumer Confidence Report status
CHANNAHON EAST 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 CHANNAHON EAST.
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 Illinois’s official records. Always confirm current status with Illinois before making decisions based on this information.
System facts
- System ID (PWSID)
- IL1970070
- System type
- Community Water System
- Population served
- 630
- Service connections
- 306
- Ownership
- local government
- Water source
- groundwater (wells)
CHANNAHON EAST is one of 773 community water systems in Illinois in the 501 to 3,300 people size category, serving 630 people from groundwater.
As of August 1, 2026, its federal record holds 29 entries between 1996 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
None of the 29 are monitoring or reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset; these involve water-quality, treatment, or public-notice findings instead. The record involves the Radionuclides and Revised Rad Rule and the Consumer Confidence Rule.
Violation history
Consumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2023 – January 4, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2007 – September 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2007 – June 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2006 – September 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2006 – June 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2006 – March 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2006 – February 14, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
October 1, 2005 – December 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2005 – December 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2005 – June 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2005 – June 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2005 – March 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2004 – September 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2003 – December 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2003 – September 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2003 – June 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2003 – March 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2002 – December 31, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2000 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
October 1, 1998 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
September 17, 1996 – September 16, 2000
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2023 – January 4, 2024 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
| October 1, 2007 – December 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2007 – September 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2007 – June 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2007 – March 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2006 – September 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2006 – June 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2006 – March 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2006 – February 14, 2006 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2005 – December 31, 2005 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2005 – December 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2005 – June 30, 2005 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| April 1, 2005 – June 30, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2005 – March 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2005 – March 31, 2005 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2004 – September 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2003 – December 31, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2003 – September 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2003 – June 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2003 – March 31, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2002 – December 31, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2000 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 1998 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| September 17, 1996 – September 16, 2000 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- January 4, 2024State Compliance achieved2 linked violations
- January 17, 2008State Violation/Reminder Notice2 linked violations
- December 31, 2007State Compliance achieved24 linked violations
- October 26, 2007State Public Notification requested1 linked violation
- August 15, 2007State Public Notification received2 linked violations
- August 3, 2007State Violation/Reminder Notice2 linked violations
- April 24, 2007State Violation/Reminder Notice2 linked violations
- February 8, 2007State Public Notification received2 linked violations
- January 24, 2007State Violation/Reminder Notice1 linked violation
- January 24, 2007State Public Notification requested1 linked violation
- November 2, 2006State Public Notification received1 linked violation
- October 17, 2006State Violation/Reminder Notice1 linked violation
- October 17, 2006State Public Notification requested1 linked violation
- July 27, 2006State Public Notification received3 linked violations
- April 11, 2006State Public Notification requested1 linked violation
- April 11, 2006State Violation/Reminder Notice2 linked violations
- January 10, 2006State Public Notification requested1 linked violation
- January 10, 2006State Violation/Reminder Notice1 linked violation
- November 14, 2005State Public Notification received3 linked violations
- October 7, 2005State Violation/Reminder Notice1 linked violation
- July 13, 2005State Public Notification received2 linked violations
- July 8, 2005State Public Notification requested1 linked violation
- July 8, 2005State Public Notification requested1 linked violation
- July 8, 2005State Violation/Reminder Notice1 linked violation
- April 8, 2005State Public Notification requested2 linked violations
- January 7, 2005State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 7, 2005State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 7, 2005State Public Notification requested1 linked violation
- November 15, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- November 15, 2004State Public Notification received1 linked violation
- October 19, 2004State Violation/Reminder Notice1 linked violation
- October 19, 2004State Public Notification requested12 linked violations
- August 23, 2004State Public Notification received2 linked violations
- August 23, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- August 23, 2004State Public Notification received1 linked violation
- August 2, 2004State Bilateral Compliance Agreement signed21 linked violations
- July 10, 2004State Violation/Reminder Notice1 linked violation
- April 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 10, 2004State Public Notification requested1 linked violation
- April 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- April 10, 2004State Violation/Reminder Notice1 linked violation
- February 19, 2004State Public Notification received1 linked violation
- February 19, 2004State Public Notification received1 linked violation
- January 10, 2004State Violation/Reminder Notice1 linked violation
- January 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 10, 2004State Public Notification requested1 linked violation
- December 17, 2003State Intentional no-action28 linked violations
- November 17, 2003State Public Notification received1 linked violation
- November 17, 2003State Public Notification received1 linked violation
- November 17, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- August 15, 2003State Public Notification received2 linked violations
- June 17, 2003State Public Notification received2 linked violations
- April 10, 2003State Public Notification requested3 linked violations
- March 17, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 17, 2003State Public Notification received1 linked violation
- January 10, 2003State Violation/Reminder Notice2 linked violations
- January 10, 2003State Public Notification requested2 linked violations
- January 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- June 29, 1998State Public Notification received1 linked violation
- May 12, 1997State Public Notification received1 linked violation
- January 10, 1997State Public Notification received1 linked violation
- October 14, 1996State Public Notification received1 linked violation
- September 30, 1996State Public Notification received1 linked violation
- March 18, 1993State Public Notification requested1 linked violation
- March 18, 1993State Violation/Reminder Notice1 linked violation
- January 23, 1993State Public Notification received1 linked violation
- December 19, 1992State Violation/Reminder Notice2 linked violations
- December 19, 1992State Public Notification requested2 linked violations
- July 18, 1992State Violation/Reminder Notice1 linked violation
Common questions
Is CHANNAHON EAST required to publish a Consumer Confidence Report?
- Yes. CHANNAHON EAST 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 CHANNAHON EAST’s next Consumer Confidence Report due?
- CHANNAHON EAST’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CHANNAHON EAST have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CHANNAHON EAST.
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
DOLEZAL, EDWARD S.
815-467-6644
CHANNAHON, IL 60410