MONMOUTH, IL · Warren County
MONMOUTH Water System
Consumer Confidence Report status
MONMOUTH 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 MONMOUTH.
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)
- IL1870150
- System type
- Community Water System
- Population served
- 8,902
- Service connections
- 3,800
- Ownership
- local government
- Water source
- groundwater (wells)
MONMOUTH is one of 248 community water systems in Illinois in the 3,301 to 10,000 people size category, serving 8,902 people from groundwater.
As of August 1, 2026, its federal record holds 23 entries between 1977 and 2024, all of which EPA lists as closed.
Of the 23, 2 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 Total Coliform Rules, and the Public Notice Rule and Revised PN Rule.
Violation history
Public Notification Violation for NPDWR Violation
—Public Notice
November 28, 2024 – November 20, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2024 – December 31, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 1, 2005 – July 12, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2005 – July 12, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2004 – December 31, 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)
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-basedGross Alpha, Excl. Radon and U
August 1, 2002 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2001 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
June 1, 2001 – June 30, 2001
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1997 – September 30, 2001
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 12, 1995 – July 12, 1999
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
July 1, 1994 – July 31, 1994
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
July 1, 1994 – July 31, 1994
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
September 1, 1988 – August 31, 1992
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
September 14, 1984 – September 13, 1988
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
May 1, 1983 – November 14, 1985
ResolvedMonitoring, 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 |
|---|---|---|---|---|
| November 28, 2024 – November 20, 2024 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2024 – December 31, 2024 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2005 – July 12, 2005 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2005 – July 12, 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 |
| April 1, 2004 – June 30, 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 |
| August 1, 2002 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2001 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| June 1, 2001 – June 30, 2001 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| October 1, 1997 – September 30, 2001 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 12, 1995 – July 12, 1999 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 1994 – July 31, 1994 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
| July 1, 1994 – July 31, 1994 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| September 1, 1988 – August 31, 1992 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| September 14, 1984 – September 13, 1988 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| May 1, 1983 – November 14, 1985 | Maximum Contaminant Level Violation, Average | Fluoride | 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
- March 11, 2025State Compliance achieved1 linked violation
- December 17, 2024State Public Notification received1 linked violation
- December 13, 2024State Violation/Reminder Notice1 linked violation
- November 20, 2024State Compliance achieved1 linked violation
- November 6, 2024State Formal Notice of Violation issued1 linked violation
- October 28, 2024State Violation/Reminder Notice1 linked violation
- October 28, 2024State Public Notification requested1 linked violation
- October 21, 2005State Public Notification received2 linked violations
- September 21, 2005State Public Notification requested1 linked violation
- September 21, 2005State Public Notification requested1 linked violation
- September 21, 2005State Violation/Reminder Notice1 linked violation
- September 21, 2005State Violation/Reminder Notice1 linked violation
- August 15, 2005State Public Notification received1 linked violation
- August 15, 2005State Public Notification received1 linked violation
- July 12, 2005State Compliance achieved24 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
- July 8, 2005State Violation/Reminder Notice1 linked violation
- May 5, 2005State Public Notification received1 linked violation
- May 5, 2005State Public Notification received1 linked violation
- April 8, 2005State Public Notification requested1 linked violation
- April 8, 2005State Public Notification requested1 linked violation
- April 8, 2005State Violation/Reminder Notice1 linked violation
- April 8, 2005State Violation/Reminder Notice1 linked violation
- February 25, 2005State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 25, 2005State Public Notification received1 linked violation
- January 7, 2005State Public Notification requested1 linked violation
- January 7, 2005State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 7, 2005State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 7, 2005State Violation/Reminder Notice1 linked violation
- December 16, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 16, 2004State Public Notification received1 linked violation
- October 19, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- October 19, 2004State Public Notification requested1 linked violation
- October 19, 2004State Violation/Reminder Notice1 linked violation
- October 19, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 3, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- September 3, 2004State Public Notification received1 linked violation
- July 10, 2004State Violation/Reminder Notice1 linked violation
- July 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- July 10, 2004State Public Notification requested1 linked violation
- June 10, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 10, 2004State Public Notification received1 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
- April 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 10, 2004State Public Notification requested1 linked violation
- March 17, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 17, 2004State Public Notification received1 linked violation
- February 17, 2004State Bilateral Compliance Agreement signed20 linked violations
- January 10, 2004State Public Notification requested1 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 Violation/Reminder Notice1 linked violation
- December 19, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 19, 2003State Formal Notice of Violation issued20 linked violations
- December 19, 2003State Public Notification received1 linked violation
- August 25, 2003State Public Notification received1 linked violation
- August 25, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- July 10, 2003State Public Notification requested1 linked violation
- July 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- July 10, 2003State Violation/Reminder Notice1 linked violation
- May 1, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- May 1, 2003State Public Notification received1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- April 10, 2003State Public Notification requested1 linked violation
- April 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- March 11, 2003State Formal Notice of Violation issued11 linked violations
- January 10, 2003State Public Notification requested1 linked violation
- January 10, 2003State Violation/Reminder Notice1 linked violation
- January 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 30, 2002State Violation/Reminder Notice2 linked violations
- December 25, 1996State Public Notification received2 linked violations
- November 11, 1996State Public Notification received2 linked violations
- July 25, 1995State Public Notification received2 linked violations
- July 21, 1995State Public Notification received2 linked violations
- August 27, 1994State Public Notification received1 linked violation
- September 18, 1993State Public Notification received1 linked violation
- April 8, 1991State Public Notification received1 linked violation
- December 18, 1990State Public Notification requested1 linked violation
- December 12, 1990State Public Notification received1 linked violation
- August 23, 1990State Public Notification received1 linked violation
- July 17, 1990State Compliance achieved2 linked violations
- May 19, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- May 19, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- May 18, 1990State Public Notification received2 linked violations
- April 19, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 19, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- April 7, 1990State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 19, 1990State Public Notification received2 linked violations
- March 15, 1990State Public Notification requested2 linked violations
- November 27, 1989State Public Notification received2 linked violations
- September 24, 1989State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- June 9, 1989State Public Notification requested4 linked violations
- February 23, 1989State Public Notification received2 linked violations
Common questions
Is MONMOUTH required to publish a Consumer Confidence Report?
- Yes. MONMOUTH 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 MONMOUTH’s next Consumer Confidence Report due?
- MONMOUTH’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does MONMOUTH have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for MONMOUTH.
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
BLEDSOE, BRAYDEN
309-734-4026
MONMOUTH, IL 61462