Is ROCKFORD required to publish a Consumer Confidence Report?

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

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

ROCKFORD, IL · Winnebago County

ROCKFORD Water System

Consumer Confidence Report status

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

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): IL2010300
System type: Community Water System
Population served: 147,051
Service connections: 51,060
Ownership: local government
Water source: groundwater (wells)

ROCKFORD is among the 6 largest community water systems in Illinois, serving 147,051 people from groundwater.

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

Of the 39, 13 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, synthetic organic chemicals, and inorganic chemicals.

Violation history

Monitoring and Reporting (DBP)
—
Total Haloacetic Acids (HAA5)
October 1, 2024 – December 31, 2024
Resolved
Monitoring, Regular
—
2,4-D
January 1, 2023 – December 31, 2025
Archived
Monitoring, Regular
—
Chlordane
January 1, 2023 – December 31, 2025
Archived
Monitoring, Regular
—
Chlordane
January 1, 2023 – December 31, 2025
Archived
Monitoring, Regular
—
Dinoseb
January 1, 2023 – December 31, 2025
Archived
Monitoring, Regular
—
Dalapon
January 1, 2023 – December 31, 2025
Archived
Monitoring, Regular
—
2,4,5-TP
January 1, 2023 – December 31, 2025
Archived
Monitoring, Regular
—
Pentachlorophenol
January 1, 2023 – December 31, 2025
Archived
Monitoring, Regular
—
cis-1,2-Dichloroethylene
January 1, 2023 – December 31, 2023
Resolved
Monitoring, Regular
—
Nitrate
January 1, 2022 – December 31, 2022
Resolved
Monitoring, Regular
—
Nitrite
January 1, 2020 – December 31, 2022
Resolved
Monitoring, Regular
—
Nitrite
January 1, 2020 – December 31, 2022
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2012 – January 6, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2011 – December 31, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2011 – September 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2011 – June 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2011 – March 31, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2010 – December 31, 2010
Resolved
Consumer Confidence Report Inadequate Reporting
—
Consumer Confidence Rule
July 1, 2010 – June 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2010 – September 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2010 – June 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2010 – March 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2009 – December 31, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2009 – September 30, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2009 – June 30, 2009
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)
October 1, 2006 – December 31, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
April 1, 2006 – April 9, 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
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
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
—
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
October 1, 2024 – December 31, 2024	Monitoring and Reporting (DBP)	Total Haloacetic Acids (HAA5)	—	Resolved
January 1, 2023 – December 31, 2025	Monitoring, Regular	2,4-D	—	Archived
January 1, 2023 – December 31, 2025	Monitoring, Regular	Chlordane	—	Archived
January 1, 2023 – December 31, 2025	Monitoring, Regular	Chlordane	—	Archived
January 1, 2023 – December 31, 2025	Monitoring, Regular	Dinoseb	—	Archived
January 1, 2023 – December 31, 2025	Monitoring, Regular	Dalapon	—	Archived
January 1, 2023 – December 31, 2025	Monitoring, Regular	2,4,5-TP	—	Archived
January 1, 2023 – December 31, 2025	Monitoring, Regular	Pentachlorophenol	—	Archived
January 1, 2023 – December 31, 2023	Monitoring, Regular	cis-1,2-Dichloroethylene	—	Resolved
January 1, 2022 – December 31, 2022	Monitoring, Regular	Nitrate	—	Resolved
January 1, 2020 – December 31, 2022	Monitoring, Regular	Nitrite	—	Resolved
January 1, 2020 – December 31, 2022	Monitoring, Regular	Nitrite	—	Resolved
January 1, 2012 – January 6, 2012	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 1, 2011 – December 31, 2011	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 2011 – September 30, 2011	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 2011 – June 30, 2011	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 2011 – March 31, 2011	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 1, 2010 – December 31, 2010	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 2010 – June 30, 2011	Consumer Confidence Report Inadequate Reporting	Consumer Confidence Rule	—	Resolved
July 1, 2010 – September 30, 2010	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 2010 – June 30, 2010	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 2010 – March 31, 2010	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 1, 2009 – December 31, 2009	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 2009 – September 30, 2009	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 2009 – June 30, 2009	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	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
October 1, 2006 – December 31, 2006	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 2006 – April 9, 2006	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	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	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	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
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

