LAUREL, MS · Jones County
CITY OF LAUREL Water System
Consumer Confidence Report status
CITY OF LAUREL 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 CITY OF LAUREL.
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)
- MS0340021
- System type
- Community Water System
- Population served
- 18,100
- Service connections
- 8,900
- Ownership
- local government
- Water source
- groundwater (wells)
CITY OF LAUREL is one of 56 community water systems in Mississippi in the 10,001 to 100,000 people size category, serving 18,100 people from groundwater.
As of August 1, 2026, its federal record holds 39 entries between 2007 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
Of the 39, 38 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 Stage 2 Disinfectants and Disinfection Byproducts Rule, and the Public Notice Rule and Revised PN Rule.
Violation history
Monitoring and Reporting (DBP)
—TTHM
January 1, 2023 – December 31, 2023
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-228
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-228
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-228
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-228
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-228
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-226
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-226
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-226
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
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-228
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-226
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-226
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2010 – March 31, 2010
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
July 1, 2009 – May 29, 2012
ResolvedMonitoring, Regular
—Radium-226
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
January 1, 2007 – March 31, 2007
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2023 – December 31, 2023 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2009 – May 29, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- May 29, 2012State Compliance achieved1 linked violation
- May 29, 2012State Public Notification received49 linked violations
- March 20, 2012State Public Notification requested48 linked violations
- March 20, 2012State Formal Notice of Violation issued50 linked violations
- September 14, 2010State Compliance achieved12 linked violations
- October 26, 2009State Compliance achieved6 linked violations
- June 24, 2009State Public Notification received4 linked violations
- June 24, 2009State Public Notification received3 linked violations
- June 24, 2009State Public Notification received3 linked violations
- June 24, 2009State Public Notification received4 linked violations
- June 24, 2009State Public Notification received3 linked violations
- June 24, 2009State Public Notification received3 linked violations
- June 24, 2009State Public Notification received3 linked violations
- June 24, 2009State Public Notification received3 linked violations
- June 24, 2009State Public Notification received3 linked violations
- June 24, 2009State Public Notification received4 linked violations
- June 24, 2009State Public Notification received4 linked violations
- June 24, 2009State Public Notification received6 linked violations
- June 24, 2009State Public Notification received5 linked violations
- June 24, 2009State Public Notification received16 linked violations
- June 24, 2009State Public Notification received6 linked violations
- June 24, 2009State Public Notification received6 linked violations
- June 24, 2009State Public Notification received3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved4 linked violations
- December 30, 2008State Compliance achieved4 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved12 linked violations
- December 30, 2008State Compliance achieved4 linked violations
- December 30, 2008State Compliance achieved5 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- December 30, 2008State Compliance achieved3 linked violations
- November 17, 2008State Public Notification requested4 linked violations
- November 17, 2008State Formal Notice of Violation issued4 linked violations
- November 17, 2008State Public Notification requested4 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Formal Notice of Violation issued3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Public Notification requested5 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Formal Notice of Violation issued5 linked violations
- November 17, 2008State Public Notification requested4 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Formal Notice of Violation issued3 linked violations
- November 17, 2008State Formal Notice of Violation issued3 linked violations
- November 17, 2008State Formal Notice of Violation issued3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Formal Notice of Violation issued3 linked violations
- November 17, 2008State Public Notification requested4 linked violations
- November 17, 2008State Formal Notice of Violation issued4 linked violations
- November 17, 2008State Formal Notice of Violation issued5 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Formal Notice of Violation issued3 linked violations
- November 17, 2008State Formal Notice of Violation issued3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Formal Notice of Violation issued4 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Formal Notice of Violation issued5 linked violations
- November 17, 2008State Public Notification requested4 linked violations
- November 17, 2008State Formal Notice of Violation issued4 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- November 17, 2008State Public Notification requested3 linked violations
- September 10, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is CITY OF LAUREL required to publish a Consumer Confidence Report?
- Yes. CITY OF LAUREL 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 CITY OF LAUREL’s next Consumer Confidence Report due?
- CITY OF LAUREL’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CITY OF LAUREL have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CITY OF LAUREL.
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
MAGEE, JOHNNY
601-428-6401
LAUREL, MS 39441