Is CORTLAND required to publish a Consumer Confidence Report?

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

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

CORTLAND, IL · DeKalb County

CORTLAND Water System

Consumer Confidence Report status

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

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): IL0370051
System type: Community Water System
Population served: 4,398
Service connections: 1,529
Ownership: local government
Water source: groundwater (wells)

CORTLAND is one of 248 community water systems in Illinois in the 3,301 to 10,000 people size category, serving 4,398 people from groundwater.

As of August 1, 2026, its federal record holds 29 entries between 1990 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.

Of the 29, 5 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 Consumer Confidence Rule, and the Public Notice Rule and Revised PN Rule.

Violation history

Consumer Confidence Report Inadequate Reporting
—
Consumer Confidence Rule
July 1, 2023 – May 22, 2024
Resolved
Monitoring, Regular
—
Combined Uranium
April 1, 2017 – June 30, 2017
Resolved
Monitoring, Regular
—
Combined Radium (-226 and -228)
October 1, 2008 – December 31, 2008
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)
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
Combined Radium (-226 and -228)
October 1, 2004 – December 31, 2004
Resolved
Monitoring, Regular
—
Combined Radium (-226 and -228)
July 1, 2004 – September 30, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2004 – September 30, 2004
Resolved
Monitoring, Regular
—
Gross Alpha, Excl. Radon and U
July 1, 2004 – September 30, 2004
Resolved
Monitoring, Regular
—
Combined Uranium
July 1, 2004 – September 30, 2004
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
June 1, 2004 – June 30, 2004
Archived
Public Notification Violation without NPDWR Violation
—
Public Notice
April 10, 2004 – June 21, 2004
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
April 10, 2004 – June 21, 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
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2003 – July 21, 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)
October 1, 2002 – December 31, 2002
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 22, 1993 – April 21, 1997
Archived
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 5, 1990 – May 19, 1992
Resolved

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, 2023 – May 22, 2024	Consumer Confidence Report Inadequate Reporting	Consumer Confidence Rule	—	Resolved
April 1, 2017 – June 30, 2017	Monitoring, Regular	Combined Uranium	—	Resolved
October 1, 2008 – December 31, 2008	Monitoring, Regular	Combined Radium (-226 and -228)	—	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
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	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 1, 2004 – December 31, 2004	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 2004 – September 30, 2004	Monitoring, Regular	Combined Radium (-226 and -228)	—	Resolved
July 1, 2004 – September 30, 2004	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 2004 – September 30, 2004	Monitoring, Regular	Gross Alpha, Excl. Radon and U	—	Resolved
July 1, 2004 – September 30, 2004	Monitoring, Regular	Combined Uranium	—	Resolved
June 1, 2004 – June 30, 2004	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Archived
April 10, 2004 – June 21, 2004	Public Notification Violation without NPDWR Violation	Public Notice	—	Resolved
April 10, 2004 – June 21, 2004	Public Notification Violation for NPDWR Violation	Public Notice	—	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
July 1, 2003 – July 21, 2003	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved
April 1, 2003 – June 30, 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 22, 1993 – April 21, 1997	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Archived
January 5, 1990 – May 19, 1992	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved

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

Enforcement actions