February 11, 2026State Compliance achievedgeneral compliance action — not tied to a specific violation on record
January 16, 2026State Public Notification requested1 linked violation
January 16, 2026State Violation/Reminder Notice1 linked violation
January 16, 2026State Public Notification requested1 linked violation
January 16, 2026State Violation/Reminder Notice1 linked violation
January 16, 2026State Public Notification requested1 linked violation
January 16, 2026State Violation/Reminder Notice1 linked violation
January 16, 2026State Public Notification requested1 linked violation
January 16, 2026State Violation/Reminder Notice1 linked violation
January 16, 2026State Public Notification requested1 linked violation
January 16, 2026State Violation/Reminder Notice1 linked violation
January 16, 2026State Public Notification requested1 linked violation
January 16, 2026State Violation/Reminder Notice1 linked violation
January 16, 2026State Violation/Reminder Notice1 linked violation
January 16, 2026State Public Notification requested1 linked violation
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
July 10, 2025State Public Notification received1 linked violation
January 22, 2025State Compliance achieved1 linked violation
January 14, 2025State Public Notification requested1 linked violation
January 14, 2025State Violation/Reminder Notice1 linked violation
July 1, 2024State Public Notification received1 linked violation
March 19, 2024State Compliance achieved1 linked violation
January 11, 2024State Public Notification requested1 linked violation
January 11, 2024State Violation/Reminder Notice1 linked violation
July 5, 2023State Public Notification received1 linked violation
July 5, 2023State Public Notification received1 linked violation
July 5, 2023State Public Notification received1 linked violation
April 3, 2023State Compliance achieved3 linked violations
February 10, 2023State Public Notification requested1 linked violation
February 10, 2023State Public Notification requested1 linked violation
February 10, 2023State Violation/Reminder Notice1 linked violation
February 10, 2023State Violation/Reminder Notice1 linked violation
February 10, 2023State Public Notification requested1 linked violation
February 10, 2023State Violation/Reminder Notice1 linked violation
May 7, 2012State Public Notification received1 linked violation
April 12, 2012State Violation/Reminder Notice1 linked violation
April 12, 2012State Public Notification requested1 linked violation
February 9, 2012State Public Notification received1 linked violation
January 17, 2012State Violation/Reminder Notice1 linked violation
January 17, 2012State Public Notification requested1 linked violation
January 6, 2012State Compliance achieved30 linked violations
November 10, 2011State Public Notification received1 linked violation
October 27, 2011State Violation/Reminder Notice1 linked violation
October 27, 2011State Public Notification requested1 linked violation
August 3, 2011State Public Notification received1 linked violation
July 20, 2011State Violation/Reminder Notice1 linked violation
July 20, 2011State Public Notification requested1 linked violation
June 30, 2011State Compliance achieved1 linked violation
May 4, 2011State Public Notification received1 linked violation
April 19, 2011State Violation/Reminder Notice1 linked violation
April 19, 2011State Public Notification requested1 linked violation
February 4, 2011State Public Notification received1 linked violation
January 21, 2011State Violation/Reminder Notice1 linked violation
January 21, 2011State Public Notification requested1 linked violation
November 5, 2010State Public Notification received1 linked violation
October 20, 2010State Public Notification requested1 linked violation
October 20, 2010State Violation/Reminder Notice1 linked violation
October 6, 2010State Violation/Reminder Notice1 linked violation
August 6, 2010State Public Notification received1 linked violation
July 15, 2010State Public Notification requested1 linked violation
July 15, 2010State Violation/Reminder Notice1 linked violation
May 5, 2010State Public Notification received1 linked violation
April 16, 2010State Violation/Reminder Notice1 linked violation
April 16, 2010State Public Notification requested1 linked violation
January 29, 2010State Public Notification received1 linked violation
January 20, 2010State Public Notification requested1 linked violation
January 20, 2010State Violation/Reminder Notice1 linked violation
November 5, 2009State Public Notification received1 linked violation
October 22, 2009State Public Notification requested1 linked violation
October 22, 2009State Violation/Reminder Notice1 linked violation
July 30, 2009State Public Notification received1 linked violation
July 15, 2009State Violation/Reminder Notice1 linked violation
July 15, 2009State Public Notification requested1 linked violation
May 8, 2009State Public Notification received2 linked violations
April 21, 2009State Violation/Reminder Notice1 linked violation
April 21, 2009State Public Notification requested1 linked violation
April 21, 2009State Violation/Reminder Notice1 linked violation
April 21, 2009State Public Notification requested1 linked violation
November 5, 2008State Public Notification received1 linked violation
October 17, 2008State Violation/Reminder Notice1 linked violation
October 17, 2008State Public Notification requested1 linked violation
July 24, 2008State Public Notification received1 linked violation
July 17, 2008State Violation/Reminder Notice1 linked violation
July 17, 2008State Public Notification requested1 linked violation
April 29, 2008State Public Notification received1 linked violation
April 16, 2008State Violation/Reminder Notice1 linked violation
April 16, 2008State Public Notification requested1 linked violation
February 4, 2008State Public Notification received1 linked violation
January 17, 2008State Public Notification requested1 linked violation
January 17, 2008State Violation/Reminder Notice1 linked violation
November 13, 2007State Bilateral Compliance Agreement signed33 linked violations
October 26, 2007State Public Notification received1 linked violation
October 18, 2007State Violation/Reminder Notice1 linked violation
October 18, 2007State Public Notification requested1 linked violation
August 22, 2007State Public Notification received1 linked violation
July 19, 2007State Violation/Reminder Notice1 linked violation
July 19, 2007State Public Notification requested1 linked violation
May 11, 2007State Public Notification received1 linked violation
April 24, 2007State Public Notification requested1 linked violation
April 24, 2007State Violation/Reminder Notice1 linked violation
February 6, 2007State Public Notification received19 linked violations
January 24, 2007State Public Notification requested1 linked violation
November 8, 2006State Public Notification received1 linked violation
October 17, 2006State Violation/Reminder Notice1 linked violation
October 17, 2006State Public Notification requested1 linked violation
August 9, 2006State Public Notification received1 linked violation
July 10, 2006State Violation/Reminder Notice1 linked violation
July 10, 2006State Public Notification requested1 linked violation
May 4, 2006State Public Notification received2 linked violations
April 11, 2006State Public Notification requested5 linked violations
April 11, 2006State Violation/Reminder Notice1 linked violation
March 24, 2006State Bilateral Compliance Agreement signed3 linked violations
February 8, 2006State Compliance Meeting conducted9 linked violations
February 8, 2006State Public Notification received2 linked violations
January 27, 2006State Formal Notice of Violation issued3 linked violations
January 10, 2006State Public Notification requested1 linked violation
January 10, 2006State Violation/Reminder Notice1 linked violation
January 6, 2006State Violation/Reminder Notice1 linked violation
January 6, 2006State Public Notification requested1 linked violation
November 9, 2005State Public Notification received1 linked violation
October 7, 2005State Public Notification requested1 linked violation
October 7, 2005State Violation/Reminder Notice1 linked violation
August 10, 2005State Public Notification received1 linked violation
July 8, 2005State Violation/Reminder Notice2 linked violations
May 16, 2005State Bilateral Compliance Agreement signed14 linked violations
April 8, 2005State Violation/Reminder Notice2 linked violations
February 25, 2005State Public Notification received1 linked violation
January 31, 2005State Formal Notice of Violation issued30 linked violations
January 14, 2005State Public Notification requested1 linked violation
January 14, 2005State Violation/Reminder Notice1 linked violation

Common questions

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

ROTT, JAMIE

779-348-7654

ROCKFORD, IL 61102