Is SYCAMORE required to publish a Consumer Confidence Report?

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

SYCAMORE’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.

SYCAMORE, IL · DeKalb County

SYCAMORE Water System

Consumer Confidence Report status

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

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): IL0370550
System type: Community Water System
Population served: 18,500
Service connections: 6,918
Ownership: local government
Water source: groundwater (wells)

SYCAMORE is one of 225 community water systems in Illinois in the 10,001 to 100,000 people size category, serving 18,500 people from groundwater.

As of August 1, 2026, its federal record holds 37 entries between 1977 and 2024, all of which EPA lists as closed.

Of the 37, 7 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, the Public Notice Rule and Revised PN Rule, and the Stage 2 Disinfectants and Disinfection Byproducts Rule.

Violation history

Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2024 – November 1, 2024
Resolved
Monitoring and Reporting (DBP)
—
Total Haloacetic Acids (HAA5)
January 1, 2024 – December 31, 2024
Resolved
Monitoring and Reporting (DBP)
—
TTHM
January 1, 2024 – December 31, 2024
Resolved
Monitoring, Regular
—
Combined Radium (-226 and -228)
April 1, 2022 – June 30, 2022
Resolved
Monitoring, Regular
—
Combined Radium (-226 and -228)
October 1, 2021 – December 31, 2021
Resolved
Monitoring, Regular
—
Combined Radium (-226 and -228)
October 1, 2021 – December 31, 2021
Resolved
Monitoring, Regular
—
Combined Radium (-226 and -228)
October 1, 2021 – December 31, 2021
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2009 – March 31, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2008 – December 31, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2008 – September 30, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2008 – June 30, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2007 – September 30, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2007 – June 30, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2006 – December 31, 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
Combined Radium (-226 and -228)
January 1, 2006 – March 31, 2006
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
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
Public Notification Violation for NPDWR Violation
—
Public Notice
October 9, 2004 – November 24, 2004
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
Public Notification Violation for NPDWR Violation
—
Public Notice
January 9, 2004 – March 31, 2004
Resolved
Public Notification Violation without NPDWR Violation
—
Public Notice
January 9, 2004 – March 31, 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)
April 1, 2003 – June 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
Maximum Contaminant Level Violation, Average
Health-based
Barium
July 1, 1996 – September 30, 1996
Resolved
Monitoring, Regular
—
Gross Alpha, Excl. Radon and U
June 30, 1977 – June 29, 1981
Archived

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

Period	Violation	Contaminant / rule	Health-based	Status
July 1, 2024 – November 1, 2024	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved
January 1, 2024 – December 31, 2024	Monitoring and Reporting (DBP)	Total Haloacetic Acids (HAA5)	—	Resolved
January 1, 2024 – December 31, 2024	Monitoring and Reporting (DBP)	TTHM	—	Resolved
April 1, 2022 – June 30, 2022	Monitoring, Regular	Combined Radium (-226 and -228)	—	Resolved
October 1, 2021 – December 31, 2021	Monitoring, Regular	Combined Radium (-226 and -228)	—	Resolved
October 1, 2021 – December 31, 2021	Monitoring, Regular	Combined Radium (-226 and -228)	—	Resolved
October 1, 2021 – December 31, 2021	Monitoring, Regular	Combined Radium (-226 and -228)	—	Resolved
January 1, 2009 – March 31, 2009	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 1, 2008 – December 31, 2008	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 2008 – September 30, 2008	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 2008 – June 30, 2008	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 2008 – March 31, 2008	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	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
October 1, 2005 – December 31, 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	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
October 9, 2004 – November 24, 2004	Public Notification Violation for NPDWR Violation	Public Notice	—	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 9, 2004 – March 31, 2004	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
January 9, 2004 – March 31, 2004	Public Notification Violation without NPDWR Violation	Public Notice	—	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
July 1, 1996 – September 30, 1996	Maximum Contaminant Level Violation, Average	Barium	Health-based	Resolved
June 30, 1977 – June 29, 1981	Monitoring, Regular	Gross Alpha, Excl. Radon and U	—	Archived

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

Enforcement actions

