Buffalo Lake, MN · Renville County
Buffalo Lake Water System
Consumer Confidence Report status
Buffalo Lake 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 Buffalo Lake.
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 Minnesota’s official records. Always confirm current status with Minnesota before making decisions based on this information.
System facts
- System ID (PWSID)
- MN1650003
- System type
- Community Water System
- Population served
- 703
- Service connections
- 347
- Ownership
- local government
- Water source
- groundwater (wells)
Buffalo Lake is one of 330 community water systems in Minnesota in the 501 to 3,300 people size category, serving 703 people from groundwater.
As of August 1, 2026, its federal record holds 6 entries between 2005 and 2021, all of which EPA lists as closed. Nothing has been added since 2021.
All 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 Lead and Copper Rule and the Stage 2 Disinfectants and Disinfection Byproducts Rule.
Violation history
Monitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
July 1, 2021 – October 31, 2021
ResolvedMonitoring and Reporting (DBP)
—TTHM
July 1, 2021 – October 31, 2021
ArchivedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2020 – September 22, 2021
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2013 – February 4, 2014
ResolvedWater Quality Parameter M/R
—Lead and Copper Rule
July 1, 2012 – December 31, 2012
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2005 – July 7, 2006
Resolved
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2021 – October 31, 2021 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
| July 1, 2021 – October 31, 2021 | Monitoring and Reporting (DBP) | TTHM | — | Archived |
| October 1, 2020 – September 22, 2021 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| October 1, 2013 – February 4, 2014 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| July 1, 2012 – December 31, 2012 | Water Quality Parameter M/R | Lead and Copper Rule | — | Resolved |
| October 1, 2005 – July 7, 2006 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- May 11, 2022State Compliance achieved1 linked violation
- February 22, 2022State Public Notification requested1 linked violation
- February 22, 2022State Formal Notice of Violation issued1 linked violation
- November 4, 2021State Violation/Reminder Notice2 linked violations
- October 1, 2021State Compliance achieved1 linked violation
- September 22, 2021State Compliance achieved1 linked violation
- February 23, 2021State Formal Notice of Violation issued1 linked violation
- February 23, 2021State Public Notification requested1 linked violation
- June 23, 2020State Violation/Reminder Notice1 linked violation
- December 19, 2019State Public Notification requested2 linked violations
- December 19, 2019State Formal Notice of Violation issued1 linked violation
- September 23, 2019State Violation/Reminder Notice2 linked violations
- February 3, 2014State Public Notification received1 linked violation
- January 2, 2014State Violation/Reminder Notice2 linked violations
- November 20, 2013State Public Notification requested1 linked violation
- November 20, 2013State Formal Notice of Violation issued1 linked violation
- September 19, 2013State Violation/Reminder Notice3 linked violations
- September 3, 2013State Violation/Reminder Notice1 linked violation
- February 15, 2013State Public Notification received1 linked violation
- January 22, 2013State Public Notification requested1 linked violation
- January 22, 2013State Formal Notice of Violation issued1 linked violation
- January 2, 2013State Compliance achieved3 linked violations
- February 17, 2011State Violation/Reminder Notice1 linked violation
- October 8, 2010State Violation/Reminder Notice1 linked violation
- October 8, 2010State Public Notification requested2 linked violations
- September 13, 2010State Public Notification received2 linked violations
- August 11, 2010State Public Notification requested3 linked violations
- August 11, 2010State Violation/Reminder Notice1 linked violation
- March 1, 2010State Public Notification received1 linked violation
- February 1, 2010State Violation/Reminder Notice1 linked violation
- January 25, 2010State Public Notification received1 linked violation
- December 24, 2009State Violation/Reminder Notice1 linked violation
- December 17, 2009State Public Notification received1 linked violation
- November 16, 2009State Violation/Reminder Notice1 linked violation
- November 16, 2009State Public Notification requested1 linked violation
- July 14, 2009State Violation/Reminder Notice1 linked violation
- June 29, 2009State Bilateral Compliance Agreement signed2 linked violations
- January 15, 2009State Violation/Reminder Notice1 linked violation
- December 18, 2008State Public Notification received3 linked violations
- July 19, 2007State Bilateral Compliance Agreement signed1 linked violation
- December 14, 2006State Bilateral Compliance Agreement signed3 linked violations
- November 22, 2006State Public Notification requested2 linked violations
- November 22, 2006State Formal Notice of Violation issued4 linked violations
- July 7, 2006State Compliance achieved3 linked violations
- December 1, 2005State Public Notification received1 linked violation
- November 30, 2005State Violation/Reminder Notice1 linked violation
- November 1, 2005State Formal Notice of Violation issued1 linked violation
- November 1, 2005State Public Notification requested1 linked violation
- September 20, 2005State Violation/Reminder Notice1 linked violation
- September 1, 2005State Violation/Reminder Notice1 linked violation
- October 31, 2000State Formal Notice of Violation issued2 linked violations
- September 15, 2000State Violation/Reminder Notice1 linked violation
- June 1, 2000State Violation/Reminder Notice1 linked violation
- May 1, 2000State Violation/Reminder Notice1 linked violation
- February 11, 1994State Formal Notice of Violation issued1 linked violation
Common questions
Is Buffalo Lake required to publish a Consumer Confidence Report?
- Yes. Buffalo Lake 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 Buffalo Lake’s next Consumer Confidence Report due?
- Buffalo Lake’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does Buffalo Lake have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for Buffalo Lake.
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
Buffalo Lake City Council
3208332272
Buffalo Lake, MN 55314