BILOXI, MS · Harrison County
CITY OF BILOXI Water System
Consumer Confidence Report status
CITY OF BILOXI 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 BILOXI.
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)
- MS0240001
- System type
- Community Water System
- Population served
- 23,310
- Service connections
- 9,324
- Ownership
- local government
- Water source
- groundwater (wells)
CITY OF BILOXI is among the 24 largest community water systems in Mississippi, serving 23,310 people from groundwater.
As of August 1, 2026, its federal record holds 8 entries between 2007 and 2012, all of which EPA lists as closed. Nothing has been added since 2012.
Of the 8, 6 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
Maximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 2012 – August 31, 2012
ResolvedMonitoring, Regular
—Radium-226
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-228
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
July 1, 2009 – May 15, 2012
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2008 – March 31, 2008
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2007 – September 30, 2007
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| August 1, 2012 – August 31, 2012 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| April 1, 2010 – June 30, 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 |
| July 1, 2009 – May 15, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2008 – March 31, 2008 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2007 – December 31, 2007 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| July 1, 2007 – September 30, 2007 | Monitoring, Regular | Combined Uranium | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- October 11, 2012State Public Notification received2 linked violations
- September 12, 2012State Compliance achieved3 linked violations
- May 15, 2012State Compliance achieved2 linked violations
- May 15, 2012State Public Notification received10 linked violations
- March 20, 2012State Formal Notice of Violation issued9 linked violations
- March 20, 2012State Public Notification requested9 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received6 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received11 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received29 linked violations
- July 1, 2009State Public Notification received6 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received8 linked violations
- July 1, 2009State Public Notification received6 linked violations
- July 1, 2009State Public Notification received7 linked violations
- July 1, 2009State Public Notification received9 linked violations
- July 1, 2009State Public Notification received3 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received3 linked violations
- July 1, 2009State Public Notification received24 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received16 linked violations
- July 1, 2009State Public Notification received14 linked violations
- July 1, 2009State Public Notification received16 linked violations
- July 1, 2009State Public Notification received18 linked violations
- July 1, 2009State Public Notification received12 linked violations
- July 1, 2009State Public Notification received14 linked violations
- July 1, 2009State Public Notification received18 linked violations
- July 1, 2009State Public Notification received10 linked violations
- July 1, 2009State Public Notification received7 linked violations
- July 1, 2009State Public Notification received9 linked violations
- July 1, 2009State Public Notification received6 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received3 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received7 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received3 linked violations
- July 1, 2009State Public Notification received3 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received7 linked violations
- July 1, 2009State Public Notification received3 linked violations
- July 1, 2009State Public Notification received6 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received5 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received6 linked violations
- July 1, 2009State Public Notification received4 linked violations
- July 1, 2009State Public Notification received6 linked violations
- December 30, 2008State Compliance achieved41 linked violations
- December 30, 2008State Compliance achieved24 linked violations
- December 30, 2008State Compliance achieved21 linked violations
- December 30, 2008State Compliance achieved21 linked violations
- December 30, 2008State Compliance achieved23 linked violations
- December 30, 2008State Compliance achieved19 linked violations
- December 30, 2008State Compliance achieved17 linked violations
- December 30, 2008State Compliance achieved18 linked violations
- December 30, 2008State Compliance achieved23 linked violations
- December 30, 2008State Compliance achieved22 linked violations
- December 30, 2008State Compliance achieved26 linked violations
- December 30, 2008State Compliance achieved39 linked violations
- December 30, 2008State Compliance achieved27 linked violations
- November 17, 2008State Public Notification requested60 linked violations
- November 17, 2008State Formal Notice of Violation issued45 linked violations
- November 17, 2008State Formal Notice of Violation issued47 linked violations
- November 17, 2008State Public Notification requested54 linked violations
- November 17, 2008State Public Notification requested40 linked violations
- October 14, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is CITY OF BILOXI required to publish a Consumer Confidence Report?
- Yes. CITY OF BILOXI 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 BILOXI’s next Consumer Confidence Report due?
- CITY OF BILOXI’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CITY OF BILOXI have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CITY OF BILOXI.
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
GILICH JR, A M
228-435-6254
BILOXI, MS 39530