HAMPDEN, ME · Waldo County
UNITY BY THE STREAM LLC Water System
Consumer Confidence Report status
UNITY BY THE STREAM LLC 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 UNITY BY THE STREAM LLC.
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 Maine’s official records. Always confirm current status with Maine before making decisions based on this information.
System facts
- System ID (PWSID)
- ME0095570
- System type
- Community Water System
- Population served
- 88
- Service connections
- 35
- Ownership
- privately owned
- Water source
- groundwater (wells)
UNITY BY THE STREAM LLC is one of 536 community water systems in Maine in the 500 or fewer people size category, serving 88 people from groundwater.
As of August 1, 2026, its federal record holds 27 entries between 2005 and 2026, all of which EPA lists as closed.
Of the 27, 7 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 inorganic chemicals, the Public Notice Rule and Revised PN Rule, and the Stage 2 Disinfectants and Disinfection Byproducts Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2026 – March 31, 2026
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2025 – December 31, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2025 – September 30, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2025 – June 30, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2025 – March 31, 2025
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
November 23, 2024 – October 28, 2024
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
November 23, 2024 – October 28, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2023 – June 30, 2023
ResolvedMonitoring and Reporting (DBP)
—TTHM
October 1, 2022 – December 31, 2022
ResolvedMonitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
October 1, 2022 – December 31, 2022
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2022 – September 30, 2022
ResolvedMonitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
January 1, 2022 – March 31, 2022
ResolvedConsumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2021 – January 3, 2022
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2020 – June 30, 2020
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2020 – March 31, 2020
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2019 – June 30, 2019
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
June 27, 2015 – July 7, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2014 – December 31, 2014
ResolvedMonitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
January 1, 2011 – December 31, 2013
ResolvedMonitoring and Reporting (DBP)
—TTHM
January 1, 2011 – December 31, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
November 1, 2008 – November 30, 2008
ResolvedMonitoring, Regular
—Arsenic
August 1, 2008 – August 31, 2008
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
April 1, 2008 – June 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2006 – September 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2006 – June 30, 2006
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedArsenic
September 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedArsenic
August 1, 2005 – August 31, 2005
Resolved
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2026 – March 31, 2026 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| October 1, 2025 – December 31, 2025 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| July 1, 2025 – September 30, 2025 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| April 1, 2025 – June 30, 2025 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| January 1, 2025 – March 31, 2025 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| November 23, 2024 – October 28, 2024 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| November 23, 2024 – October 28, 2024 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| April 1, 2023 – June 30, 2023 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2022 – December 31, 2022 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| October 1, 2022 – December 31, 2022 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
| July 1, 2022 – September 30, 2022 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2022 – March 31, 2022 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
| July 1, 2021 – January 3, 2022 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
| April 1, 2020 – June 30, 2020 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2020 – March 31, 2020 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2019 – June 30, 2019 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| June 27, 2015 – July 7, 2015 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2014 – December 31, 2014 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2011 – December 31, 2013 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
| January 1, 2011 – December 31, 2013 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| November 1, 2008 – November 30, 2008 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| August 1, 2008 – August 31, 2008 | Monitoring, Regular | Arsenic | — | Resolved |
| April 1, 2008 – June 30, 2008 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| July 1, 2006 – September 30, 2006 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2006 – June 30, 2006 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| September 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Single Sample | Arsenic | Health-based | Resolved |
| August 1, 2005 – August 31, 2005 | Maximum Contaminant Level Violation, Single Sample | Arsenic | Health-based | Resolved |
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
Enforcement actions
- March 30, 2026State Public Notification received2 linked violations
- March 19, 2026State Formal Notice of Violation issued9 linked violations
- January 8, 2026State Public Notification requested2 linked violations
- January 8, 2026State Formal Notice of Violation issued1 linked violation
- October 29, 2025State Public Notification received1 linked violation
- October 20, 2025State Public Notification requested1 linked violation
- October 20, 2025State Formal Notice of Violation issued1 linked violation
- July 10, 2025State Public Notification requested2 linked violations
- April 24, 2025State Public Notification received2 linked violations
- March 7, 2025State Public Notification received4 linked violations
- February 24, 2025State Formal Notice of Violation issued3 linked violations
- October 22, 2024State Formal Notice of Violation issued3 linked violations
- October 22, 2024State Formal Notice of Violation issued2 linked violations
- October 22, 2024State Public Notification requested3 linked violations
- June 13, 2024State Public Notification requested2 linked violations
- May 24, 2024State Public Notification received5 linked violations
- May 15, 2024State Public Notification received3 linked violations
- May 3, 2024State Public Notification requested3 linked violations
- May 3, 2024State Formal Notice of Violation issued3 linked violations
- March 19, 2024State Formal Notice of Violation issued3 linked violations
- September 21, 2023State Compliance achieved6 linked violations
- August 4, 2023State Formal Notice of Violation issued4 linked violations
- August 4, 2023State Public Notification requested2 linked violations
- June 20, 2023State Public Notification received2 linked violations
- June 5, 2023State Public Notification requested2 linked violations
- March 27, 2023State Public Notification received3 linked violations
- March 12, 2023State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- March 12, 2023State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- March 10, 2023State Public Notification received4 linked violations
- March 9, 2023State Compliance achieved5 linked violations
- February 22, 2023State Public Notification received1 linked violation
- February 21, 2023State Public Notification requested2 linked violations
- February 21, 2023State Formal Notice of Violation issued3 linked violations
- February 14, 2023State Formal Notice of Violation issued1 linked violation
- February 7, 2023State Formal Notice of Violation issued1 linked violation
- February 7, 2023State Public Notification requested1 linked violation
- January 19, 2023State Public Notification received2 linked violations
- January 11, 2023State Compliance achieved1 linked violation
- January 10, 2023State Formal Notice of Violation issued2 linked violations
- January 10, 2023State Public Notification requested2 linked violations
- January 9, 2023State Compliance achieved1 linked violation
- November 9, 2022State Public Notification received1 linked violation
- October 29, 2022State Public Notification requested1 linked violation
- October 29, 2022State Formal Notice of Violation issued1 linked violation
- June 28, 2022State Compliance achieved2 linked violations
- June 27, 2022State Formal Notice of Violation issued2 linked violations
- June 27, 2022State Public Notification requested2 linked violations
- April 26, 2022State Public Notification received1 linked violation
- March 15, 2022State Formal Notice of Violation issued1 linked violation
- July 8, 2020State Compliance achieved7 linked violations
- July 8, 2020State Compliance achieved2 linked violations
- June 22, 2020State Public Notification received1 linked violation
- June 5, 2020State Public Notification requested1 linked violation
- June 5, 2020State Formal Notice of Violation issued1 linked violation
- May 4, 2020State Public Notification received1 linked violation
- April 22, 2020State Public Notification requested1 linked violation
- April 22, 2020State Formal Notice of Violation issued1 linked violation
- November 21, 2019State Public Notification received1 linked violation
- November 14, 2019State Formal Notice of Violation issued1 linked violation
- November 14, 2019State Public Notification requested1 linked violation
- October 18, 2019State Public Notification received1 linked violation
- September 9, 2019State Formal Notice of Violation issued1 linked violation
- September 9, 2019State Public Notification requested1 linked violation
- September 5, 2019State Public Notification received1 linked violation
- August 16, 2019State Public Notification requested1 linked violation
- August 16, 2019State Formal Notice of Violation issued1 linked violation
- March 19, 2019State Public Notification received1 linked violation
- February 25, 2019State Formal Notice of Violation issued1 linked violation
- February 25, 2019State Public Notification requested1 linked violation
- February 7, 2019State Public Notification received1 linked violation
- January 2, 2019State Formal Notice of Violation issued1 linked violation
- January 2, 2019State Public Notification requested1 linked violation
- December 20, 2018State Public Notification received1 linked violation
- November 6, 2018State Formal Notice of Violation issued1 linked violation
- November 6, 2018State Public Notification requested1 linked violation
- July 6, 2018State Public Notification received1 linked violation
- June 13, 2018State Public Notification requested1 linked violation
- June 13, 2018State Formal Notice of Violation issued1 linked violation
- August 11, 2015State Compliance achieved4 linked violations
- July 13, 2015State Public Notification received1 linked violation
- July 8, 2015State Formal Notice of Violation issued1 linked violation
- July 7, 2015State Compliance achieved1 linked violation
- May 27, 2015State Public Notification requested1 linked violation
- May 27, 2015State Formal Notice of Violation issued1 linked violation
- March 11, 2015State Public Notification received1 linked violation
- February 25, 2015State Formal Notice of Violation issued1 linked violation
- February 25, 2015State Public Notification requested1 linked violation
- February 23, 2015State Public Notification received1 linked violation
- February 18, 2015State Formal Notice of Violation issued1 linked violation
- January 7, 2015State Compliance achieved1 linked violation
- December 17, 2014State Public Notification requested1 linked violation
- December 17, 2014State Formal Notice of Violation issued1 linked violation
- October 9, 2014State Public Notification received1 linked violation
- September 15, 2014State Public Notification requested1 linked violation
- September 15, 2014State Formal Notice of Violation issued1 linked violation
- July 9, 2014State Compliance achieved2 linked violations
- December 16, 2013State Public Notification received2 linked violations
- November 22, 2013State Formal Notice of Violation issued2 linked violations
- November 22, 2013State Public Notification requested2 linked violations
- September 16, 2011State Intentional no-action2 linked violations
- August 19, 2011State Intentional no-action2 linked violations
- December 7, 2009State Compliance achieved5 linked violations
- October 27, 2009State Compliance achieved2 linked violations
- October 23, 2009State Public Notification received6 linked violations
- March 24, 2009State Public Notification requested1 linked violation
- March 24, 2009State Formal Notice of Violation issued1 linked violation
- November 18, 2008State Formal Notice of Violation issued2 linked violations
- November 18, 2008State Public Notification requested1 linked violation
- November 18, 2008State Formal Notice of Violation issued1 linked violation
- November 18, 2008State Public Notification requested1 linked violation
- August 25, 2008State Public Notification received1 linked violation
- August 25, 2008State Compliance achieved1 linked violation
- August 5, 2008State Public Notification requested1 linked violation
- January 3, 2007State Violation/Reminder Notice5 linked violations
- January 3, 2007State Formal Notice of Violation issued1 linked violation
- August 18, 2006State Public Notification requested7 linked violations
- May 18, 2006State Public Notification received3 linked violations
- May 18, 2006State Public Notification received3 linked violations
- April 18, 2006State Violation/Reminder Notice5 linked violations
- April 18, 2006State Public Notification requested6 linked violations
- February 16, 2006State Public Notification requested4 linked violations
- February 16, 2006State Violation/Reminder Notice3 linked violations
- January 13, 2006State Compliance achieved3 linked violations
- September 16, 2005State Violation/Reminder Notice2 linked violations
- June 10, 2002State Compliance achieved1 linked violation
- May 24, 2002State Violation/Reminder Notice2 linked violations
- May 24, 2002State Public Notification requested4 linked violations
- December 15, 2000State Public Notification received1 linked violation
Common questions
Is UNITY BY THE STREAM LLC required to publish a Consumer Confidence Report?
- Yes. UNITY BY THE STREAM LLC 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 UNITY BY THE STREAM LLC’s next Consumer Confidence Report due?
- UNITY BY THE STREAM LLC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does UNITY BY THE STREAM LLC have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for UNITY BY THE STREAM LLC.
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
PATTERSON, KAREN
Phone not on record
HAMPDEN, ME 04444