September 25, 2025State Compliance achieved2 linked violations
June 9, 2025State Public Notification received2 linked violations
November 1, 2024State Compliance achieved1 linked violation
October 15, 2024State Public Notification requested2 linked violations
October 15, 2024State Violation/Reminder Notice2 linked violations
October 4, 2024State Violation/Reminder Notice1 linked violation
September 21, 2022State Compliance achieved1 linked violation
July 13, 2022State Violation/Reminder Notice1 linked violation
February 24, 2022State Compliance achieved2 linked violations
February 2, 2022State Compliance achieved1 linked violation
January 19, 2022State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
January 19, 2022State Violation/Reminder Notice1 linked violation
January 19, 2022State Violation/Reminder Notice1 linked violation
January 19, 2022State Violation/Reminder Notice1 linked violation
June 29, 2009State Public Notification received1 linked violation
May 1, 2009State Compliance achieved27 linked violations
April 21, 2009State Public Notification requested1 linked violation
April 21, 2009State Violation/Reminder Notice1 linked violation
March 30, 2009State Public Notification received1 linked violation
January 14, 2009State Public Notification requested1 linked violation
January 14, 2009State Violation/Reminder Notice1 linked violation
December 19, 2008State Public Notification received1 linked violation
October 17, 2008State Public Notification requested1 linked violation
October 17, 2008State Violation/Reminder Notice1 linked violation
September 25, 2008State Public Notification received1 linked violation
July 17, 2008State Public Notification requested1 linked violation
July 17, 2008State Violation/Reminder Notice1 linked violation
July 2, 2008State Public Notification received1 linked violation
June 24, 2008State Bilateral Compliance Agreement signed6 linked violations
April 16, 2008State Public Notification requested1 linked violation
April 16, 2008State Violation/Reminder Notice1 linked violation
April 3, 2008State Public Notification received1 linked violation
February 19, 2008State Formal Notice of Violation issued6 linked violations
January 17, 2008State Public Notification requested1 linked violation
January 17, 2008State Violation/Reminder Notice1 linked violation
January 2, 2008State Public Notification received1 linked violation
October 18, 2007State Public Notification requested1 linked violation
October 18, 2007State Violation/Reminder Notice1 linked violation
September 27, 2007State Public Notification received1 linked violation
July 18, 2007State Public Notification requested1 linked violation
July 18, 2007State Violation/Reminder Notice1 linked violation
June 27, 2007State Public Notification received1 linked violation
April 24, 2007State Public Notification requested1 linked violation
April 24, 2007State Violation/Reminder Notice1 linked violation
April 2, 2007State Public Notification received1 linked violation
January 17, 2007State Public Notification requested1 linked violation
January 17, 2007State Violation/Reminder Notice1 linked violation
December 28, 2006State Public Notification received1 linked violation
October 12, 2006State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
October 12, 2006State Violation/Reminder Notice1 linked violation
October 12, 2006State Violation/Reminder Notice1 linked violation
October 12, 2006State Public Notification requested1 linked violation
October 2, 2006State Public Notification received2 linked violations
September 8, 2006State Compliance achieved1 linked violation
July 24, 2006State Public Notification received1 linked violation
May 3, 2006State Public Notification received1 linked violation
April 11, 2006State Public Notification requested1 linked violation
April 11, 2006State Violation/Reminder Notice1 linked violation
February 8, 2006State Public Notification received1 linked violation
January 10, 2006State Public Notification requested1 linked violation
January 10, 2006State Violation/Reminder Notice1 linked violation
November 3, 2005State Public Notification received1 linked violation
July 8, 2005State Violation/Reminder Notice1 linked violation
May 2, 2005State Public Notification received1 linked violation
April 8, 2005State Violation/Reminder Notice1 linked violation
January 31, 2005State Public Notification received2 linked violations
January 7, 2005State Public Notification requested1 linked violation
December 14, 2004State Violation/Reminder Notice4 linked violations
December 3, 2004State Public Notification received3 linked violations
October 19, 2004State Public Notification requested1 linked violation
July 10, 2004State Public Notification requested1 linked violation
July 10, 2004State Violation/Reminder Notice1 linked violation
July 1, 2004State Public Notification received1 linked violation
April 10, 2004State Violation/Reminder Notice1 linked violation
April 10, 2004State Public Notification requested1 linked violation
April 5, 2004State Public Notification received1 linked violation
April 5, 2004State Public Notification received1 linked violation
March 31, 2004State Compliance achieved2 linked violations
March 31, 2004State Violation/Reminder Notice1 linked violation
March 17, 2004State Violation/Reminder Notice1 linked violation
February 27, 2004State Bilateral Compliance Agreement signed21 linked violations
January 10, 2004State Violation/Reminder Notice1 linked violation
December 19, 2003State Formal Notice of Violation issued21 linked violations
July 10, 2003State Public Notification requested1 linked violation
July 10, 2003State Violation/Reminder Notice4 linked violations
April 10, 2003State Public Notification requested4 linked violations
April 10, 2003State Violation/Reminder Notice1 linked violation
January 10, 2003State Violation/Reminder Notice1 linked violation
January 10, 2003State Public Notification requested1 linked violation
December 20, 2001State Bilateral Compliance Agreement signed2 linked violations
September 30, 1996State Compliance achieved3 linked violations
September 30, 1996State Compliance achieved1 linked violation
July 1, 1996State Public Notification requested1 linked violation
July 1, 1996State Violation/Reminder Notice1 linked violation
April 1, 1996State Violation/Reminder Notice1 linked violation
April 1, 1996State Public Notification requested1 linked violation
January 4, 1996State Public Notification received1 linked violation
January 1, 1996State Public Notification requested1 linked violation
January 1, 1996State Violation/Reminder Notice1 linked violation
December 3, 1988State Public Notification requested1 linked violation
October 11, 1988State Public Notification received11 linked violations

Common questions

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

KECK, JAKE

815-895-3545

SYCAMORE, IL 60178