EVERLY, IA · Clay County
EVERLY WATER SUPPLY Water System
Consumer Confidence Report status
EVERLY WATER SUPPLY 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 EVERLY WATER SUPPLY.
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 Iowa’s official records. Always confirm current status with Iowa before making decisions based on this information.
System facts
- System ID (PWSID)
- IA2115029
- System type
- Community Water System
- Population served
- 575
- Service connections
- 345
- Ownership
- local government
- Water source
- groundwater (wells)
EVERLY WATER SUPPLY is one of 403 community water systems in Iowa in the 501 to 3,300 people size category, serving 575 people from groundwater.
As of August 1, 2026, its federal record holds 18 entries between 1978 and 2022, all of which EPA lists as closed. Nothing has been added since 2022.
Of the 18, 12 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 inorganic chemicals, synthetic organic chemicals, and volatile organic chemicals.
Violation history
Monitoring, Regular
—Nitrate
March 1, 2022 – March 31, 2022
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedNitrate
June 1, 2000 – June 30, 2000
ResolvedMaximum Contaminant Level Violation, Average
Health-basedNitrate
November 1, 1997 – November 30, 1997
ResolvedMonitoring, Regular
—Toluene
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—Xylenes, Total
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—LASSO
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—Atrazine
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—Dinoseb
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—Pentachlorophenol
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—Simazine
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—2,4,5-TP
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—Picloram
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—p-Dichlorobenzene
January 1, 1996 – December 31, 2000
ResolvedMonitoring, Regular
—Ethylbenzene
January 1, 1996 – December 31, 2000
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedNitrate
January 1, 1985 – August 31, 1985
ArchivedMaximum Contaminant Level Violation, Single Sample
Health-basedNitrate
October 1, 1983 – September 30, 1984
ArchivedMaximum Contaminant Level Violation, Average
Health-basedNitrate
July 12, 1978 – July 11, 1979
ArchivedMaximum Contaminant Level Violation, Average
Health-basedNitrate
July 12, 1978 – July 11, 1979
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 |
|---|---|---|---|---|
| March 1, 2022 – March 31, 2022 | Monitoring, Regular | Nitrate | — | Resolved |
| June 1, 2000 – June 30, 2000 | Maximum Contaminant Level Violation, Single Sample | Nitrate | Health-based | Resolved |
| November 1, 1997 – November 30, 1997 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Toluene | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Xylenes, Total | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | LASSO | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Atrazine | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Dinoseb | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Pentachlorophenol | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Simazine | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | 2,4,5-TP | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Picloram | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | p-Dichlorobenzene | — | Resolved |
| January 1, 1996 – December 31, 2000 | Monitoring, Regular | Ethylbenzene | — | Resolved |
| January 1, 1985 – August 31, 1985 | Maximum Contaminant Level Violation, Single Sample | Nitrate | Health-based | Archived |
| October 1, 1983 – September 30, 1984 | Maximum Contaminant Level Violation, Single Sample | Nitrate | Health-based | Archived |
| July 12, 1978 – July 11, 1979 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Archived |
| July 12, 1978 – July 11, 1979 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- April 25, 2022State Public Notification received1 linked violation
- April 25, 2022State Public Notification received1 linked violation
- April 20, 2022State Compliance achieved1 linked violation
- April 18, 2022State Public Notification requested1 linked violation
- April 18, 2022State Formal Notice of Violation issued1 linked violation
- April 18, 2022State Public Notification requested1 linked violation
- April 18, 2022State Formal Notice of Violation issued1 linked violation
- April 18, 2022State Public Notification requested1 linked violation
- April 18, 2022State Formal Notice of Violation issued1 linked violation
- April 18, 2022State Public Notification requested1 linked violation
- April 18, 2022State Formal Notice of Violation issued1 linked violation
- September 13, 2013State Public Notification received1 linked violation
- September 13, 2013State Public Notification received2 linked violations
- July 31, 2013State Compliance achieved2 linked violations
- October 18, 2012State Public Notification requested2 linked violations
- October 18, 2012State Public Notification requested4 linked violations
- December 3, 2002State Compliance achieved4 linked violations
- December 3, 2002State Compliance achieved6 linked violations
- December 3, 2002State Compliance achieved5 linked violations
- March 5, 2001State Compliance achieved2 linked violations
- March 5, 2001State Compliance achieved3 linked violations
- March 5, 2001State Compliance achieved2 linked violations
- March 5, 2001State Compliance achieved4 linked violations
- March 5, 2001State Compliance achieved3 linked violations
- March 5, 2001State Compliance achieved4 linked violations
- March 5, 2001State Compliance achieved4 linked violations
- March 5, 2001State Compliance achieved4 linked violations
- March 5, 2001State Compliance achieved4 linked violations
- March 5, 2001State Compliance achieved7 linked violations
- March 5, 2001State Compliance achieved5 linked violations
- March 5, 2001State Compliance achieved2 linked violations
- March 5, 2001State Compliance achieved5 linked violations
- March 5, 2001State Compliance achieved4 linked violations
- March 1, 2001State Bilateral Compliance Agreement signed3 linked violations
- March 1, 2001State Bilateral Compliance Agreement signed3 linked violations
- February 28, 2001State Compliance achieved7 linked violations
- February 28, 2001State Compliance achieved4 linked violations
- February 19, 2001State Formal Notice of Violation issued2 linked violations
- February 19, 2001State Public Notification requested2 linked violations
- February 19, 2001State Public Notification requested3 linked violations
- February 19, 2001State Public Notification requested4 linked violations
- February 19, 2001State Public Notification requested3 linked violations
- February 19, 2001State Public Notification requested2 linked violations
- February 19, 2001State Public Notification requested4 linked violations
- February 19, 2001State Public Notification requested8 linked violations
- February 19, 2001State Public Notification requested2 linked violations
- February 19, 2001State Public Notification requested1 linked violation
- February 19, 2001State Public Notification requested3 linked violations
- February 19, 2001State Public Notification requested2 linked violations
- February 19, 2001State Formal Notice of Violation issued3 linked violations
- February 19, 2001State Formal Notice of Violation issued2 linked violations
- February 19, 2001State Formal Notice of Violation issued2 linked violations
- February 19, 2001State Formal Notice of Violation issued2 linked violations
- February 19, 2001State Formal Notice of Violation issued2 linked violations
- February 19, 2001State Formal Notice of Violation issued5 linked violations
- February 19, 2001State Formal Notice of Violation issued2 linked violations
- September 11, 2000State Formal Notice of Violation issued2 linked violations
- August 10, 2000State Public Notification requested11 linked violations
- May 31, 2000State Bilateral Compliance Agreement signed3 linked violations
- May 31, 2000State Bilateral Compliance Agreement signed2 linked violations
- May 31, 2000State Bilateral Compliance Agreement signed2 linked violations
- May 31, 2000State Bilateral Compliance Agreement signed2 linked violations
- May 31, 2000State Bilateral Compliance Agreement signed2 linked violations
- April 7, 2000State Formal Notice of Violation issued2 linked violations
- April 7, 2000State Formal Notice of Violation issued12 linked violations
- February 10, 2000State Public Notification received1 linked violation
- February 10, 2000State Formal Notice of Violation issued1 linked violation
- April 23, 1998State Public Notification requested4 linked violations
- March 23, 1998State Public Notification requested1 linked violation
- January 23, 1998State Bilateral Compliance Agreement signed1 linked violation
- January 23, 1998State Bilateral Compliance Agreement signed9 linked violations
- January 23, 1998State Bilateral Compliance Agreement signed3 linked violations
- January 7, 1998State Public Notification requested1 linked violation
- January 7, 1998State Formal Notice of Violation issued1 linked violation
- December 23, 1997State Public Notification received8 linked violations
- November 24, 1997State Formal Notice of Violation issued37 linked violations
- September 3, 1992State Compliance achieved1 linked violation
- September 3, 1992State Compliance achieved1 linked violation
- March 26, 1992State Public Notification received2 linked violations
- March 26, 1992State Public Notification received1 linked violation
- May 28, 1991State Compliance achieved1 linked violation
- September 30, 1984Federal issued Formal Notice of Violation2 linked violations
- January 19, 1982State Unresolved2 linked violations
Common questions
Is EVERLY WATER SUPPLY required to publish a Consumer Confidence Report?
- Yes. EVERLY WATER SUPPLY 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 EVERLY WATER SUPPLY’s next Consumer Confidence Report due?
- EVERLY WATER SUPPLY’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does EVERLY WATER SUPPLY have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for EVERLY WATER SUPPLY.
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
EVERLY WATER SUPPLY
712-834-2691
EVERLY, IA 51338