FLORENCE, MS · Rankin County
TOWN OF FLORENCE Water System
Consumer Confidence Report status
TOWN OF FLORENCE 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 TOWN OF FLORENCE.
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)
- MS0610009
- System type
- Community Water System
- Population served
- 5,824
- Service connections
- 2,206
- Ownership
- local government
- Water source
- groundwater (wells)
TOWN OF FLORENCE is one of 161 community water systems in Mississippi in the 3,301 to 10,000 people size category, serving 5,824 people from groundwater.
As of August 1, 2026, its federal record holds 42 entries between 2007 and 2024, all of which EPA lists as closed.
Of the 42, 41 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 and the Stage 2 Disinfectants and Disinfection Byproducts Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedTTHM
January 1, 2024 – March 31, 2024
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-228
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-226
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-226
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
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
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-228
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-226
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2009 – December 31, 2009
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
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-228
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-226
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 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
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-228
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2007 – September 30, 2007
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
July 1, 2007 – September 30, 2007
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2024 – March 31, 2024 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | 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-228 | — | Resolved |
| April 1, 2011 – June 30, 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-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Combined Uranium | — | 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 | Radium-228 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2009 – December 31, 2009 | 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 |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2009 – March 31, 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 |
| July 1, 2007 – September 30, 2007 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2007 – September 30, 2007 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- April 30, 2024State Public Notification received5 linked violations
- April 10, 2024State Public Notification requested2 linked violations
- March 12, 2024State Other6 linked violations
- January 29, 2024State Public Notification received2 linked violations
- January 11, 2024State Public Notification requested3 linked violations
- January 11, 2024State Formal Notice of Violation issued3 linked violations
- December 1, 2023State Public Notification received2 linked violations
- November 7, 2023State Public Notification requested3 linked violations
- September 19, 2023State Formal Notice of Violation issued2 linked violations
- July 11, 2022State Formal Notice of Violation issued3 linked violations
- July 11, 2022State Formal Notice of Violation issued3 linked violations
- November 6, 2020State Public Notification received2 linked violations
- October 14, 2020State Public Notification requested2 linked violations
- May 21, 2013State Public Notification received50 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved1 linked violation
- December 31, 2012State Compliance achieved2 linked violations
- December 31, 2012State Compliance achieved2 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved16 linked violations
- December 31, 2012State Compliance achieved12 linked violations
- December 31, 2012State Compliance achieved6 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved6 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved6 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- July 2, 2012State Public Notification received155 linked violations
- March 20, 2012State Public Notification requested156 linked violations
Common questions
Is TOWN OF FLORENCE required to publish a Consumer Confidence Report?
- Yes. TOWN OF FLORENCE 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 TOWN OF FLORENCE’s next Consumer Confidence Report due?
- TOWN OF FLORENCE’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does TOWN OF FLORENCE have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for TOWN OF FLORENCE.
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
GUNN, TREY
601-845-3542
FLORENCE, MS 39073