RIO HONDO, TX · Cameron County
CITY OF RIO HONDO Water System
Consumer Confidence Report status
CITY OF RIO HONDO 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 RIO HONDO.
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 Texas’s official records. Always confirm current status with Texas before making decisions based on this information.
System facts
- System ID (PWSID)
- TX0310006
- System type
- Community Water System
- Population served
- 2,640
- Service connections
- 824
- Ownership
- local government
- Water source
- surface water (rivers, lakes, or reservoirs)
CITY OF RIO HONDO is one of 1,859 community water systems in Texas in the 501 to 3,300 people size category, serving 2,640 people from surface water.
As of August 1, 2026, its federal record holds 12 entries between 2009 and 2025, all of which EPA lists as closed.
Of the 12, 3 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 Public Notice Rule and Revised PN Rule, the Stage 2 Disinfectants and Disinfection Byproducts Rule, and the Surface Water Treatment Rules.
Violation history
Monitoring of Treatment (SWTR-Filter)
—Surface Water Treatment Rule
October 1, 2025 – October 31, 2025
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
March 3, 2025 – March 27, 2025
ResolvedMonthly Turbidity Exceed (Enhanced SWTR)
Health-basedInterim Enhanced Surface Water Treatment Rule
December 1, 2020 – December 31, 2020
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
August 7, 2020 – July 6, 2020
ResolvedMonitoring and Reporting (DBP)
—Chlorite
October 1, 2019 – October 31, 2019
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
August 3, 2019 – September 9, 2019
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
October 31, 2018 – September 9, 2019
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2018 – December 31, 2018
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
July 31, 2018 – September 9, 2019
ResolvedFailure Submit IDSE/Subpart V Plan Rpt
—Total Haloacetic Acids (HAA5)
June 12, 2018 – September 11, 2018
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2016 – December 31, 2016
ResolvedConsumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2009 – December 22, 2010
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 1, 2025 – October 31, 2025 | Monitoring of Treatment (SWTR-Filter) | Surface Water Treatment Rule | — | Resolved |
| March 3, 2025 – March 27, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| December 1, 2020 – December 31, 2020 | Monthly Turbidity Exceed (Enhanced SWTR) | Interim Enhanced Surface Water Treatment Rule | Health-based | Resolved |
| August 7, 2020 – July 6, 2020 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2019 – October 31, 2019 | Monitoring and Reporting (DBP) | Chlorite | — | Resolved |
| August 3, 2019 – September 9, 2019 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 31, 2018 – September 9, 2019 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2018 – December 31, 2018 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 31, 2018 – September 9, 2019 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| June 12, 2018 – September 11, 2018 | Failure Submit IDSE/Subpart V Plan Rpt | Total Haloacetic Acids (HAA5) | — | Resolved |
| October 1, 2016 – December 31, 2016 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2009 – December 22, 2010 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- February 9, 2026State Violation/Reminder Notice5 linked violations
- January 9, 2026State Compliance achieved7 linked violations
- May 29, 2025State Public Notification received8 linked violations
- May 21, 2025State Public Notification requested4 linked violations
- April 28, 2025State Public Notification requested3 linked violations
- April 10, 2025State Public Notification received2 linked violations
- April 10, 2025State Compliance achieved4 linked violations
- April 4, 2025State Public Notification received3 linked violations
- March 31, 2025State Public Notification requested4 linked violations
- March 25, 2025State Violation/Reminder Notice3 linked violations
- March 20, 2025State Violation/Reminder Notice5 linked violations
- March 10, 2025State Compliance achieved7 linked violations
- January 31, 2025State Public Notification requested10 linked violations
- January 1, 2023State Compliance achieved12 linked violations
- December 1, 2022State Compliance achieved5 linked violations
- November 17, 2022State Violation/Reminder Notice3 linked violations
- May 27, 2022State Formal Notice of Violation issued7 linked violations
- April 30, 2022State Public Notification requested2 linked violations
- April 27, 2022State Public Notification received10 linked violations
- April 26, 2022State Violation/Reminder Notice4 linked violations
- January 31, 2022State Public Notification requested4 linked violations
- October 1, 2021State Compliance achieved2 linked violations
- September 21, 2021State Compliance achieved5 linked violations
- September 21, 2021State Public Notification received4 linked violations
- August 3, 2021State Violation/Reminder Notice3 linked violations
- April 1, 2021State Compliance achieved5 linked violations
- March 3, 2021State Violation/Reminder Notice8 linked violations
- September 23, 2020State Public Notification received7 linked violations
- September 1, 2020State Compliance achieved26 linked violations
- September 1, 2020State Compliance achieved7 linked violations
- August 28, 2020State Violation/Reminder Notice6 linked violations
- January 22, 2020State Violation/Reminder Notice6 linked violations
- November 1, 2019State Violation/Reminder Notice6 linked violations
- October 21, 2019State Public Notification requested6 linked violations
- October 16, 2019State Public Notification requested6 linked violations
- September 9, 2019State Public Notification received2 linked violations
- September 9, 2019State Compliance achieved8 linked violations
- September 9, 2019State Compliance achieved52 linked violations
- September 9, 2019State Public Notification received6 linked violations
- September 9, 2019State Compliance achieved6 linked violations
- September 9, 2019State Public Notification received15 linked violations
- September 9, 2019State Compliance achieved13 linked violations
- June 28, 2019State Violation/Reminder Notice11 linked violations
- May 6, 2019State Violation/Reminder Notice18 linked violations
- February 10, 2019State Compliance achieved36 linked violations
- December 10, 2018State Public Notification requested38 linked violations
- September 11, 2018State Compliance achieved49 linked violations
- September 10, 2018State Compliance achieved37 linked violations
- January 31, 2012State Public Notification requested35 linked violations
- July 1, 1986State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- June 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- September 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- May 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- August 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- July 1, 1982State Public Notification received1 linked violation
- June 1, 1982State Public Notification received1 linked violation
- April 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 1, 1982State Public Notification received1 linked violation
- February 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- November 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- September 1, 1981State Public Notification received1 linked violation
- August 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- July 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- November 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- September 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- August 1, 1980Federal issued Formal Notice of Violation1 linked violation
- July 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- June 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- May 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- April 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- March 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- February 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- January 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- December 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- November 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- October 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
Common questions
Is CITY OF RIO HONDO required to publish a Consumer Confidence Report?
- Yes. CITY OF RIO HONDO 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 RIO HONDO’s next Consumer Confidence Report due?
- CITY OF RIO HONDO’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CITY OF RIO HONDO have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CITY OF RIO HONDO.
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
OLIVARES, GUSTAVO
956-748-2102
RIO HONDO, TX 78583-0389