January 27, 2026State Compliance achievedgeneral compliance action — not tied to a specific violation on record
January 27, 2026State Compliance achievedgeneral compliance action — not tied to a specific violation on record
January 14, 2026State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
January 14, 2026State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
May 22, 2024State Compliance achieved1 linked violation
December 1, 2023State Violation/Reminder Notice1 linked violation
July 21, 2017State Compliance achieved1 linked violation
July 12, 2017State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
July 12, 2017State Violation/Reminder Notice1 linked violation
January 15, 2009State Compliance achieved1 linked violation
January 14, 2009State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
January 14, 2009State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
January 14, 2009State Violation/Reminder Notice1 linked violation
January 14, 2009State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
May 3, 2007State Public Notification received1 linked violation
April 24, 2007State Public Notification requested1 linked violation
April 24, 2007State Violation/Reminder Notice1 linked violation
April 10, 2007State Compliance achieved19 linked violations
January 17, 2007State Public Notification requested1 linked violation
January 17, 2007State Violation/Reminder Notice1 linked violation
January 4, 2007State Public Notification received1 linked violation
October 12, 2006State Violation/Reminder Notice1 linked violation
October 12, 2006State Public Notification requested1 linked violation
September 5, 2006State Public Notification received1 linked violation
July 17, 2006State Public Notification received1 linked violation
July 10, 2006State Public Notification requested1 linked violation
July 10, 2006State Violation/Reminder Notice1 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
January 18, 2006State Public Notification received1 linked violation
January 10, 2006State Public Notification requested1 linked violation
January 10, 2006State Violation/Reminder Notice1 linked violation
December 23, 2005State Public Notification received3 linked violations
November 10, 2005State Public Notification received1 linked violation
October 7, 2005State Violation/Reminder Notice1 linked violation
October 7, 2005State Public Notification requested1 linked violation
July 21, 2005State Public Notification received1 linked violation
July 8, 2005State Violation/Reminder Notice1 linked violation
July 8, 2005State Public Notification requested1 linked violation
May 12, 2005State Public Notification received1 linked violation
April 8, 2005State Violation/Reminder Notice1 linked violation
April 8, 2005State Public Notification requested1 linked violation
February 7, 2005State Public Notification received1 linked violation
January 7, 2005State Violation/Reminder Notice1 linked violation
January 7, 2005State Public Notification requested1 linked violation
December 3, 2004State Public Notification received1 linked violation
November 18, 2004State Public Notification requested3 linked violations
November 18, 2004State Violation/Reminder Notice3 linked violations
November 5, 2004State Compliance achieved3 linked violations
October 19, 2004State Public Notification requested1 linked violation
October 19, 2004State Violation/Reminder Notice1 linked violation
October 15, 2004State Public Notification received1 linked violation
August 24, 2004State Violation/Reminder Notice2 linked violations
August 24, 2004State Public Notification requested2 linked violations
July 10, 2004State Public Notification requested2 linked violations
July 10, 2004State Violation/Reminder Notice2 linked violations
July 6, 2004State Public Notification received2 linked violations
June 21, 2004State Compliance achieved2 linked violations
June 11, 2004State Violation/Reminder Notice3 linked violations
April 10, 2004State Violation/Reminder Notice2 linked violations
January 16, 2004State Formal Notice of Violation issued21 linked violations
January 10, 2004State Public Notification requested1 linked violation
January 10, 2004State Violation/Reminder Notice1 linked violation
December 1, 2003State Public Notification received2 linked violations
September 19, 2003State Public Notification received1 linked violation
July 21, 2003State Compliance achieved1 linked violation
July 10, 2003State Violation/Reminder Notice2 linked violations
July 10, 2003State Public Notification requested1 linked violation
April 10, 2003State Violation/Reminder Notice1 linked violation
April 4, 2003State Public Notification received1 linked violation
February 12, 2003State Compliance achieved1 linked violation
January 10, 2003State Public Notification requested1 linked violation
January 10, 2003State Violation/Reminder Notice1 linked violation
November 8, 2002State Bilateral Compliance Agreement signed6 linked violations
October 17, 2002State Formal Notice of Violation issued6 linked violations
February 1, 1998State Public Notification received1 linked violation
October 1, 1997State Public Notification received1 linked violation
June 1, 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
March 1, 1996State Public Notification received1 linked violation
December 8, 1995State Public Notification received1 linked violation
December 1, 1995State Public Notification received1 linked violation
September 11, 1995State Public Notification received1 linked violation
September 1, 1995State Public Notification received1 linked violation
June 1, 1995State Public Notification received1 linked violation
March 1, 1995State Public Notification received1 linked violation
December 1, 1994State Public Notification received1 linked violation
December 1, 1993State Public Notification received1 linked violation
June 1, 1993State Public Notification received1 linked violation
May 19, 1992State Compliance achieved1 linked violation
March 1, 1992State Public Notification received1 linked violation
December 1, 1991State Public Notification received1 linked violation

Common questions

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

SUMMERHILL, JOEL S.

815-756-9684

CORTLAND, IL 60112-0519