Is BATAVIA required to publish a Consumer Confidence Report?

Yes. BATAVIA 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 BATAVIA’s next Consumer Confidence Report due?

BATAVIA’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

BATAVIA, IL · Kane County

BATAVIA Water System

Consumer Confidence Report status

BATAVIA 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 BATAVIA.

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): IL0894130
System type: Community Water System
Population served: 26,098
Service connections: 9,828
Ownership: local government
Water source: groundwater (wells)

BATAVIA is one of 225 community water systems in Illinois in the 10,001 to 100,000 people size category, serving 26,098 people from groundwater.

As of August 1, 2026, its federal record holds 30 entries between 1984 and 2025, all of which EPA lists as closed.

Of the 30, 4 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 Radionuclides and Revised Rad Rule, inorganic chemicals, and the Stage 1 Disinfectants and Disinfection Byproducts Rule.

Violation history

Monitoring, Regular
—
Nitrate
July 1, 2025 – September 30, 2025
Archived
Monitoring, Regular
—
Nitrite
July 1, 2025 – September 30, 2025
Archived
Monitoring and Reporting (DBP)
—
Chlorine
October 1, 2024 – October 31, 2024
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
October 1, 2024 – October 31, 2024
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
July 1, 2006 – September 30, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2006 – September 30, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2006 – June 30, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
April 1, 2006 – June 30, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2006 – January 10, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
January 1, 2006 – January 30, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
October 1, 2005 – December 31, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2005 – December 31, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
July 1, 2005 – September 30, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2005 – June 30, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
January 1, 2005 – March 31, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2004 – December 31, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2004 – September 30, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2003 – December 31, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2003 – September 30, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2003 – March 31, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2002 – December 31, 2002
Resolved
WQP Entry Point/Tap Treatment Technique Non-Compliance
Health-based
Lead and Copper Rule
April 1, 2001 – June 30, 2001
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2000 – September 30, 2002
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 1992 – December 31, 1995
Archived
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
February 1, 1988 – December 31, 1991
Archived
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
June 18, 1987 – June 17, 1991
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 25, 1984 – January 24, 1988
Archived

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
July 1, 2025 – September 30, 2025	Monitoring, Regular	Nitrate	—	Archived
July 1, 2025 – September 30, 2025	Monitoring, Regular	Nitrite	—	Archived
October 1, 2024 – October 31, 2024	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
October 1, 2024 – October 31, 2024	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
July 1, 2006 – September 30, 2006	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	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
April 1, 2006 – June 30, 2006	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
January 1, 2006 – January 10, 2006	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 2006 – January 30, 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
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
October 1, 2004 – December 31, 2004	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	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
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
April 1, 2001 – June 30, 2001	WQP Entry Point/Tap Treatment Technique Non-Compliance	Lead and Copper Rule	Health-based	Resolved
January 1, 2000 – September 30, 2002	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 1992 – December 31, 1995	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Archived
February 1, 1988 – December 31, 1991	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Archived
June 18, 1987 – June 17, 1991	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
January 25, 1984 – January 24, 1988	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Archived

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Enforcement actions

