DES PERES, MS · Lafayette County
WELLSGATE Water System
Consumer Confidence Report status
WELLSGATE 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 WELLSGATE.
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 Mississippi’s official records. Always confirm current status with Mississippi before making decisions based on this information.
System facts
- System ID (PWSID)
- MS0360068
- System type
- Community Water System
- Population served
- 1,447
- Service connections
- 548
- Ownership
- privately owned
- Water source
- groundwater (wells)
WELLSGATE is one of 794 community water systems in Mississippi in the 501 to 3,300 people size category, serving 1,447 people from groundwater.
As of August 1, 2026, its federal record holds 37 entries between 2005 and 2025, all of which EPA lists as closed.
Of the 37, 32 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 Groundwater Rule, and the Lead and Copper Rule.
Violation history
Follow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
January 1, 2025 – September 17, 2025
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
December 19, 2024 – May 15, 2025
ResolvedMonitoring and Reporting (DBP)
—TTHM
January 1, 2024 – December 31, 2024
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
March 1, 2023 – March 31, 2023
ResolvedFailure To Address Deficiency
Health-basedGroundwater Rule
February 10, 2021 – January 28, 2022
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
January 1, 2021 – June 28, 2023
ResolvedMonitoring, Regular
—Nitrate
January 1, 2020 – December 31, 2020
ResolvedMonitoring, Regular
—Nitrate-Nitrite
January 1, 2020 – December 31, 2020
ResolvedFailure To Address Deficiency
Health-basedGroundwater Rule
September 13, 2013 – February 20, 2019
ResolvedMonitoring, Regular
—Radium-228
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-226
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedFailure To Address Deficiency
Health-basedGroundwater Rule
October 25, 2011 – February 20, 2019
ResolvedMonitoring, Regular
—Radium-226
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-226
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-228
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-226
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-228
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-226
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-226
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-228
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-228
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-228
October 1, 2008 – December 31, 2008
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
October 1, 2008 – June 27, 2012
ResolvedMonitoring, Regular
—Radium-226
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Carbon tetrachloride
July 1, 2005 – September 30, 2005
ResolvedMonitoring, Regular
—Vinyl chloride
July 1, 2005 – September 30, 2005
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2025 – September 17, 2025 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| December 19, 2024 – May 15, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2024 – December 31, 2024 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| March 1, 2023 – March 31, 2023 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| February 10, 2021 – January 28, 2022 | Failure To Address Deficiency | Groundwater Rule | Health-based | Resolved |
| January 1, 2021 – June 28, 2023 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| January 1, 2020 – December 31, 2020 | Monitoring, Regular | Nitrate | — | Resolved |
| January 1, 2020 – December 31, 2020 | Monitoring, Regular | Nitrate-Nitrite | — | Resolved |
| September 13, 2013 – February 20, 2019 | Failure To Address Deficiency | Groundwater Rule | Health-based | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 25, 2011 – February 20, 2019 | Failure To Address Deficiency | Groundwater Rule | Health-based | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2008 – June 27, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2005 – September 30, 2005 | Monitoring, Regular | Carbon tetrachloride | — | Resolved |
| July 1, 2005 – September 30, 2005 | Monitoring, Regular | Vinyl chloride | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- September 17, 2025State Compliance achieved1 linked violation
- September 17, 2025State Compliance achieved4 linked violations
- September 4, 2025State Compliance achieved1 linked violation
- September 4, 2025State Compliance achieved1 linked violation
- May 15, 2025State Public Notification received1 linked violation
- May 15, 2025State Compliance achieved1 linked violation
- May 15, 2025State Compliance achieved1 linked violation
- May 15, 2025State Public Notification received1 linked violation
- March 19, 2025State no additional Formal Action needed2 linked violations
- January 17, 2025State no additional Formal Action needed1 linked violation
- January 17, 2025State no additional Formal Action needed1 linked violation
- January 17, 2025State no additional Formal Action needed1 linked violation
- November 19, 2024State Formal Notice of Violation issued1 linked violation
- November 19, 2024State Public Notification requested1 linked violation
- October 29, 2024State Public Notification received1 linked violation
- June 30, 2024State Compliance achieved1 linked violation
- March 7, 2024State no additional Formal Action needed2 linked violations
- February 26, 2024State Public Notification requested1 linked violation
- February 26, 2024State Formal Notice of Violation issued1 linked violation
- June 30, 2023State Compliance achieved1 linked violation
- June 29, 2023State Compliance achieved1 linked violation
- June 28, 2023State Compliance achieved1 linked violation
- May 23, 2023State Public Notification received2 linked violations
- April 25, 2023State Compliance achieved1 linked violation
- April 17, 2023State Public Notification requested1 linked violation
- April 17, 2023State Formal Notice of Violation issued1 linked violation
- April 17, 2023State Public Notification requested1 linked violation
- April 17, 2023State Formal Notice of Violation issued1 linked violation
- January 17, 2023State Public Notification requested1 linked violation
- January 17, 2023State Formal Notice of Violation issued1 linked violation
- June 30, 2022State Compliance achieved1 linked violation
- June 30, 2022State Compliance achieved1 linked violation
- June 30, 2022State Public Notification received3 linked violations
- June 30, 2022State Public Notification received1 linked violation
- June 30, 2022State Compliance achieved1 linked violation
- June 30, 2022State Compliance achieved1 linked violation
- June 30, 2022State Compliance achieved1 linked violation
- May 13, 2022State Public Notification received2 linked violations
- April 28, 2022State Compliance achieved1 linked violation
- April 8, 2022State Public Notification requested1 linked violation
- April 8, 2022State Formal Notice of Violation issued1 linked violation
- April 8, 2022State Formal Notice of Violation issued1 linked violation
- April 8, 2022State Public Notification requested1 linked violation
- April 7, 2022State Compliance achieved1 linked violation
- April 1, 2022State Formal Notice of Violation issued1 linked violation
- April 1, 2022State Public Notification requested1 linked violation
- February 15, 2022State Public Notification requested1 linked violation
- February 15, 2022State Formal Notice of Violation issued1 linked violation
- January 28, 2022State Compliance achieved1 linked violation
- October 14, 2021State Compliance achieved3 linked violations
- May 27, 2021State Public Notification received1 linked violation
- April 5, 2021State Public Notification requested1 linked violation
- April 5, 2021State Formal Notice of Violation issued1 linked violation
- April 5, 2021State Public Notification requested1 linked violation
- April 5, 2021State Formal Notice of Violation issued1 linked violation
- April 5, 2021State Public Notification requested1 linked violation
- April 5, 2021State Formal Notice of Violation issued1 linked violation
- March 11, 2021State Public Notification requested3 linked violations
- March 11, 2021State Formal Notice of Violation issued3 linked violations
- January 11, 2021State Formal Notice of Violation issued2 linked violations
- February 20, 2019State Compliance achieved1 linked violation
- February 20, 2019State Compliance achieved3 linked violations
- September 30, 2012State Compliance achieved143 linked violations
- June 27, 2012State Public Notification received107 linked violations
- June 20, 2007State Public Notification received205 linked violations
Common questions
Is WELLSGATE required to publish a Consumer Confidence Report?
- Yes. WELLSGATE 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 WELLSGATE’s next Consumer Confidence Report due?
- WELLSGATE’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does WELLSGATE have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for WELLSGATE.
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
COX, JOSIAH
314-736-4743
DES PERES, MO 63131