October 15, 2025State Public Notification requested1 linked violation
October 15, 2025State Violation/Reminder Notice1 linked violation
October 15, 2025State Violation/Reminder Notice1 linked violation
October 15, 2025State Public Notification requested1 linked violation
October 15, 2025State Violation/Reminder Notice1 linked violation
October 15, 2025State Public Notification requested1 linked violation
October 15, 2025State Violation/Reminder Notice1 linked violation
October 15, 2025State Public Notification requested1 linked violation
July 3, 2025State Public Notification received1 linked violation
July 3, 2025State Public Notification received1 linked violation
November 27, 2024State Public Notification requested1 linked violation
November 27, 2024State Violation/Reminder Notice1 linked violation
November 27, 2024State Public Notification requested1 linked violation
November 27, 2024State Violation/Reminder Notice1 linked violation
November 25, 2024State Compliance achieved1 linked violation
November 25, 2024State Compliance achieved1 linked violation
October 13, 2006State Violation/Reminder Notice1 linked violation
October 13, 2006State Public Notification requested1 linked violation
October 12, 2006State Violation/Reminder Notice1 linked violation
October 12, 2006State Public Notification requested1 linked violation
September 30, 2006State Compliance achieved4 linked violations
September 11, 2006State Public Notification received2 linked violations
July 31, 2006State Public Notification received2 linked violations
July 28, 2006State Violation/Reminder Notice1 linked violation
July 28, 2006State Public Notification requested2 linked violations
July 10, 2006State Violation/Reminder Notice1 linked violation
June 8, 2006State Public Notification received1 linked violation
May 30, 2006State Public Notification received1 linked violation
May 11, 2006State Public Notification requested2 linked violations
May 11, 2006State Violation/Reminder Notice2 linked violations
April 11, 2006State Violation/Reminder Notice1 linked violation
April 11, 2006State Public Notification requested1 linked violation
March 15, 2006State Public Notification received1 linked violation
January 30, 2006State Compliance achieved6 linked violations
January 10, 2006State Public Notification requested1 linked violation
January 10, 2006State Violation/Reminder Notice1 linked violation
January 10, 2006State Compliance achieved16 linked violations
December 19, 2005State Public Notification received1 linked violation
October 7, 2005State Public Notification requested2 linked violations
October 7, 2005State Violation/Reminder Notice2 linked violations
September 14, 2005State Public Notification received1 linked violation
July 8, 2005State Public Notification requested2 linked violations
July 8, 2005State Violation/Reminder Notice2 linked violations
June 6, 2005State Public Notification received2 linked violations
April 8, 2005State Public Notification requested2 linked violations
April 8, 2005State Violation/Reminder Notice2 linked violations
March 25, 2005State Public Notification received1 linked violation
January 7, 2005State Public Notification requested1 linked violation
October 19, 2004State Violation/Reminder Notice2 linked violations
September 15, 2004State Public Notification received1 linked violation
September 15, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 10, 2004State Public Notification requested1 linked violation
July 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
July 10, 2004State Violation/Reminder Notice1 linked violation
June 4, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
April 15, 2004State Bilateral Compliance Agreement signed34 linked violations
April 10, 2004State Public Notification requested2 linked violations
March 11, 2004State Public Notification received1 linked violation
March 11, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
March 1, 2004State Public Notification received1 linked violation
March 1, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
December 19, 2003State Formal Notice of Violation issued30 linked violations
December 15, 2003State Public Notification received1 linked violation
December 15, 2003State Public Notification received1 linked violation
July 10, 2003State Violation/Reminder Notice2 linked violations
July 10, 2003State Public Notification requested2 linked violations
June 2, 2003State Public Notification received3 linked violations
April 10, 2003State Public Notification requested1 linked violation
April 10, 2003State Violation/Reminder Notice1 linked violation
March 3, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
March 3, 2003State Public Notification received1 linked violation
January 10, 2003State Public Notification requested1 linked violation
January 10, 2003State Violation/Reminder Notice1 linked violation
December 12, 2002State Bilateral Compliance Agreement signed9 linked violations
July 1, 2001State Compliance achieved6 linked violations
June 15, 1999State Public Notification requested1 linked violation
June 15, 1999State Violation/Reminder Notice1 linked violation
June 1, 1998State Public Notification received1 linked violation
March 1, 1998State Public Notification received1 linked violation
September 1, 1997State Public Notification received1 linked violation
June 5, 1997State Public Notification received1 linked violation
March 1, 1997State Public Notification received1 linked violation
December 1, 1996State Public Notification received1 linked violation
September 1, 1996State Public Notification received1 linked violation
June 1, 1996State Public Notification received1 linked violation
March 8, 1996State Public Notification received1 linked violation
December 1, 1995State Public Notification received1 linked violation
September 1, 1995State Public Notification received1 linked violation
June 1, 1995State Public Notification received1 linked violation
May 5, 1995State Public Notification received1 linked violation
April 28, 1995State Public Notification received1 linked violation
March 9, 1995State Public Notification received1 linked violation
October 1, 1994State Public Notification received1 linked violation
June 30, 1994State Public Notification received1 linked violation
October 1, 1993State Public Notification received1 linked violation
July 1, 1993State Public Notification received1 linked violation
June 29, 1993State Compliance achieved2 linked violations
March 1, 1993State Public Notification received2 linked violations
December 5, 1992State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
November 1, 1992State Public Notification received2 linked violations
June 4, 1992State Public Notification received2 linked violations
May 7, 1992State Public Notification requested2 linked violations
January 15, 1992State Public Notification received2 linked violations
October 1, 1991State Public Notification received3 linked violations
August 20, 1991State Public Notification requested3 linked violations
April 17, 1991State Public Notification received5 linked violations
March 7, 1991State Public Notification received3 linked violations
January 11, 1991State Public Notification received3 linked violations
October 10, 1990State Public Notification received4 linked violations
August 9, 1990State Administrative/Compliance Order without penalty issued2 linked violations
August 4, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
August 4, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
June 27, 1990State Public Notification received3 linked violations
April 5, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
March 28, 1990State Public Notification received3 linked violations
January 15, 1990State Public Notification received3 linked violations
October 4, 1989State Public Notification received3 linked violations

Common questions

Is BATAVIA required to publish a Consumer Confidence Report?: Yes. BATAVIA 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 BATAVIA’s next Consumer Confidence Report due?: BATAVIA’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BATAVIA have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for BATAVIA.
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

BARKEI, JEREMY P.

630-454-2452

BATAVIA, IL 60510